Publishing issue with ez3.3 beta 2, News Package

Previous topic

Developer

Next topic

Author	Message
Marco Zinn	Wednesday 10 December 2003 12:46:51 pm If you try ez3.3 beta 2 with the news package and have problems with publishing, read this: Please note, that the "news" package does not work as in beta 1, when you want to publish something. In beta2, there is a "before publish content" trigger with an approval workflow. I usually use the admin user to test betas... and even the admin user cannot publish content, because it needs to be approved by the editor user. Best option: Go to Setup->Triggers and remove the workflow from the first trigger. If you really want to use approval: You must have a running cronjob for the workflow to work at all. And you must know, that the passwork of the user "editor" is the same as for "admin". ez, please don't use approval workflows for the final release package. Marco http://www.hyperroad-design.com
Björn [email protected]	Thursday 11 December 2003 10:16:25 am well I think it was not wise that eZ implmented it because 1.) dumb users don't know how it by pass it and set it up 2.) expericenced users know it so they can easily implement it Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Marco Zinn	Thursday 11 December 2003 12:17:45 pm Hi Björn, I agree ;) That's why i wrote the post. Handling with beta releases is a hard job without these "traps". I was trying to edit a poll and noticed, that it was not published. I thought "A feature? Maybe you cannot edit an open poll". Then i saw the "pending" status and tracked it down. I'm sure, that most users will not have knowledge about setting up cron-jobs, because for low-end setups, you won't need it. Marco http://www.hyperroad-design.com

Author

Message

Marco Zinn

Wednesday 10 December 2003 12:46:51 pm

If you try ez3.3 beta 2 with the news package and have problems with publishing, read this:

Please note, that the "news" package does not work as in beta 1, when you want to publish something.
In beta2, there is a "before publish content" trigger with an approval workflow. I usually use the admin user to test betas... and even the admin user cannot publish content, because it needs to be approved by the editor user.
Best option: Go to Setup->Triggers and remove the workflow from the first trigger.
If you really want to use approval: You must have a running cronjob for the workflow to work at all. And you must know, that the passwork of the user "editor" is the same as for "admin".
ez, please don't use approval workflows for the final release package.

Marco
http://www.hyperroad-design.com

Björn [email protected]

Thursday 11 December 2003 10:16:25 am

well I think it was not wise that eZ implmented it

because

1.) dumb users don't know how it by pass it and set it up
2.) expericenced users know it so they can easily implement it

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Marco Zinn

Thursday 11 December 2003 12:17:45 pm

Hi Björn,
I agree ;) That's why i wrote the post.
Handling with beta releases is a hard job without these "traps".
I was trying to edit a poll and noticed, that it was not published. I thought "A feature? Maybe you cannot edit an open poll". Then i saw the "pending" status and tracked it down.
I'm sure, that most users will not have knowledge about setting up cron-jobs, because for low-end setups, you won't need it.

Marco
http://www.hyperroad-design.com