[Plugin: W3 Total Cache] Settings don’t get saved

I forgot to mention. When I click on “Save changes” the plugin says “Plugin configuration successfully updated”. Usually I use 0.8.5.2, but i tried also the current developer version.

Can you submit a bug submission from the support tab of the plugin as this is not a known issue.

I’m having the same problem as chrisss. I disabled all plug-ins and tried it again but same problem. Nothing on the error logs. I uninstalled it and then installed he development version. Same results. I’m at a lost.

I’m using w3 total cache with xcache

I did a bug submission and waiting.

Thanks.

Can you submit a bug submission from the support tab of the plugin as this is not a known issue.

frederick. I already submitted a report. Last i heard from you, you requested an admin account for the blog and server which I provided. I’ll submit another one and will include a link to this topic.

I also now noticed I can’t even save the Hide this Message. I click on it and nothing happens

I know you are busy but i really appreciate the help.

Unfortunately this issue can occur because the opcode cache itself caches the W3TC config’ file. Only testing on your server will help determine if there’s a workaround and frankly caching the settings file is good, but the opcode cache is supposed to check for file changes in order to avoid this issue. APC does a good job in this regard.

I followed your suggestion and went away with Xcache. I was running into errors trying to install APC so I went ahead with eAccelerator . I can see improvement already

<!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching using disk (user is logged in)
.

chrissss I hope you to fix you problem too.

fredericktownes
What are the best settings using eAccelerator? Any suggestions?

Thanks

What are the best settings using eAccelerator? Any suggestions?

Circumstances vary to much to just blindly give you suggestions. Sorry.

Thank you very much. PS i had another issue with ea not being able to select it. I was able to fix it following the suggestion here
https://www.ads-software.com/support/topic/413477?replies=14#post-1589645

THANKS AGAIN

I have the same issue where settings wont save. It happens on sites that are just running disk cache too. I even “empty all cache” to no avail.

Usually, I end up clicking “Save changes” until they do, 10-15 clicks later.

gregrickaby I suggest you check the logs for any errors. /var/log/httpd/error_log < this is the location where mine is located. If you havent just submit a bug report from the w3 total cache support tab option.

@invi2003 is correct. @gregrickaby sounds like you have a network-based file server, that is the cause of that issue.

While you are configuring w3tc, set apc.stat = 1 in php.ini

This is the default setting. It requires the cache to check for file changes on every request for a file, which is a performance issue that may cause you to experience decreased performance with the cache plugin enabled.

Stat on can also cause the problem of the cache settings and alerts being cached… which is an annoyance.

After you have tested and deployed, set apc.stat = 0 and you will see performance increase.

@playgod, I’m not really seeing amazing performance increases by toggling this setting.

FT, I think you may be ~somewhat~ correct. I changed my sites back to apc_stat=1 and there doesn’t seem to be much of a performance hit. I was going by the recommendations from php.net:

On a production server where the script files rarely change, a significant performance boost can be achieved by disabled stats.

However, it looks like w3tc performs best with apc_stat=1. I did have trouble with plugin and core upgrades with apc_stat=1 (automated upgrades with w3tc & wordpress, and manual upgrades of other php packages such as vanilla, phpbb, joomla and slideshowpro director).

It may be worthwhile to research apc_stat a bit more and see what can be done to allow the cache (either plugin or APC itself) to recognize when important files are changed, without the overhead of polling each script every time it is called. While the performance hit for a single server running a single script package may not be overwhelming, I’m sure it could create performance issues on a setup like mine, which has 30+ virtual servers running various PHP script packages on a single physical machine.

I don’t currently have the time to do a detailed performance comparison, but in general I see CPU load is about 2x greater under normal load when apc_stat=1 vs apc_stat=0. It’s still manageable at ~1.5 but I would prefer the normal load to be less than 1… it was consistently under 1 with apc_stat=0. Remember I am running 100+ PHP script packages on a single physical server with 5 IP addresses, multiple domains, Email, PHP, CGI, Perl, MySQL and PostgreSQL. So, any single measurable performance issue has exponential consequences.