Marko Vasiljevic

Hello

Thank you for reaching out and I am happy to answer
We replied to your email on Mar 12 2024 and the issue was fixed and we never got a reply from you via the W3 Total Cache support channel.
Please check your email, and reply to the email chain.
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
First, we should confirm which option may be causing the issue. Can you please disable the settings one by one in W3 Total Cache, Performance>general settings, save the settings and purge the cache after each setting is disabled, and see which one might be causing the issue?

Thanks!

Hello Peter,

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

Since this public forum, I recommend you don’t share any sensitive information. Please reach out directly via this contact form, and share the information about your W3 Total Cache Pro subscription so we can check this for you.

Thanks!

Hello Rob,

Thank you for reaching out and I am happy to help!
First, we should determine which W3 Total Cache setting may be causing the problem in this case.
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?
Please start with lazyloading if it’s enabled and let me know if this helps!

Thanks!

Hello,

Thank you for reaching out and I am happy to help!
Yes, you can exclude specific JS/CSS in W3 Total Cache. Go to Performance>Minify>Advanced, and add the path to the file in “Never minify following JS files” for example:
/wp-config/plugins/some-plugin/some-js-file.js
Make sure to save all settings and purge the cache.
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
To completely remove the W3 Total Cache, please follow the instructions below:
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.

Thanks!

Hello Markus,

I am sorry for the issue you are experiencing with the purchase.
We’ve received your email via the W3 Total Cache support channel and replied to it.
Once again I am sorry about the inconvenience, however, please follow the instructions in the email and continue the correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Dmitry

Thank you for your feedback.
Ah yes, sometimes, depending on the server the nginx needs to be restarted in order for the configuration to update.
I’ve removed the previous replies with some sensitive details.
As I’ve mentioned before, W3 Total Cache utilizes the rewrite capabilities of the server, to serve the web images. W3 do not change the image extension or replace existing images.
So you will not see the extension changes, just toe content-type: header

Thanks!

Hello Florian,

Thank you for reacing our and I am happy to help!
Can you plaese ahre the W3 Total Cache version you are curretnly using?
This is not specificaly related to the plugins, and theme, but mostly to the server and server resources.
Can you please inspect the soruce, and check the network tab once the Conver all button is clicked, and see if there are any 404 ajax requests?
Additionaly please check the PHP allowed memory size.
Thanks!

Hello,

You are most welcome!

We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
Thanks!

Hello David,

Thank you for reaching out and I am happy to help!
The W3 Total Cache detects the Memcached if installed and if running. The notification indicates that the Memcached should be restarted
Check the service at the CLI/SSH: memcached-tool 127.0.0.1:11211 display and memcached-tool 127.0.0.1:11211 stats.
telnet 127.0.0.1 11211
should communicate with memcache and respond to status commands etc
Look if the service is running: ps afux | grep memc
restart the service if needed (as root/sudo): service memcached restart.

Hey Michael,

Thank you for reaching out.
We’ve received your email via the W3 Total Cache support channel.
We replied with some instructions so please provide more details there so we can assist you further.
Please continue the correspondence there so we can avoid duplicating the answer.
Thanks!

Hello Michael,

Thank you for reaching out and I am happy to help!
Just to confirm, you are trying to manage your W3 Total Cache subscription and you want your email updated for this?
If this is the case, please confirm this, and drop us a note directly via the W3 Total Cache plugin in Performance>Support or the contact form: https://www.w3-edge.com/contact/
So we can provide access to your account as this is a public forum.

Thanks!

• This reply was modified 9 months, 4 weeks ago by Marko Vasiljevic.

Hello,

We’ve received your reply.
Thanks! Can we please continue the correspondence via the support channel (email) to avoid duplicating the answers?
Thanks!

Hello,

Thank you for your patience and the details provided.
In 99% of the cases, there is no need to add anything manually so it’s all down to the server configuration and if the server allows the plugin to modify the files or not.
We cannot force this so in some cases such as yours, the server configuration prevents this.
I’ve checked the files and as I can see the rewrite is now taking place, and all the files look good in terms of not removing the characters. Can you please confirm this?
As for the CDN, and the minified files not being uploaded to the CDN, if you are using origin push, you may need to invalidate those files manually.
You should visit the page as logged in. That will find out which minified URLs are used by that page and the queue upload process of minified urls.
Go to the backend and check that the upload queue is empty. if not – process it.
visit page as logged in again. it should use cdn urls now.
Now you can purge the page cache and visit it as an anonymous user to check that cdn urls are used by page cached version too

