I am vexed and after much searching of the web I can not find a solution to the scheduling issue, so I turn to my colleagues, as I now admit personal defeat.
Given the number of returns I get from Google it seems to be a common problem however I have been unable to find the elusive needle in the haystack.
[b]Problem.[/b] Getting schedules and auto stuff to work
[b]Background. [/b] After launching my sites I had hoped that I could get a number of things done automatically. This would include scheduled posts and backups.
After installing the plugin BackUpWordPress I noticed that it was not firing and not doing it's funky stuff. This got me to investigate further.
It transpires the failure to launch seems to have something to do with the page wp-cron.php and inturn the inability of it to get back to the server.
This was confirmed based on this article [url]http://wordpress.org/support/topic/109363/page/2[/url]
and gave the response
[i]Warning: fsockopen() [function.fsockopen]: unable to connect to example.com:80[/i]
and further confirmed using the test further down the page where 2 lines of wp-cron.php are removed and you browse to wp-cron.php with a web browser.
if ( $_GET['check'] != wp_hash('187425') )
The result of this test was for the wp-cron to run.
Back to the hosts now and they report [quote] 'Our system administrators have confirmed that loopbacks are not allowed on our servers, this is now the same on all servers so I'm afraid it will not be possible to use this cron.'[/quote]
Yes, I could leave the two lines of code off the wp-cron.php but it has been suggested that this may get me into 'server resource issues' as my sites become popular. [url]http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/[/url]
[b]So, as the answer is always in the room, what does the floor suggest?[/b]
I do have access to a scheduler from my host to run a scheduled cron job. But using it to 'ping' wp-cron.php doesn't work because it is seeing the page as above and in turn not working.