Conversation
supportHi again, I managed to install the plugin after updating my php version (see my previous post ( https://wordpress.org/support/topic/fatal-error-when-activating-plugin-17?replies=2 ), but I cant’ seeem to be able to make it work. I tried a fresh install on localhost (XAMMP) and all went great, no error on install and posts/pages being changed as scheduled. However, when I go to a live server, nothing happens. I’m able to select date and time, but when the date and time that I set pass by, the pages or posts simply remain as they were… Any thoughts? https://wordpress.org/plugins/post-status-scheduler/
Hi! It sounds to me like the time on your server isn’t set correctly. I’d look in to that first. Hope that helps.
Hi, The server time is correct (I even echoed it through php to check out). And when I’m scheduling a page, the plugin doesn’t allow me to set a date/time prior to current date/time, so I think that part is working.
Andreas, I tried on a fresh WP install in the same server and the plugin still doesn’t work. I then tried on another hosting company and it worked. So it does seem it’s something related to the server. Are there any special requirements to get this up and running?
Sorry for the late answer. There should be no special requirements for the plugin to work so it is a bit puzzling. The plugin registers a cron job (the wp kind). Can you see if other WP crons are running as they should? Does the server have php-curl installed? Anyways it seems like a server environment problem and is very difficult for me to do anything about. I’m very sorry about this 🙁 You might try to create a proper cronjob to run the wp-cron.php once in a while and see if that works. Please let me know if you find out anything.
Andreas, After a lot of testing… I’m unable to find out the problem 🙁 Server date/time is correct and wp cron jobs are running properly. I did another fresh install, in the same server, with all the plugins I had on my other site and Post Status Scheduler worked. I’m guessing the fatal error I had during install ( https://wordpress.org/support/topic/fatal-error-when-activating-plugin-17?replies=7 ) somehow corrupted something. Uninstalling and installing Post Status Scheduler doesn’t change anything 🙁 You said the plugin registers a cron job… Uninstalling the plugin “unregisters” that cron job? Are there any database changes?
Sorry to hear that. The plugin schedules a cron everytime you schedule a post status change via the plugin, not when you activate the plugin. “I did another fresh install, in the same server, with all the plugins I had on my other site and Post Status Scheduler worked.” Is it now working you mean? Or is this on another host?
I have site A in server 1. In that site, I had the fatal error when I tried to activate the plugin; I updated the php version and was able to activate the plugin but unable to make it work. I then created site B on server 1; I tried several php versions but was unable to make the plugin work. I went to server 2 and created site C. Here, all worked ok from scratch. I then went back to server 1 and created site D, with all the plugins I have in site A (just to see if there were any plugin compatibility issues). I did not change the php version (it’s now running 5.4) and the plugin works. In site A (my primary site), hosted in server 1, it still doesn’t work, no matter what I do. My guess goes to something related to that initial fatal error during activation 🙁
Hi! It sounds to me like the time on your server isn’t set correctly. I’d look in to that first. Hope that helps.
Hi, The server time is correct (I even echoed it through php to check out). And when I’m scheduling a page, the plugin doesn’t allow me to set a date/time prior to current date/time, so I think that part is working.
Andreas, I tried on a fresh WP install in the same server and the plugin still doesn’t work. I then tried on another hosting company and it worked. So it does seem it’s something related to the server. Are there any special requirements to get this up and running?
Sorry for the late answer. There should be no special requirements for the plugin to work so it is a bit puzzling. The plugin registers a cron job (the wp kind). Can you see if other WP crons are running as they should? Does the server have php-curl installed? Anyways it seems like a server environment problem and is very difficult for me to do anything about. I’m very sorry about this 🙁 You might try to create a proper cronjob to run the wp-cron.php once in a while and see if that works. Please let me know if you find out anything.
Andreas, After a lot of testing… I’m unable to find out the problem 🙁 Server date/time is correct and wp cron jobs are running properly. I did another fresh install, in the same server, with all the plugins I had on my other site and Post Status Scheduler worked. I’m guessing the fatal error I had during install ( https://wordpress.org/support/topic/fatal-error-when-activating-plugin-17?replies=7 ) somehow corrupted something. Uninstalling and installing Post Status Scheduler doesn’t change anything 🙁 You said the plugin registers a cron job… Uninstalling the plugin “unregisters” that cron job? Are there any database changes?
Sorry to hear that. The plugin schedules a cron everytime you schedule a post status change via the plugin, not when you activate the plugin. “I did another fresh install, in the same server, with all the plugins I had on my other site and Post Status Scheduler worked.” Is it now working you mean? Or is this on another host?
I have site A in server 1. In that site, I had the fatal error when I tried to activate the plugin; I updated the php version and was able to activate the plugin but unable to make it work. I then created site B on server 1; I tried several php versions but was unable to make the plugin work. I went to server 2 and created site C. Here, all worked ok from scratch. I then went back to server 1 and created site D, with all the plugins I have in site A (just to see if there were any plugin compatibility issues). I did not change the php version (it’s now running 5.4) and the plugin works. In site A (my primary site), hosted in server 1, it still doesn’t work, no matter what I do. My guess goes to something related to that initial fatal error during activation 🙁