I hope this helps!

Thanks!

Hello,

Thank you for reaching out and I am happy to help!
The W3 Total Cache can also process background images and lazyload them. In some cases, the theme or some other plugin, or the way those images are added are also lazyloading those images, and doing this with the W3 Total Cache also can cause conflict, for example:
div class="footer-content lazy" style="background-image: url("https://guillaumelaccordeur.ca/wp-content/uploads/2021/06/Pied-dune-pianiste-et-pédales-du-piano.jpg");" data-bg="url("https://guillaumelaccordeur.ca/wp-content/uploads/2021/06/Pied-dune-pianiste-et-pédales-du-piano.jpg")" data-was-processed="true"

This being said, you can try and disable the option in Performance>User Experience Process background images which will prevent W3 Total Cache from lazyloading them, and if that does not work, simply add the URLs of those images to Performance>User Experience>Exclude words: field. Make sure to save all settings and purge the cache after each setting is changed.

I hope this helps!

Thanks!

Hello,

Thank you for your feedback.
Let me investigate this more and check all the details and I’ll get back to you once I have more information on this.
Thanks!

Hello,

Thank you for your feedback.
Is there a reason why the Rewrite structure is disabled is disabled? Are you having issues with the rewrite on your environment?
How it should work is when the Files are minified (manual or Auto) they should be stored in the /cache/minify/ folder if you are caching to disk.
the Rewrite structure is disabled, which may also be related to the gzip compression. You should also check if you have zlib enabled and that may be causing double compression.

I cannot replicate any of those things you mentioned as the files are minified correctly, gzip is enabled and the files are uploaded to the CDN.

When it comes to the javascript errors, I can confirm that the W3 Total Cache does not remove anything from the files when minified, so you may want to disable minify and see if any of the files are corrupted or if you are getting the errors in the console.
You should also provide details about your environment, the setup, the PHP and the wp version, the type of server, and the plan with your hosting provider.

I also want to mention that the replies will not be faster if you ask the same question in multiple channels, like here, via the plugin or the chat. Please understand that some issues are very specific to the environment and the server configuration and cannot be easily replicated.

Thanks!

Hello Allen,

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

The settings are stored in wp-content/w3tc-config/master.php. When the W3 Total Cache is temporarily disabled, this file is not removed. This being said, if the plugin is disabled and then enabled again, the settings will remain the same so you won’t need to re-configure from the start.

Thanks!

Hello Emiliano,

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

The general rule is that you should not cache the pages for logged-in users, simply because of the reason you mentioned. Once cached, the pages will show for the next visitor as cached. This may lead to the sharing of some sensitive information.

You cannot have separate cached pages from logged-in users and non-logged-in users. And even if that is available, you should have a separate cache based on the user to avoid sharing some sensitive/account details. This means, more caching, and more server resource consumption. Not to mention that the separate user caching would have to be based on the data that the user provides, and we cannot collect this data due to the GDPR rules.

However, W3 Total Cache is an advanced plugin for a reason, and you can achieve what you need, but this means some specific configuration.

As a guideline, you should disable caching for logged-in users and only allow caching for subscribers/customers (If this is the user role). Next, Browser Caching is a big NO in this case, so you should modify the Browser Cache for the HTML and set the expires headers to not cache and no-store. This will also impact non-logged-in users.

And of course, any pages with sensitive information like checkout, cart, or account should be excluded from the cache.
The login/logout is also something that should remain dynamic, so this depends on the plugin you are using for this. and you can use Page Fragment Caching, and wrap the PHP code for the login/logout with the mfunc to exclude that part of the page from being cached. Alternatively, you may use AJAX call for login/logout.

to direct your question directly, There is no way to only cache a couple of pages for logged in users. There is no option to add pages to cache only to exclude them from being cached.

I hope I explained this and let me know if you have any other questions.

Thanks!

• This reply was modified 11 months ago by Marko Vasiljevic.