-
Posts
-
Hello,
We are an SEO SaaS platform that has a new feature which allows you to implement SEO changes on your website directly from our platform. We have a large number of customers who use WordPress and the W3 Total Cache plugin.
The feature works by adding a Javascript snippet to the customers website to implement the SEO changes made. We are having issues with the way that W3 Total Cache delays/alters the loading of the script. Is there a way to be able to stop our script being cached/pre-loaded by W3 Total Cache either by updating a setting or adding an additional tag to the script tag to ensure it’s ignored.
I look forward to hearing from you.Hello Sophie,
Thank you for reaching out and I am happy to help!
The W3 Total Cache can optimize the files if you configure the plugin to do so. In this case, I would need more details on what this file actually is, the website URL on which the issue occurs and how the plugin is configured.
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?Thanks!
Hi Marko,
I don’t think my question was quite answered. I can’t share clients websites however, I have recorded the following video to give more context- https://www.loom.com/share/5254729cd8194144a98235ed8fcd29c1
As mentioned we’d like to know if there is a way to exclude our snippet from being changed/cached/pre-loaded by W3 Total Cache? Either by updating a setting in W3 Total Cache or adding an additional tag to the script tag to ensure it’s ignored.
Hello Sophie,
Thank you for sharing the video.
While this answers a part of the question, I am unsure what is the actual issue.
Regarding your caching question. When the page is cached, the entire HTML is cached if the mentioned snippet is embedded, it becomes part of the HTML, and therefore it’s cached as a part of the page.
In ordered to exclude a specific part of the page from being cached, there are a couple of ways do do this. One way si to use Page Fragment Cache and wrap the part of the PHP code in the template with theleaving this part of the page fully uncached.
You can check more about the page fragment cache on our wiki page.
The alternative is to fire the specific part of the page with ajax which also bypasses the cache.
If you change the or update the content of the snippet and the cache is not purged the content will remain the same.
What kind of changes are making when it comes to the snippet? is it the actual content or the naming of the snippet?
Does the issue persist if you purge the cache after the snippet update?
Thanks!
- The topic ‘W3 Total Cache interrupting our snippet’ is closed to new replies.
