Workflow processes

Sunday 20 January 2008 11:18:32 pm

I´m confused. I really need help ... What is the problem in the workflows?

Thanks

Monday 30 March 2009 9:17:53 am

I have the same problem :(

Wednesday 26 August 2009 1:38:07 am

The answer is in the post from emiri above, there are several cronjob parts (group of tasks), and workflow.php is in the "frequent" part.
The whole point with several parts is that some cronjobs should be run very often, and some not.

It's more in depth explained here, and the page also shows what parts the different cronjobs are by default:
http://ez.no/doc/ez_publish/technical_manual/4_x/features/cronjobs/configuring_cronjobs

Further reading, where you get recommended crontab setup for linux/unix:
http://ez.no/doc/ez_publish/technical_manual/4_x/features/cronjobs/running_cronjobs

The syntax for running the cronjobs from command line is:

php runcronjobs.php [-s <siteaccess_name>] [<cronjob_part>]

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Thursday 27 August 2009 1:18:38 am

Hi there,

I've exactly the same problem. Here is the message I can see in my pending list :

process status "(4) Workflow event deferred to cron job"
current event "status : (4) Event deferred to cron job, event will be rerun
event type : ezapprove
description : Approve".

Is there someone how could help us on fixing this problem ?

I asked my web hosting provider to run a cronjob at midnight everyday, the cronjob should have been executed but I can't see my messages published in my web site.

It's very blocking for us, I really need help on this. And I must admit that it's very annoying to not have the possibility to see the messages and publish them direcly by a simple click of button from the admin console of EZP. When will we have a very simple way of working which can avoid us using cronjobs and complicated ways of functioning ?

If someone could help, it would be great !!!
Many thanks.

Saturday 29 August 2009 4:26:31 am

That class should be there, some things you can try:
* check autoload/ezp_kernel.php, and search for eZDB, it should be there and correctly point to lib/ezdb/classes/ezdb.php
* Make sure APC is disabled for cli, this can be done with apc.enable_cli=0 in php.ini which is the default setting. (You can check which php.ini file is used with "php --ini")
* Enabled debugging, use "php -e runcronjobs.php frequent -s <siteaccess_name> -dall"

BTW: I got some database errors as well here (not the same one though), and the reason was because I had forgotten to enable the mysqli (which I use in eZ Publish) extension in php.ini.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Monday 31 August 2009 4:49:05 am

Hello,

For me everything was solved due only to a misunderstanding of my web hosting provider who was not executing the runcronjobs.php as a php line command but more as a direct call to the file.

I don't know if this can help the other members of the forum who initially opened this discussion. If it's not the case, I hope solutions will be found for them. So please if someone can bring answers, thank you for them.

Just to try to give some clues to other members of the forum, I created locally a batch file (under my Windows system) and put in it this command line :

if you are running a Wamp server :

"C:\wamp\bin\php\php5.2.8\php.exe" "C:\wamp\www\my_website_folder\runcronjobs.php"
pause

NB : the C:\wamp\bin\php\php5.2.8\php.exe must be changed by the path to the php.exe of your Wamp server version

If you are running Easyphp, put this :

"C:\Program Files\EasyPHP1-8\php\cli\php.exe" "C:\Program Files\EasyPHP1-8\www\my_website_folder\runcronjobs.php"
pause

NB : the C:\Program Files\EasyPHP1-8\php\cli\php.exe must be changed by the path to the php.exe of your Easyphp server version.

Executing the batch file will let you see first if there are no errors (as the pause command freezes the display to let you read what happened during execution) and will allow you to examine if the publication has worked on your local front-office website.

I hope it will help.

Cheers.