Posted 1 year ago #
Hi, I upgraded to 3.0.1 but there is still this really annoying bug with scheduled posts: Missed Schedule.
Is there a way to solve that problem? I can't schedule my posts on my blog and this is a big issue... Am I the only one having this problem?
Thanks for your help!
Have you tried:
- deactivating all plugins to see if this resolves the problem? If this works, re-activate the plugins one by one until you find the problematic plugin(s).
- switching to the default theme to rule out any theme-specific problems?
Posted 1 year ago #
Hi esmi, I deactivated all the plugins and it didn't change anything, I still get the 'Missed Schedule' bug.
I also modified cron.php and changed thr value from 0,01 to 5 and it changed anything neither.
Why the theme could be the cause of this bug?
Some themes have been known to cause problems in the Admin and related areas. Changing to the 2010 theme would help to confirm whether this was the cause in your case.
To the best of my knowledge, there's no known scheduling issue in WP 3.0.1 (although a complete re-upload of a fresh copy of the wp-admin & wp-includes folders wouldn't come amiss - especially if you carried out an 1-click auto-upgrade), so that just leaves plugins, theme or a server-specific problem. Try resetting the plugins folder by FTP or phpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.
Posted 1 year ago #
Hi esmi, I think I found out. My site is password protected... So I guess everything will work fine when it will be open. But how would I imagine that could be the cause? ...
Thanks for your help, now I'm gonna check my theme like you suggested, just in case ;)
Password protection shouldn't create a scheduling problem - though it could depend upon how you've password protected the site.
Posted 1 year ago #
was this problem ever resolved? I am having the same issue.
Posted 1 year ago #
I too have the issue and have tried all ideas above and still have sames issues :-(
Posted 1 year ago #
Hi, I still have the problem... Not resolved, sorry...
Posted 1 year ago #
Same here. I used this plugin to fix it http://wordpress.org/extend/plugins/wp-missed-schedule/
I used to have my site password protected via .htaccess and it caused some problems. But when I removed the password protection, I did not encounter any more issues.
Posted 1 year ago #
Thank you very much Te Calleja, I'm gonna try it!!
I wish WordPress could correct this bug without the use of a plugin...
Thanks a lot! :)
Posted 1 year ago #
Hi Te Calleja,
I tried this plugin and still have the problem.
We have two servers for which we use worpress.In One server, the schedules was failing and in the other one(test server) , it is working fine.
When I added this plugin in my test server, schedules started to fail.
I have not tried in the other server though, wanted to test it first in my test server.
Posted 1 year ago #
I just moved my blog to new hosting under an Apache2 completely configured by me, so I assume there is something going on causing this, though I can't seem to find out exactly what that is...
The plugin wp-missed-schedule worked perfectly for me.
Maybe one day I'll get to the bottom of it.
-Dan
Posted 1 year ago #
I too have the issue and have tried all ideas above and still have sames issues :(
Posted 1 year ago #
Yup, me too. I've used 'WP Missed Schedule' to get things to post but it seems to be incompatible with the plugin that emails posts. I need a better fix for this.
Posted 1 year ago #
I've had success making the changes suggested here
http://wordpress.org/support/topic/missed-schedule-scheduled-posts-not-publishing-with-27/page/2
Posted 1 year ago #
Hi, I tried to make the timeout longer in cron.php (0.01 to 5sec), but it didn't help.
However, using this plugin: WP Missed Schedule Version 2010.1226.0246, did work. If you use WP super cache beware that wp-cron.php might not be called as WP Super Cache precomputes .html files.
In that case, you might have to call fetch site.com/wp-cron by hand, or with a cron job (wget). I still don't know what's causing this to start with, but if I ever find out I'll post an update. Good luck to all.
Posted 1 year ago #
Update: the trouble spot was that at some point, I had the W3TC plug-in installed. Even though it was deactivated, WordPress was still using wp-content/db.php and wp-content/object-cache.php (stuff was going through it). Renaming the files did solve the problem in this case.
This topic has been closed to new replies.
