I’ve tried doing some research and right now I’m just fumbling around looking for an explanation. This isn’t your typical “missed scheduled” error.
What happens: I schedule a post in the future. It doesn’t show up on the site. I go into the dashboard and it says it posted, but even if I refresh (dumping browser cache) it still doesn’t show up. Then I go into the post, hit “update” and it *then* magically appears on the site.
Maybe it’s a caching issue? Now that I write it out I doubt it but I’ll take all the help I can get. I don’t think the WP Missed Schedule plugin will help because it never says missed schedule. Just taking a stab that it might be a cache config?
You should probably enable the debug log and watch it when the scheduled post is supposed to publish. It should report that the plugin is deleting the front page and other cached files.
I’m having a similar issue after installing 1.1. I’ve reverted back to 1.0 and will see if that helps.
What happens is that the scheduled post gets created, but the homepage cache isn’t cleared so the new pos isn’t visible on the homepage. For some reason this also causes the rss feed not to update & kills the automation of the site’s XML for google as well.
sephage – confirmed. I killed the plugin and all problems went away. I’d be interested to hear if there are any issues using the legacy 1.0. Thanks for confirming I wasn’t crazy. Any way to get feedback to the devs so a fix can be made?
Same issue for me. I schedule posts for around 7am the following day. On that day with a fresh browser, the posts are not there.
I clear the cache from Super Cache and then the posts appear.
Wasn’t WP-SuperCache updated not too long ago?
All – I can confirm that reverting back to 1.0 resolved this for me at 1WineDude.com (including reverting the .htaccess mod rewrite rules just in case they were different).
Not sure what is going on but I don’t have time to debug it right now so reverting and ignoring updates on WPSC until there’s more time for Donncha to review/test/sort it out.
I have exactly this – updated from 1.0 to 1.1 and now the cache is not cleared whenever a scheduled post is published (and I do have the “Clear all cache files when a post or page is published or updated” option enabled). I’ve changed no settings at all since upgrading, and now I need to manually clear my cache each morning.
Thank you all for posting this. I had same problem…it worked again after reverting to 1.0. When I enabled debugging, i was seeing two strange things:
1) on the browser I had that had a valid login cookie, doing a refresh of the homepage caused it to load a random post, unrelated to the home page
2) on the browser I had that wasn’t logged in, a refresh did nothing that was reflected in the debugging log.
So back to 1.0 for now! Please tell me if i can be of further help.
I tested this by scheduling a post and it worked fine. I enabled the debug log first and at 11:45am when I scheduled it there was a call to wp-cron.php and I saw this log entry:
Clearing cache for post 89497576 on post edit
And afterwards it logged that it was “clearing cache in” various directories.
I checked wp-content/cache/supercache/ocaoimh.ie/ and yes, the index.html and index.html.gz had a timestamp at 10:45am (Summer time vs UTC) which was correct.
That’s basically all I’m asking you to do if you have a problem with scheduling posts. Please try the debug log. If you want to send me the debug log then don’t send me reams of stuff. I won’t look at it. Edit the log and limit it to the scheduled time. Paste the log into http://pastebin.com/ and post the resulting URL to this thread.
Does this help? I posted this elsewhere before noticing this thread.
Like others here, scheduled posts are successfully published, but they don’t seem to trigger a clearing of the cache:
A post was scheduled to publish at 16:31:00, and did publish then. It could be accessed directly, but the main/index page was not updated/cleared.
16:28:08 /crain/wpsc11/wp-admin/edit.php Cookie detected: wordpress_logged_in_8530db1c189dc0fb8e3bf9a6bf8742e4 16:28:08 /crain/wpsc11/wp-admin/edit.php supercache dir: /#####/crain/wpsc11/wp-content/cache/supercache/####/crain/wpsc11/wp-admin/edit.php/ 16:28:08 /crain/wpsc11/wp-admin/edit.php No wp-cache file exists. Must generate a new one. 16:28:08 /crain/wpsc11/wp-admin/edit.php Cookie detected: wordpress_logged_in_8530db1c189dc0fb8e3bf9a6bf8742e4 16:28:08 /crain/wpsc11/wp-admin/edit.php In WP Cache Phase 2 16:28:08 /crain/wpsc11/wp-admin/edit.php Setting up WordPress actions 16:28:08 /crain/wpsc11/wp-admin/edit.php Not caching wp-admin requests. 16:28:09 /crain/wpsc11/wp-admin/admin-ajax.php Cookie detected: wordpress_logged_in_8530db1c189dc0fb8e3bf9a6bf8742e4 16:28:09 /crain/wpsc11/wp-admin/admin-ajax.php In WP Cache Phase 2 16:28:09 /crain/wpsc11/wp-admin/admin-ajax.php Setting up WordPress actions 16:28:09 /crain/wpsc11/wp-admin/admin-ajax.php Not caching wp-admin requests. 16:32:44 /crain/wpsc11/wp-admin/edit.php Cookie detected: wordpress_logged_in_8530db1c189dc0fb8e3bf9a6bf8742e4 16:32:44 /crain/wpsc11/wp-admin/edit.php supercache dir: /#####/crain/wpsc11/wp-content/cache/supercache/####/crain/wpsc11/wp-admin/edit.php/ 16:32:44 /crain/wpsc11/wp-admin/edit.php No wp-cache file exists. Must generate a new one. 16:32:44 /crain/wpsc11/wp-admin/edit.php Cookie detected: wordpress_logged_in_8530db1c189dc0fb8e3bf9a6bf8742e4 16:32:44 /crain/wpsc11/wp-admin/edit.php In WP Cache Phase 2 16:32:44 /crain/wpsc11/wp-admin/edit.php Setting up WordPress actions 16:32:44 /crain/wpsc11/wp-admin/edit.php Not caching wp-admin requests. 16:32:44 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 In WP Cache Phase 2 16:32:44 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 Setting up WordPress actions 16:32:44 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 Not caching POST request. 16:32:45 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 wp_cache_post_edit: draft post, not deleting any cache files. 16:32:45 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 wp_cache_post_change: draft post, not deleting any cache files. 16:32:45 /crain/wpsc11/wp-cron.php?doing_wp_cron=1338913964 wp_cache_post_edit: draft post, not deleting any cache files.
Thanks very much!
There’s something odd there. The wp_cron process thought the post was a “draft post” so it didn’t delete any cache files! I’m not sure how that would happen tbh. 🙁
Could it be that GC kicks in a moment too soon, somehow, before the post status goes from “future” to “publish” and so mistaking it as a draft? Just a guess, as I’m not familiar with the internals.
It happens the same to me since v1.1. If I see the homepage of my blog automatically logged in as an admin user, the last scheduled posts appear. I try to see the blog with another browser that don’t log into Wp-admin automatically and the last scheduled posts are missing.
Then I clear caché and the posts appear in both browsers, logged in and not logged in. It seems v1.1 only regenerates caché for logged in users.
Hope it helps,
jclandin – enable the debug log just before you publish something and see what files are deleted. If you want, post just the logs from around the publish time to pastebin.com and post the url here.
Any update on this bug? I’m having the same issue since the 1.1 upgrade. If it’s not going to be fixed soon I’d like to downgrade to 1.0 because scheduled posts are an integral part of our site. To downgrade, is there anything I need to do besides deactivate the plugin and then replace the 1.1 folder with the 1.0 folder and then reactivate?
- The topic ‘[Plugin: WP Super Cache] Issue with Scheduled Posts Not Showing Up’ is closed to new replies.