awhig

I’m having the same issue.

Please see my post at:

https://www.ads-software.com/support/topic/plugin-wp-super-cache-category-page-is-not-updated-when-new-post-is-added

Rich

I’m still trying to figure this out. I have 5 sites and they are all having problems with cached category and index pages not being re-generated.

All of them have 3600 seconds as the cache timeout, and most of them had the garbage collection set to clock 00:00, hourly (1 was set to timer 3600). I believe, my issue is with the cache timeout. It is not properly throwing out cached category and index pages, correct? I guess I don’t have to fiddle with the garbage collection settings, as that is not my main issue (that I know of).

I do not think this is related to preloading, as Preloading, only caches individual post and pages, correct?

I tried turning on debugging, but didn’t see anything relevant. I then changed the gc timer to 10 seconds, and kept checking the debug log, but never saw anything. If I change the cache timeout to 60 secs from its current 3600, and then revisit a category page, it finally regenerates it (It was last generate 4-27-2012). I then put back the cache timeout to 3600 and the timer back to 3600 (I guess).

I’m hoping by updating these options, I’ll jiggle something to cause everything to update properly…

I’m at a loss on how to get this to work correctly.

Thanks,
Rich

HI Donncha, thanks for the reply.

So, in order to mitigate this issue, I’ve put on the preload panel…

Refresh preloaded cache files every set to 720 minutes.

and Preload all posts.

I believe, my cached pages, should never bee older than 720 minutes then?

I’m still having issues, with the category and index 2, index 3, etc. pages. When I view source, they are showing:

<!– Cached page generated by WP-Super-Cache on 2012-05-09 12:12:50 –>

Today is 5-15-2012. My pages are outdated, and content that has been pushed off the home page, are no longer showing up anywhere, as the pages, have not been re-generated for 6 days.

How do I fix this?

Some more info, on the Advanced tab, I have Cache timeout set to 3600.
Scheduler set to Clock 00:00
Interval hourly.

Also, I’m showing the warning below. Can you tell me what a Supercache file is? Should I turn off preload mode? Is this the issue?

Thanks for any help.
Rich

Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.

Follow up info…

Some More Info: I see on my Advanced tab:

Expiry Time & Garbage Collection

Current server time is: 2012-04-25 18:23:40

Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.

On the Preload tab, currently I have Preload All, set and Refresh preloaded cache files every minutes, is set to 0.

The reason I’ve set this to 0, is because I believed Category pages would be updated, if a new post was added to the Category. Please correct me if I’m wrong.

Thanks for any help,
Rich

I see

[15-Mar-2012 15:41:12] PHP Warning: in_array() expects parameter 2 to be array, null given in …/wp-content/plugins/antispam-bee/antispam_bee.php on line 1658
[15-Mar-2012 15:41:12] PHP Warning: Cannot modify header information – headers already sent by (output
started at …/wp-content/plugins/antispam-bee/antispam_bee.php:1658) in …/wp-comments-post.php on line 95
[15-Mar-2012 15:41:12] PHP Warning: Cannot modify header information – headers already sent by (output
started at …/wp-content/plugins/antispam-bee/antispam_bee.php:1658) in …/wp-comments-post.php on line 96
[15-Mar-2012 15:41:12] PHP Warning: Cannot modify header information – headers already sent by (output
started at …/wp-content/plugins/antispam-bee/antispam_bee.php:1658) in …/wp-comments-post.php on line 97
[15-Mar-2012 15:41:12] PHP Warning: Cannot modify header information – headers already sent by (output
started at …/wp-content/plugins/antispam-bee/antispam_bee.php:1658) in …/wp-includes/pluggable.php on line 866

I tried changing the category title, and it still does not work for me.

It works for me on the homepage template, but doing the same thing for the category template, all I see is the standard category name title.

I first started off trying

%%category%% Archives %%page%% - %%sitename%%

but after this did not work, I simplified to

%%page%%

as a test, and still did not see any changes.

This is with Version 1.1.4 of the plugin, running on top of WP 3.3.1

Rich

Does anyone know if this was fixed in the latest release? I haven’t tried it yet…don’t want to mess with anything, unless it has.

Thanks,
Rich

I am having the same issue. SEO titles for my categories, where I put in a custom template (to show page #’s) never show up. Using version 1.0.3.

Thanks,
Rich

Titles do not work for me as well. Using Version 1.0.3.

Rich

I also consistently get errors from the plugin, yet the diagnostics says everything is fine (though I can see the error in the diagnostic response) BUT our posts have always, and continue to post to our FB page.

Here is what I see:

Check if your server can connect to Facebook

Sends a https request to Facebook to detect possible connection errors. Expects a code 400 / Bad request response.
Everything looks fine

Array
(
[headers] => Array
(
[cache-control] => no-store
[content-type] => text/javascript; charset=UTF-8
[expires] => Sat, 01 Jan 2000 00:00:00 GMT
[pragma] => no-cache
[www-authenticate] => OAuth “Facebook Platform” “invalid_client” “Error validating application.”
[x-fb-rev] => 450480
[x-fb-server] => 10.54.6.37
[connection] => close
[content-length] => 77
)

[body] => {“error”:{“message”:”Error validating application.”,”type”:”OAuthException”}}
[response] => Array
(
[code] => 400
[message] => Bad Request
)

[cookies] => Array
(
)

[filename] =>
)

Check if the SSL module is loaded

Facebook requires secure https transmissions. Therefore your webserver has to support SSL. Not all hoster, especially freehoster, offer this service.
Everything looks fine

I know, because when I turn on debug info for page caching, I see at the bottom of my page the following:

<!– W3 Total Cache: Page cache debug info:
Engine: disk (enhanced)
Cache key: _index.html
Caching: disabled
Reject reason: Requested URI has a trailing slash
Status: not cached
Creation Time: 1.739s
Header info:
X-Pingback: https://www.—&#8212;.com/—–/xmlrpc.php
Content-Type: text/html; charset=UTF-8
X-Powered-By: W3 Total Cache/0.9.2.3

I believe there is a bug in 0.9.2.3 that prevents the homepage from being cached with the reject reason that there is a trailing slash in the URI when viewing the debug info for page caching.(at least for me).

I believe this is fixed in 0.9.2.4. I am still running 0.9.2.3 due to other bugs in in .4 though.

Rich

When Frederick said:

>>This issue is fixed in the latest release.

Did he mean in 0.9.2.4?

I think he did, as the code that generates the reject reasons in .4 is vastly different than .3.

Rich

I see your point. I was relying on this info as debug info, instead of turning on the debug mode and was always using this info.

In any case, I hope .4 is fixed soon. I turned on debug in .3, and realized my home page isn’t even being cached because of a trailing slash in the URI. I think this is fixed in .4, but had to revert because of other issues it has. Looking forward to the caching of my homepage soon.

Rich

Yes, I saw this code and understand it is the trigger.

My question is *why* is this a trigger to hide potentially valuable/interesting information that previously was shown in the comments? It makes no sense to me.

I’d rather not uncheck the “I’ve tweeted” thing, since it will probably show the nag popup again (though I haven’t tried this).