Hello,
Before installing W3 total cache my user would be automatically logged in after registering (www.neliti.com). However now they are not. I suspect this is a caching issue. What can be done?
Thanks.
Hello,
Before installing W3 total cache my user would be automatically logged in after registering (www.neliti.com). However now they are not. I suspect this is a caching issue. What can be done?
Thanks.
Ah, didn't see this - W3 Total Cache.
I would uninstall W3TC delete the cache and any other files it may have left and then move the website. After that I would just reinstall and reconfigure it.
Trying using Auto optimize the only issue I have with that plugin is the caching is not that smart and it can be a drain on resources at times.
This will combine and minify all JS and CSS this will reduce the amount of http requests.. However, don't inline and differ all the CSS I don't care what Google says on this and the reason is you will miss out on caching and a lot of other benefits.
I'm running W3 in a load balanced environment with memcache, each server is accessing the same database so most options/settings and content are equal.
Occasionally I visit w3 settings and see that the settings I saved are different from what I set, I realized that it's happening on one server.
So I'm wondering if all the W3 options are saved to the database? That may help me determine the issue.
Thanks,
Robert
UP!!!!!!!!!!
Thanks Destac, I will do just that.
I am seeing these problems too (pages that should be redirected are getting cached), Will do a bit more research, I think it might be caused by a wp_redirect
that doesn't have an exit immediately following it... might be wrong as this is just my initial evaluation
Are you using the minification module?
I have same problem...
Maybe is related to .htaccess conf
i am getting this error with auto minify
Recently an error occurred while creating the CSS / JS minify cache: Url/Filename is too long: 1/xenword-2.5.1.05/admin/xenword. Max length is 20.
If you want to limit the allocated memory for the whole WP, do this: Controlling allocated memory for PHP
If you want to limit memory allocated for a particular file (particular process), use the following lines (ex. for edit.php
file) and put it into your wp-config.php
after wp-settings.php
line:
if( $_SERVER['SCRIPT_FILENAME'] == './wp-admin/edit.php' )
ini_set('memory_limit','48M');
I started to get the following Deadlock error in our logs. It seems to be related to W3 Total Cache.
[Wed May 20 20:47:15 2015] [error] [client 10.1.1.94] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE
ms1_9_postmetaSET
meta_value= '1' WHERE
post_id= 15076 AND
meta_key= 'dsq_needs_sync' AND
meta_value= '1' made by require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), call_user_func_array, dsq_request_handler, dsq_add_pending_post_id, update_post_meta, update_metadata, W3_Db->update, W3_DbCache->update, W3_DbCallUnderlying->update, W3_Db->update, W3_DbProcessor->update, W3_Db->default_update, W3_Db->query, W3_DbProcessor->query, W3_Db->default_query, referer: http://www.beachbody.com/beachbodyblog/weight-loss/how-3-day-refresh-strengthens-your-willpower?code=SOCIAL_BB_BLOG&linkId=14371499
I'm on version of 0.9.4 of W3 Total Cache. Is this an issue fixed in the latest version or is there a server setting we need to change?
From what I know, redirects should be called in the get_header hook.
I've programmed all my redirects that way and I'm facing no problems in a MU-setup, and also be sure to exit the redirect as Eddie said.
If you've programmed your own redirects be sure to check out when they're called and adjust those when possible.
Hi, i've disabled the CSS and JS minify to do my own and combine all CSS files to only one file. In that case WordPress need some additional CSS files if the user are logged in. So i only combine the file for users who not logged in.
Problem: W3T generate the cache to wrong time / with wrong markup. Sometimes it generates with the combined style and sometimes with the admin style (without that the user is logged in).
Also without my minify plugin i see this problem that sometimes are styles are cached from the admin bar, and the user is logged out.
Thank you both for your comments, and in one of the cases I'd also noticed the hook that was getting called wasn't get_header and read it should be.
However I didn't go this route since this issue also happens with plugins we don't develop, such as the domain mapping one, and probably others.
I don't think there's any case in which the W3TC, as it's working now, should cache the 301/302 and as such opted to deliver the workaround at the W3TC plugin instead of all possible plugins that might have the wrong hook.
The plugins should fix the issue, but W3TC shouldn't cache responses that will produce issues. 404 already has the exception, 301/302 have caused issues to me and other, but probably anything other then 200 shouldn't be cached.
If anybody runs into the same problem, there is an option in W3 Total Cache, under the Page Cache options called "Accepted query strings". In there just enter gclid
Same problem here, will you fix it?
Disable the cache for logged in users.
Page Cache >>> Disable cache for logged in users.
It might also be the caching modules you are running. List which ones you are running, this is commonly an issue with object or db caching.