Marko Vasiljevic

Hello @raufomat

Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled, and see which one might be causing the issue?

Just want to confirm that is a specific option, and not the pure fact that the plugin is active.
Can you also share some screenshots?

Thanks!

Hello @cynops

Thank you for your feedback.
The (Requested URI contains query) means that the page you are trying to cache is not cached, because the URLs with queries are not cached by default by the W3 Total Cache, especially if Disk: Enhanced is selected.
This being said, what you see is the confirmation that the page is not cached.
Are you having any issues, and do you see that page being cached anywhere?

Do you have server-side caching?

Thanks!

Hello @giorgosd1

We received yoru email and provided feedback and instructions there.
Please continue the correspondence there so we can avoid duplicating the answers.

Thanks!

Hello @giorgosd1

This depends on where the website is hosted and the environment.

Most Linux installations manage Redis through systemd. Run one of the following commands based on your package name:

• sudo systemctl restart redis
• sudo systemctl restart redis-server

If your system uses the older SysVinit manager, use:

• sudo service redis restart
• sudo service redis-server restart

If you are unsure about this please check this with your hositng provder!

Let me know if this helps and if you have any additional questions

Thanks!

Hello @cynops

Thank you for your feedback.
Can you please try adding the /volunteer_calendar/ to Performance>Page Cache>Advanced>”Never Cache following pages field, save all settings, purge the cache, and let me know if the sub-pages are being excluded?

Thanks!

Hello @stevehale

Thank you for reaching out and I am happy to help!

We’ve received the email via the W3 Total Cache support channel and replied to it.

Please continue the correspondence there so we can avoid duplicating the answers.

Thanks!

Hello @nemuelv

Thank you for reaching out and I am happy to help!

1. Check .htaccess File (make backup)
W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
2. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– db.php (if exists)
– upgrade folder
– delete the w3-total-cache folder in wp-content/plugins/ (if exists)
3. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enable the minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.

Go to your dashboard and install fresh version of the W3 Total Cache!

I hope this helps!

Thanks!

Hello @leanca

Thank you for reaching out and I am happy to help!

Can you pelase let me know if the minify rewrite rules are added to your .htaccess file and in the .htaccess in the cache/minify/ folder?
Also, pelase check the install tab and make sure that the Rewrite URL structure option is enabled in the Performance>Minify settings

Thanks!