Docs

[windhover4]

I have a child version of the Education Demo installed. http://www.amerthai.com

Today I received notice that W3 Total Cache Version 0.9.5 Update is available. I updated and the theme crashed. See attached Screen Shot when crashed, and as it should be after I Deactivated W3 Total Cache.

[Jade]

Hi there,

Try to login through FTP then go to wp-content/plugins then delete the current w3 cache plugin then go back to the admin and reinstall it.

Let us know how it goes.

[windhover4]

I deleted original and updated installation through my FTP login. I then downloaded from WP the W3 Total Cache and activated.

I experience the same results, except the Home page was even blanker that with updated W3. See Screenshot.

I then deactivated the new installation of W3, and Emptied Caches and Home Page was restored. See Screenshot.

http://www.amerthai.com

[windhover4]

This reply has been marked as private.

[Paul R]

HI,

The login provided doesn’t seem to work.

Kindly check again and let us know.

For the mean time try clearing your plugin cache.

http://www.inmotionhosting.com/support/edu/wordpress/recommended-wordpress-plugins/clearing-cache-in-wordpress

Thanks

[windhover4]

That was not very helpful advice. My first disappointment with your support. I believe there is an issue with the updates of WordPress, X-Theme, and W3 Total Cache. If you look on the Facebook X-Theme Users Group page, there is much traffic on this issue. I think X-Theme now owes its subscribers a more definitive position on W3 Total Cache and increased support for dealing with this problem. I purchased and installed WP Rocket, and with a few clicks, my site before and after performance report on GTmetrix shot through the roof. I feel silly telling you guys things change. Otherwise, thanks for a great theme…so far.

[Rad]

Hi there,

I’ll forward your concern. Any caching plugin has the same effect regardless of Theme or plugins. Plus, it’s not our plugin but we can try helping users that have cache issues. The issue is not because of the Theme, but the cache itself.

Updates are related to the term recent or latest, like the files are updated and new. While cache is related to stale content or files (cache remains unchanged for a specific period of days, weeks, months). They are contradictory in meaning and purpose. Like if your site serves stale files while the running in the updated system, then there will be conflicts and that’s always expected if you have cache and CDN.

Caches are 3rd party features that theme has no control, and that applies to all themes and plugins. For example, one of the purposes of cache is to prevent script execution to improve performance. It will serve same content over and over and prevent script re-execution. Since theme’s scripts are not executing then it can’t directly control the cache.

It’s really a broad topic and maintenance, it can’t be done in an automatic way. It always requires users intervention by means of manually managing them. Cache purpose is to serve same content and resources permanently (as long as you’re not updating or adding changes to your site).

Thanks for understanding.

[windhover4]

Follow-up question. Do I recall that W3 was pre-installed by X-Theme? If I am mistaken, and it is causing the number of issues begin discussed on the FB user site, I still think you have an obligation to provide an update on problems being so widely experienced with the plug-in on your theme.

[Rad]

Hi there,

It’s not pre-installed or bundled, it’s only recommended and used as a sample on our Knowledge Base about Performance. There are many plugins, and it’s only normal to manually manage your cache on every installation and updates.

That cache plugin has the same effect on all plugins and themes, and even without X theme, you are still required to manually manage your site’s cache.

Based on my experience here in the forum, users that have problem with caching are the ones who :

1. Enabled caching while developing
2. Optimizing their site while developing
3. Updating their site

Optimization and caches should not be done along with development. You should only do that once you’re done developing your site. It’s like a finishing touch and polishing should be done on the end. Same goes for the updates, caches should be cleared and disabled during the update.

You’re introducing changes to your site and you probably want to see those changes, but cache will not let you, that’s why it’s recommended to only enable it when you’re done applying those changes.

Thanks!

[Author]

Posts