I have several plugins that deal with with scheduling of posts, but with my upgrade to 2.7 they're all broken!
Anyone know what changed in wordpress that's breaking them? Most of them are relying on the local date and not on the GMT date, but I don't see how that would break anything :(
I'm terribly sad that scheduling posts is not working the way it should.
Anyone know what changed with the time db from 2.6 to 2.7?
Could you be any less specific? ;)
What plugin? Have you asked the plugin author? What is "scheduling of posts"? If you mean future posting, WordPress has that built in.
tdo-mf, post draft schedules, image scheduler. Specific enough for you? :)
every single scheduling function of wordpress was fubar'd after the upgrade, I'm sure you've seen the dozens of posts and requests for help. I eventually had to open every scheduled post and save it again for it to show up when it was scheduled to.
The easiest way to tell what's going on is to see what's changed in the db schema, as several of schedule related plugins have more to do with straight mysql entries then going through wordpress. I've checked the 2.7 changelog, but there's no mention as to any changes to anything time related. I've done a comparison of 2.6 to 2.7's tables and I can't see anything that's obviously different. It took about a week for the loggging in/out nonce issue to show up in the changlelog, so maybe this is something that still hasn't been put into the codex?
So back to my specific question : anyone know what's changed with the time db from 2.6 to 2.7? Is wordpress handling the time functions differently now?
No, the time stuff is fine. The problems people are having with scheduling is the same one that it's always been: wp-cron. Some servers just don't like it.
One possible problem is that 2.7 uses a POST instead of a GET to activate wp-cron. Some servers apparently don't like that. This has been patched for the next version, but you can try it now and see if it helps any.
Look in wp-includes/cron.php, line 201. Change "wp_remote_post" to "wp_remote_get". That might solve your issues. Maybe.
Beyond that, 2.7 is actually much better at allowing wp-cron to get triggered, since it uses the new http API which tries several methods to make the connection, instead of the previous fsockopen-only approach.
mmm, no, I'm pretty sure that it's something do with what's in the db, and the only reason I say that is there's a good portion of my site that now has nonsense characters instead of commas or quotes. would that mess up the time?
this is called encoding of the text?
This topic has been closed to new replies.
