Workflow status change NOT Working.
Fri, 26/02/2010 - 19:40
Hello all,
Have been using the "workflow" status change module (draft - public) for about 6 months but recently I have noticed that its stopped working. Regardless of whether I leave the default 00:00 time or not my articles remail "drafts" and do not become "public" unless I schedule immediately and do not specify a date and time.
Any ideas as to what is causing this problem would be really appreciated.
Tue, 02/03/2010 - 17:41
#2
Cron not running
I checked the status and it hasn't run for two and a half weeks so I guess this has been the problem. I tried to run it manually but it failed.
I, or more to the point my slightly more technical colleague, will try and set cron up again and I will get back to you.
Thanks for your help.
Fri, 05/03/2010 - 01:10
#3
still not working
We set up a crontab file with the following entry:
0 * * * * wget -O - -q -t 1
Our /cron.php file displays as blank in the browser which is correct according to the cron video on http://drupal.org/cron#help but it was displaying like this before when we had no crontab entry.
It still says failed to run when we try to run it manually.
Could it be a DNS issue?
Fri, 05/03/2010 - 10:52
#4
I don't think your problem is initiating cron to run
I don't think your problem is initiating cron to run. I think your problem is that your site somehow fails to successfully complete when cron is initiated.
If you visit .../admin/reports/status and click on run cron manually, what happens? You should be redirected back to .../admin/reports/status with a message "Cron ran successfully".
If you don't see this message, then your site is running into problems or errors when it is trying to execute scheduled tasks. In which case, your PHP or web server logs may be useful.
Please let me know how you go.
Fri, 05/03/2010 - 15:59
#5
I am re-directed to
I am re-directed to ./admin/reports/status but the message is "Cron run failed."
Tue, 09/03/2010 - 10:23
#6
that message confirms an issue with cron running on your site
Well, that message confirms an issue with cron running on your site. Unfortunately, it doesn't point to where the problem is.
There can be any number of modules which are scheduling tasks via cron which might be causing the issue. At this point, it's a case of trying to narrow them down as far as practical.
Would it be possible to selectively temporarily disable/enable modules (or groups of modules) until you can run cron successfully? That would hopefully point to the module causing the issue.
Tue, 09/03/2010 - 18:27
#7
Hi Beng thanks for the
Hi Beng thanks for the advice, willl give it a try at some point but for now I will publish article manually.
thanks again!
Thu, 11/03/2010 - 10:10
#8
...
Hmmm...okay, but please be aware that cron is not working on your site and this may impact other functions of your site which depend on cron (if there are any). Hopefully it won't be too much impact.
Hi,
The Workflow module relies on cron to make scheduled state changes. If you schedule a state change for time T, the new state won't take effect until the next cron run after time T.
To confirm or test this for your site, please reproduce your issue, then visit .../admin/reports/status and click on the link run cron manually. Then verify whether scheduled state changes occurred or not.
On a more general note, you may also need to ensure cron is running more frequently than once-per-hour on your site.
Please let me know if this resolves your issue or whether it still persists.