Thanks, that seemed to work. However, now when I try to enable static caching, the “Regenerate files” link doesn’t work. Clicking it doesn’t clear the “Regenerate files” prompt, it just persists ( see screenshot here: https://today.ucsd.edu/news_uploads/redis-static.png ). Also, the index_redis_default_site.php file isn’t generated. It does seem to be caching pages to Redis in the static folder.

Here’s what I have in config.php:

$config['speedy_enabled'] = 'yes';
$config['speedy_static_enabled'] = 'yes';
$config['speedy_break_async'] = 'no';
$config['speedy_driver'] = 'redis';
$config['speedy_redis_settings'] = [
    'static' => 'yes',
    'servers' => [
        [
            'host' => '/home/ucsdstage/.redis/redis.sock',
            'timeout' => '0',
            'password' => null,
        ]
    ],
];
$config['speedy_ttl'] = 3600;

Thanks

I did notice it was trying to write to the private_html directory for some reason. It should be public_html. (private_html is a symlink to public_html)

Yes, public_html was set to 755 and writable. Even after I set it to 777 it’s still exhibiting the same behavior.

So I’ve tried this on two different servers - stage and production - and it does the same thing on both. When using file caching, it is able to generate the correct utility files and static caching works fine. See screenshots: https://today.ucsd.edu/news_uploads/path_public_html.png https://today.ucsd.edu/news_uploads/path-public_html-static.png https://today.ucsd.edu/news_uploads/path-public_html-static-utilities.png

When I switch to Redis as the driver, it gives the prompt to regenerate files but then does nothing when I click on the regenerate link. Again, I’m configuring using sockets so not sure if this difference is causing the issue.

Not sure if this makes a difference, but we also recently migrated to new servers (and also moved the old database). On the old server, we were using Speedy with static file caching (not Redis).

Thanks

Redis with partial caching is working but it’s not redirecting to fully static cached pages

“maserati” is the name of the EE system folder. I’m not sure why FCPATH would have been modified. I do see index.php in the web root as well as in maserati. The one in the root directory defines the system path:

$system_path = './maserati';

The one in maserati doesn’t contain the system path.

Yes static caching is working now, I just had to change this line in the index_redis file to point to the index.php in the web root:

// No cached response, proceed with normal EE operations.
require_once '/home/ucsdstage/domains/stage-today.ucsd.edu/public_html/index.php';
exit;

Oddly the browser seems to be caching the static cache files, which is not good if the Speedy cache needs to be broken. I assume this probably has to do with some caching directive in my htaccess file and nothing to do with Speedy? Thanks

Yes, I found the htaccess directive that was caching html so now everything seems to be working as expected. I just had a couple more thoughts below and then I think we can close this ticket:

• Did you have any thoughts on how to modify the FCPATH variable? I’m not sure why there’s another index.php file in the system folder, but maybe just delete that?
• Not sure if you’re aware, but your email notifications for support updates doesn’t seem to be working.

Thanks!

Hi, here’s a video showing the homepage being cached: https://today.ucsd.edu/news_uploads/static-homepage.mov

When I go to look at the homepage item in Speedy, it is cached but doesn’t show up because the URL for the homepage doesn’t have a path. So the key for the item is apparently blank?

In the past when I’ve used disk caching, the homepage key will show up as just “static,” but now with Redis nothing shows up.

Hi, I tried using that build but it’s still doing the same thing - homepage is cached but the item doesn’t show up.

Also, it looks like I can’t access the dropbox link of the screenshot in comment #27: https://www.dropbox.com/scl/fi/7klwbuymppebpa41fuab6/Screenshot-2023-11-14-at-4.47.54-AM.png?dl=0

Thanks

Hi, yes, the same behavior persists and it doesn’t create a key named “home.” Here’s a video showing that the code was updated to the latest build you sent me, then when I cache the homepage, the key “home” isn’t showing up in Speedy: https://today.ucsd.edu/news_uploads/static-homepage-2.mov

I also tried using the url_override parameter which did rename the key, but it also caused the caching redirect to stop working. Thanks

I showed that line 504 in the video. It’s this:

$uriString = ee()->uri->uri_string() ?: 'home'; // If there is no URI, assume it's the home page.

Yes, it’s working for every page but the homepage. I can see the cache keys for all other pages and clear them with the cache-clearing rules. That’s all I really want to be able to do with the homepage. Do you know why clearing it using the tag parameter wouldn’t work?

Here is the tag in exp_speedy_tags: https://today.ucsd.edu/news_uploads/speedy-tags.png The double trailing slashes in the key doesn’t look right?

Hi, I tried that build and it still inserted a double slash at the end. I did confirm this new code was at line 555 of mod.speedy.php. But where is it calling reduce_double_slashes from? I don’t see that function anywhere:

return ee()->security->sanitize_filename(
            $this->utf8Decode(
                reduce_double_slashes(
                    trim($url, '/')
                )
            ), true);

I also did confirm that clearing the cache using the tag parameter does work when I manually remove the trailing slash from the database.

{exp:speedy:static tags="home"}

Hi yes, I can provide that but the staging site is only accessible on a VPN from certain IP blocks. I could probably get the server admin to add your IP.

I’m not sure if this would add a trailing slash? I can send the whole htaccess file if you want

<IfModule mod_rewrite.c>
 RewriteEngine On
 RewriteBase /

 # Removes index.php from ExpressionEngine URLs
 RewriteCond %{THE_REQUEST} ^GET.*index\.php [NC]
 RewriteCond %{REQUEST_URI} !/maserati/.* [NC]
 RewriteRule (.*?)index\.php/*(.*) /$1$2 [R=301,NE,L]

 # Directs all EE web requests through the site index file
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 RewriteRule ^(.*)$ /index.php/$1 [L]
</IfModule>

Hi, I edited the ticket with cp and ftp info. I temporarily opened ports so you should be able to access the site. This is not hosted on a Windows machine. It’s Alma Linux. I have not tried a fresh EE install to replicate the issue yet.

Thanks!

Actually I just tested this on staging and cache clearing using static/index does seem to be working now. (I was testing this on my local machine before.)

Yes, everything seems to be working now after testing. I just need to figure out the FCPATH issue but can work around that for now. Thank you for your help!