|
Author
|
Message
|
|
gaga 66
|
Friday 24 August 2007 7:27:42 am
Hi, I've got collaboration set up with workflows, triggers and cronjob. An editor can submit an article and it appears in the administrators collaboration area. I'd like to be able to allow admin to edit an article before approving it. Things like small spelling errors should not cause an article to be disapproved. This doesn't seem to be standard functionality for ezPublish but I would view it as essential. Can anyone advise how I might set this up? I'd also like editors to get email notification when an article is approved or declined but this functionality isn't available either. thanks in advance
|
|
Nabil Alimi
|
Friday 24 August 2007 8:37:26 am
Hi gaga, One can check his content in the "My Account" Tab / Pending Items menu but i'm afraid that they aren't editable until someone with appropriate rights has approved or denied content.
My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr
|
|
Tony Wood
|
Friday 24 August 2007 8:53:54 am
It is probably worth adding this as a suggestion. As this is a much requested feature
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
gaga 66
|
Friday 24 August 2007 9:29:48 am
Added as suggestion: As cron is set to 15 mins there's awaiting period between approval and being able to edit. is there any way of being able to edit sooner after approval other than reducing cron times? What affect will changing cron to 1 min have?
|
|
J-A Eberhard
|
Friday 24 August 2007 9:31:46 am
Hi
This could be dangerous on the Business side.
If you can edit the content within the workflow and you have a workflow with more than one step, then the content validated by the first in line in the workflow could be edited by the second before it's published.
This edit feature should then be deactivated in multi steps workflow to avoid such problems.
My 2 cents.
JAE
Open Source Solution Provider
Open-Net Ltd Switzerland
http://www.open-net.ch
|
|
gaga 66
|
Friday 24 August 2007 9:38:42 am
Couldn't you just give all contributors/editors edit rights and simply allow a single admin publishing rights?
|
|
Tony Wood
|
Friday 24 August 2007 9:58:03 am
I think that in multiple workflow environments the edit should move the document to the start of a flow or override and keep it. For example.
1. Author -> Writes article
2. Editor -> Edits article for typos etc
3. Legal -> Reviews/modifies article
4. Publishing Editor - > Publishes it In this example you would not want the article to go back to the Author you just want the Editor to fix Typos, the Legal to make it legal and then the Publishing editor to make the final decision and set the time etc for go live. I think this feature is needed. Thoughts?
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Mark Marsiglio
|
Friday 24 August 2007 10:07:48 am
I have had a few clients that would benefit from Tony's suggested implementation. I thought it could be done with the multiplexer, but I think that the editing during the process would be best. To add to this idea, it would be nice if the content diff function were used during the workflow to show changes, if any, made by each step in the process.
http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions
|
|
Tony Wood
|
Friday 24 August 2007 1:11:43 pm
An inline diff feature would be very useful... I think the ability to approve or reject each diff would be very very useful.
I think a full audit trail would make this the best.. Wow it feels like Christmas... I feel like saying Dear Santa :)
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Xavier Dutoit
|
Friday 24 August 2007 10:44:09 pm
Albeit I don't have such complex workflows, I use sections to describes each stage (pending, approved, rejected...), and event to change the status (ie if an editor publish, it changes the status to pending), and a couple of views to allow to change the status. Each user group can have different read/write rights based on each section. It works, at least it's much easier to use than the default "collaboration" system (where the only options are to reject or approve). X+
http://www.sydesy.com
|
|
Tony Wood
|
Friday 24 August 2007 11:12:31 pm
Hi X, You see I really like that idea. I have only one issue with it. Sections are one of those really really powerful elements. I mean I want to use them for everything, but I know that if I do then they become unmanageable. So you get to choose with section.
- Do I use them for permissions?
- Do I use them for work flow?
- Do I use them for View display? I mean they just work really well.. I knida wish you could have multiple types of sections. So you could create them as you need them so you don't get stuck when with a thousand of them. Did I read somewhere that there were deprecated? or did I dream it? Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Heath
|
Saturday 25 August 2007 11:48:34 pm
Existing related issues
<i>http://issues.ez.no/6917
http://issues.ez.no/9023</i>
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|
