Title: gosuser's Replies | WordPress.org --- # gosuser [ ](https://wordpress.org/support/users/gosuser/) * [Profile](https://wordpress.org/support/users/gosuser/) * [Topics Started](https://wordpress.org/support/users/gosuser/topics/) * [Replies Created](https://wordpress.org/support/users/gosuser/replies/) * [Reviews Written](https://wordpress.org/support/users/gosuser/reviews/) * [Topics Replied To](https://wordpress.org/support/users/gosuser/replied-to/) * [Engagements](https://wordpress.org/support/users/gosuser/engagements/) * [Favorites](https://wordpress.org/support/users/gosuser/favorites/) Search replies: ## Forum Replies Created Viewing 6 replies - 1 through 6 (of 6 total) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Schedule a post to be published at a future date: Does not work](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/page/3/#post-572356) * SOLVED DEFINITELY. It was a DNS problem. wp-cron.php upgrades posts by calling with a socket the host in get_option(‘siteurl’). This hostname is your blog. If you dns does not answer right to you internal server the connection will fail and wp-cron.php will be not called. To solve this in my “home” server i set up bind9 and set it to answer to the internal requests of my domain with 127.0.0.1. Now it work like a charm. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Schedule a post to be published at a future date: Does not work](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/page/3/#post-572352) * I think it’s not a problem with configuration of apache/mysql because if i call wp-cron.php directly it WORKS! * So the problem is that nobody calls wp-cron.php and probably it’s a WordPress bug. I’ll investigate on this. * the problem seems to be at the fsockopen step, i checked my php.ini file and i saw that it allows fsockopen functions. * If it was a configuration problem either calling directly wp-cron.php should not work…. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Schedule a post to be published at a future date: Does not work](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/page/2/#post-572348) * SOLVED: With a brute hack, finally i got this feature working again. Sorry for the last 3 posts, but i’m making a lot of test and i reported each single progress. To solve it: * chmod -R 775 * to set executable flag to each wp script. * Then edit wp-cron.php and comment the following lines: * #if ( $_GET[‘check’] != wp_hash(‘187425’) ) # exit; * #if ( get_option(‘doing_cron’) > time() ) # exit; * Then edit index.php and force the execution of wp-cron.php each time that the index.php webpage is loaded (yes i know that it will increase database calls… this is why it’s a brute hack). To do so change your index.php with this one: * * Now everyting should work, when the timestamp is reached && an user views your blog, it’s automatically updated with new posts. * Ps: probably there should be a better solution, but for now it works… * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Schedule a post to be published at a future date: Does not work](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/page/2/#post-572347) * I tried to execute directly wp-cron.php and it didn’t work. Then i edited teh file and commented out the following lines * #if ( $_GET[‘check’] != wp_hash(‘187425’) ) # exit; * Now when i start wp-cron.php it WORKS! It’ able to post automatically when the timestamp is reached. The only problem that remains is that it seems that wp- cron.php is not started automatically. In fact, if i start it, the blog is update with new posts, but it is not so if the script is not executed manually. * Does anybody know which file calls wp-cron.php? * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Schedule a post to be published at a future date: Does not work](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/schedule-a-post-to-be-published-at-a-future-date-does-not-work/page/2/#post-572346) * Problem not solved even if i do a fresh install… * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Scheduled post time messed up](https://wordpress.org/support/topic/scheduled-post-time-messed-up/) * [gosuser](https://wordpress.org/support/users/gosuser/) * (@gosuser) * [18 years, 11 months ago](https://wordpress.org/support/topic/scheduled-post-time-messed-up/#post-563758) * same problem in my blog with wordpress 2.2 Viewing 6 replies - 1 through 6 (of 6 total)