awhig
Forum Replies Created
-
I saw the CPU usage of my site doubling from 15-16% CPU to around 30% CPU in the daily usage log when I updated from 9.2.5 to 9.2.8 (I thought I’d be safe and wait to update after a few more releases when 9.2.6 came out).
I saw another post, http://wordpress.org/support/topic/w3-total-cache-creates-tens-of-thousands-inodes
and looked at my APC cache, and saw that the cache full count was very high, compared to how it was before upgrading. MY DB and Object cache are both in APC. There seems to be an issue with the DB caching mechanism.
Based on these 2 things, I’ve downgraded back to 9.2.5 until a couple of more fix releases come out :\
Rich
Forum: Plugins
In reply to: [W3 Total Cache] W3 Total Cache critical Vulnerability disclosedFor those whose page caching stopped working with the update to .5, someone has posted a fix to this. It is only for Disk: Basic page caching, which is exactly what stopped working for me. I’ve applied the fix and it seems to be working.
http://www.wmiles.com/2013/01/03/w3tc-cache-preload-for-version-0-9-2-5
Rich
Forum: Plugins
In reply to: [W3 Total Cache] W3 Total Cache critical Vulnerability disclosedI’ve reverted back to .4 and I still get no page caching.
This is not good!
Rich
Forum: Plugins
In reply to: [W3 Total Cache] W3 Total Cache critical Vulnerability disclosedI’ve updated to .5 and now all page caching is non-functional as TDF and Mediaink have reported.
Timestamps are always fresh and turning on debugging for page caching, it always reports “not cached”.
I’m using Disk: Basic.
I’m going to try and revert back to .4 as the load on my server is too high!!!
Please help.
Thanks,
RichMarking this resolved.
Oh man, I made your changes to my installation and its working beautifully.
My homepage now has been cached for over 10 minutes now. A NEW WORLD RECORD! I’ve never had it be cached for more than 2 or 3 minutes ever TOPS!
I really think this should be made a permanent change to the plugin.
If anyone is listening, please consider making these changes part of the official plugin release.
Thanks,
RichI think the solution stated in this thread is easier to do. Just change a setting on your FB App….
http://wordpress.org/support/topic/plugin-facebook-page-publish-error-occured-at-line-774
Also,
Maybe don’t even purge the selected page in the purge policy even when a “Pending” comment is received. We also get a lot of spam that slips through the filter, so we have to manually mark those as spam, since we moderate all our comments.
So, I guess my request not actually purge the cache unless a comment gets published, as opposed to just “received”.
Again, I’m not sure the WP API supports this, but if it does, then I think this makes more sense to do instead of the current functionality, which is to purge upon the receiving of a comment.
Also, sorry if I’m completely wrong on how w3tc is currently working. I haven’t looked through that part of the code, but just basing my suggestions on what I *think* is happening after trying to debug my caching issue.
Rich
The plugin is currently working for me, but I have a couple of issues with it that are becoming annoying to my users…mostly to do with defaulting the post to facebook checkmark for posts, that are being edited…
Does anyone know of another plugin that is being actively worked on that provides the same functionality…I”m currently looking through the catalog…
Rich
Nevermind…Somehow between yesterday and today when I updated to 1.2.8.4, the plugin was deactivated…Not sure what did it.
I reactivated it, and now I see the Google+ field on the user profile pages.
I also started noticing this a few weeks ago. Scheduled posts were publishing, but the homepage, etc. was never being refreshed. 3 days of posts were not showing up, because the homepage was never being refreshed (though, I have cache timeout at 3600 seconds), which is still confusing….
I ended up turning on the option:
Clear all cache files when a post or page is published or updated
to fix this issue. Which it did, at the expense of clearing my whole cache, which is what I was having to do manually, to get new posts to show up.
But now, I’m having load issues, so I’m turning it back off.
Hopefully, I don’t see the previous issue of the homepage never refreshing again.
If so, I will try to do as you say, and turn on the debug options and publish a test post…
FYI,
WP Super Cache handles this scenario with their option:
Only refresh current page when comments made.This stops the homepage from being purged when comments are made. Only the homepage though. The post that contain the comments is still purged.
Hi, Just an update. I updated to the latest version of the plugin yesterday 1.1 hoping my problem would be solved.
I turned off preloading all (5000+ posts), and set expiration for 3600 seconds, and GC to timer 3600.
I checked my category pages and they seemed to refresh correctly. I checked my pages after an hour or so, and I could see the timestamp on the generated pages be updated correctly.
Yay!! I then turned preloading all back on, and my issue returned. The plugin would start serving stale category pages. I checked, 1, then 2 hour later, the page was never regenerated.
I turned off preloading, and the issue went away.
So, I think my issue is related to preloading.
I believe, preloading is only suppose to affect individual posts, and pages?
Would there be any reason for this to occur? My theory, again because I’m not sure how the GC works, is that the process that does preloading, because it’s busy doing that, somehow blocks the GC process from properly marking pages as expired? Could this be possible?
Anyway, for now I’ve turned off preloading, and things are working nicely.
Rich
I’m still having this issue as well, with category pages. I have my settings set to cache timeout 3600, and GC Scheduler set to Timer 3600, and pages that are days old are being served.
As a test, I turned on debugging and set cache timeout to 30, and GC Scheduler set to Timer 60.
I look at the debug log and can see that the category page is being regenerated now, and the timeout stamp at the bottom of the generated page is new.
If I change the settings back to 3600/3600, my pages are no longer regenerated, and days old pages are served (my experience for the last several weeks)
How do I debug this?
What should I be looking for in the log?
I believe, with my regular settings of 3600/3600, every 3600 seconds, the GC should run, and mark any page that is over 3600 seconds old as expired?
I’m just guessing as I don’t know how the GC is implemented.
Is the GC responsible 1 thing, or 2 things?
1)Marking files as expired
2)Deleting expired filesI’m willing to put some extra debug statements in to find the issue, I just need to be pointed in the right direction.
The following functions look promising:
function prune_super_cache
function wp_cache_rebuild_or_delete
function wp_cache_phase2_clean_expiredThanks,
RichYes, I disabled it on a few of them as a test. I just checked, and I’m still seeing a cached category page, that says
<!-- Dynamic page generated in 0.243 seconds. --> <!-- Cached page generated by WP-Super-Cache on 2012-05-15 15:39:40 --> <!-- Compression = gzip -->My cache timeout is set to 3600 seconds, so I would assume this should have already been regenerated…
Scheduler is set to Clock 00:00, if that matters.At this rate, I’m going to have to manually delete the cache every day, on all my sites, in order to have up-to-date category and index pages…
Please help.
Thanks,
Rich