Hello Nazanin,

It sure sounds like you have not yet successfully installed eZ Publish (re: problems with setup process).

Also you must only run the runcronjobs.php from within the eZ Publish root directory.

Worth noting that in most common use cases the choice between ezflow and ezwebin design extensions does not affect the workflow feature or functionality.

Also worth mentioning that eZ Webin is often the better choice for new users as apposed to the more complicated and less documented eZ Flow.

I hope this helps ...

Cheers,

Heath

Hello Heath

thank you for ur answer.u made things more clear for me! however i dont know what is wrong in my ezpublish installation!

infact now simply i cannot underestad why my workflows doesn't work , 

i created the right for adminstrator to be able to approve the comments,

in backend everything's correct , but when an anonymous write a comment it disapear in frontend, even i dont have it in my backend.

i looked everywhere for a solution and the only thing that i am sure about is that what i have done is correct! and i think i have missed something. that hadnt been mentioned in docs.

i would be very thankfull if u could help me.

Hello nazanin,

Your welcome. I'm sorry I don't know exactly what's wrong with your installation or the functionality your trying to use unsuccessfully.

Please try to be careful when saying things generically like "in backend everything's correct" as this statement is clearly false by your own reported details.

You should enable DebugOutput settings and review your eZ Publish logs (see: /path/to/ezpublish/var/logs/*.log) for errors when publishing new comments.

Also you should know that in approval workflows, comments (or other new content) are not available at all by default within the content tree. Instead you must approve content for publishing using the features available using the "Collaboration" interface under "My account" provides the review/approve/reject interface for the editors.

Also what version of eZ Publish are you using? I recommend using the latest available community build 2011.12

Also remember that new content can not be published until it is first approved in admin *and* the workflow cronjob part must be executed (which does the actual publishing; not real time).

I think you should search your eZ Publish installation files for the file 'runcronjobs.php' from within the eZ Publish root directory. Remember it should be available in the root ezpublish folder directly. If you can not find this file I might recommend re-installing from scratch or upgrading to the latest version.

I hope this helps ...

Cheers,

Heath

Hello Heath

thank you very much for ur answer , that was really helpfull ,

i found runcronjobs.php in my root ezpublish directory. and now i have all of my comments in my collaboration part. and i have approuved them as admin.

as u said they are not been published, then i run :  php runcronjobs.php   but they didnt get published.

so i ran another command: php runcronjobs -s ezProject group_of_tasks   that it give again "no script for execution".

i would be gratefull if you can help me if you know where i am doing wrong?

thank you

Hello nazanin,

Your very welcome. I'm pleased that your starting to make progress forward on your own. This is why I do this, I help you reach your goals, it's fun for me.

I think you need to run the workflow cronjob part as configured by default.

I *think* (sorry in a rush today) that you need to run this exact command:

php ./runcronjobs.php frequent

When in doubt, search the doc site via google site: keyword searches

http://doc.ez.no/eZ-Publish/Technical-manual/4.4/Features/Cronjobs/Configuring-cronjobs

http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/Cronjobs/Running-cronjobs

http://doc.ez.no/eZ-Publish/Technical-manual/4.4/Features/Cronjobs/The-cronjob-scripts#eztoc117713_12

Cheers,

Heath

PERFECT!!! finally it workssss!!

thank you very very much for ur support

Hello nazanin,

Your very welcome. I wish you the very best!

Feel free to ask for help again here in the future.

Cheers,

Heath