I’m having the exact same problem, and no, it’s not resolved. I’m following two tickets on TRAC about this:
http://trac.ww.wp.xz.cn/ticket/3565
http://trac.ww.wp.xz.cn/ticket/3742
When I am editing my website online in log in, the posts aren’t appearing in the main website that my members use.
Actually, what this thread is about is future-dated posts that never go live.
But no one has come up with a fix yet, right?
Not that I’m aware of from reviewing the mentioned Trac threads.
What’s odd is I future-dated one last night and it showed up fine this morning as expected, so we can’t say it is categorically broken for all.
You might want to contribute to the trac articles with your server details to help narrow it down?
Are you suggesting that I might actually know my server details? *grin*
Lol, touche’
If you’re feeling zesty, you could build a phpinfo.php file with contents:
<?php php_info() ?>
Upload it to your site and hit it with a browser. That’ll tell you (among other things) things about versions of apache and such.
Or you could ask your host for the details (which is a lot easier if your host is helpful)
It’s an issue on occasion with wp.com and the WPMu software as well. 🙁
It’s not specific to 2.1.2.
But it is specific to the 2.1 branch. 2.0 doesn’t have this problem (as far as I can tell).
Grrrr… tried the phpinfo thingy and all I got was a blank page. I’ll have to have my web dude look at this next week. I hope someone comes up with something brilliant soon, because I truly depend upon future dating posts to keep things running smoothly. 🙂
Ditto. The most dificult thing about fixing this is that the vast majority of folks don’t seem to have the issue, so it’s almost impossible to mark as a bug in WP. There’s the guy who started the TRAC thread (Trent), a couple others who have posted there, and the two of us. If there are others, I haven’t seen their comments on this forum or at TRAC.
I’ll throw my hat into the ring. I did see someone, somewhere, had a solution with WP’s cron files not having the right permissions. But I’m still stuck and it still doesn’t work 🙁
Yeah, Trent mentioned that on one of those TRAC threads, but there was nothing about which specific files had the wrong permissions. wp-cron.php doesn’t need any special permissions to work.
And nor does includes/cron.php (to my knowledge). Maybe I should roll back to 2.11 or even earlier…
No! Oh, golly. Please don’t do that. Roll back to the 2.0 branch if you must, but don’t roll back anywhere in 2.1. It’s not safe. :o)
