Schedule a post to be published at a future date: Does not work

I decided to do that hack with two different web host accounts so that the cron is hit every 30 mins. Just in case one host goes down then I’m still covered. Wicked :P.

But I found that these new posts weren’t sending Pings, from what I could tell at least. I activated Feedburner’s PingShot and things are golden again.

Duct tape and bubblegum holding this blog together–but it’s working! Thanks again :).

So to get to pingomatic you have to use Feedburner? Or are you skipping pingomatic altogether?

I just removed pingomatic from wordpress (leaving the space blank) and chose to do all pinging through Feedburner. You can leave pingomatic in wp though and just not check that option in Feedburner.

I’m letting feedburner handle it all because it didn’t seem like wp was pinging the timestamped posts for me.

Well it all worked. Cron’d a fresh post Sunday night. I’m happy now. :o)

Logs showed the server was still trying to get wp-cron and subsequently getting a 403 every time. Hacked cron.php to fix that:

wp-includes > cron.php comment out line 125:

124 continue;
125 //spawn_cron();
126 break 2;

Anyone know of a plug-in (or hack) that gives more future post options – such as creating a standby list of articles to publish if no post has been made in the past 24 hours, etc.?

No, but that’d be a good idea. Keep the upcoming posts from going live if you’ve manually published within x number of days. Good call. Did you try suggesting that in ideas?

Hello all,

is there a way one of the more experienced WP Users can summarize what i need to check if i am experiencing the same problem?

I have read all messages, but imho everything should work fine (which doesn’t).

So perhaps there is a way to check all necessary vars (phpinfo, etc) before calling an admin (i have read BOFH and i really like my life! ??

This is also a problem with the plug-in Registered-Only, although not WordPress’s fault, the plug-in secures all pages and requires users be login to access. But WordPress can’t log itself in to access wp-cron.php! Heres the fix to Registered-Only, if you are using that plug-in. Change the one and only function to be:

function carthik_bouncer() {
if ( $_GET[‘check’] != wp_hash(‘187425’) ){
if (substr($_SERVER[‘SCRIPT_NAME’], -12) != “wp-login.php”) {
auth_redirect();
}
}
}

In my case that was .htaccess rewrite rule. Before php 5.2.3 everything was working OK. After host upgrade timestamp posting did not work anymore.

I have rule to force users to main index page

RewriteBase /
RewriteCond %{HTTP_HOST} ^domainname.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.domainame.com$
RewriteCond %{HTTP_REFERER} !^https://domainname.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^https://domainname.com $      [NC]
RewriteCond %{HTTP_REFERER} !^https://www.domainname.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^https://www.domainname.com $      [NC]
RewriteRule .*\.(html|php)$ https://domainname.com/index.phtml [R,NC]

After excluding from this rule my host IP (IP in example is 000.000.000.000) WordPress start publishing scheduled articles again.

RewriteBase /
RewriteCond %{HTTP_HOST} ^domainname.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.domainame.com$
RewriteCond %{HTTP_REFERER} !^https://domainname.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^https://domainname.com $      [NC]
RewriteCond %{HTTP_REFERER} !^https://www.domainname.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^https://www.domainname.com $      [NC]
RewriteCond %{REMOTE_ADDR} !^000.000.000.000$
RewriteRule .*\.(html|php)$ https://domainname.com/index.htm [R,NC]

Something inside new php is different or my host makes some changes to server.

Anyway in my case problem resolved

After upgrading to 2.2.2 it seems that timestamping is now working for me (woohoo!). My host also did some upgrades in the past few hours (specifically to MySQL) so it may be that, I didn’t think to test before I updated wp.

I hope everyone else finds this fixed for them :).

Glad you got it working right, Terry. I’m skittish to go back and try it.

I was skittish too jonlandrum. I just installed wordpress in a separate folder (and database), did a test timestamped post, saw that it worked on that host and then upgraded the main blog.

“This is also a problem with the plug-in Registered-Only, although not WordPress’s fault, the plug-in secures all pages and requires users be login to access.”

Hah .. thanx for this advice, that did it. I deactivated all my plugins and hacks for the user control, and wp-cron is working right now …

Problem: Solved

Just have to find out a workaround like the one Steveorevo mentioned.

jonlandrum said that find the solution with this:

Just edit wp-cron.php, comment out these two lines:

‘6 if ( $_GET[‘check’] != wp_hash(‘123456’) )
7 exit;’
and set up an hourly Cron job executing wp-cron.php using a CLI php binary like this:
/usr/local/bin/php /users/home/USERNAME/web/public/wp-cron.php

And it seems that worked for Terry too.

But I don’t understand how to do it in wordpress 2.2.2. My archive is cron.php in which the most similar lines I have found are:

‘if ( $argyle )
fputs( $argyle,
“GET {$parts[‘path’]}?check=” . wp_hash(‘187425’) . ” HTTP/1.0\r\n”
. “Host: {$_SERVER[‘HTTP_HOST’]}\r\n\r\n”
);
}

function wp_cron() {
// Prevent infinite loops caused by lack of wp-cron.php
if ( strpos($_SERVER[‘REQUEST_URI’], ‘/wp-cron.php’) !== false )
return;’

What have I write exactly to fix the problem in those lines? I would appreciated any help, because I’m getting mad with this problem.