[wp-hackers] Future Posting Fix Request
computerguru at neosmart.net
Sat Jul 22 07:26:02 GMT 2006
> We spawn ours out-of-band so that the user doesn't have to wait for it
> to complete. Others kick their pseudo-cron off from an image tag or
> the like.
OK, can't we fall-back to pseudo image tags, or something? Or even make them wait.... I mean, it's worth it for the CGI users if one visit near the time of the publication is 2 or 3 seconds longer than normal. It's just _one_ time (right?), and in exchange their future-publication works....
So you can use it the way you already are, but if CGI is detected, fall back to this 'waiting way' and then from there to IFRAME.... foolproof, no?
About the cron jobs though - it _is_ the default for all CGI installations, isn't it? With PHP compiled into Apache, it's not always the default, but AFAIK, all CGI installations have it stock, no?
And IIRC, we're not using any of those commands you listed as being "blacklisted" on hosts, and safe mode exec _should_ only escape all commands in the strings associated...
>From the PHP docs:
>With safe mode enabled, the command string is escaped with escapeshellcmd().
>Thus, echo y | echo x becomes echo y \| echo x.
Neither of these should inhibit a simple command like
$ 0 1 * * 0,2,4,6 /usr/local/bin/php /home/user/wp/mycron.php >/dev/null
Leaving us home-free.....
More information about the wp-hackers