First of all thanks for the extension. It is nice to have the possibility to edit content objects while they are in the approval process.

We would like to extend it to make voluntary approvals possible. Now we have a setup
where an "author" (fewer privileges) can write an article that needs approval by an "editor" (more privs). Now we would like the "editor" to send an article he wrote for approval by
another "editor". Ideally both of them should be able to approve the article in the end.
As you might note this is less of a formal approval but just to cross check the articles on a voluntary basis. Right now this does not work because the articles of the "editor" get published right away, probably because he is in the group which is allowed to approve.

Where and how can we start to implement the desired behaviour?

best
Oliver

The best way to report bugs is actually to use our bug tracker: http://issues.ez.no. Thanks in advance :)

Its ok in my eyes. Its just a difference between american and british english.

Hi

I expanded the installation document a little to explain how to use it (will be included in the next release). The text is as following:

*Installation:


 

1. Copy this folder to <ez publish root>/extension/ezapprove2


2. Apply SQL in sql/<sql server>/schema.sql


3. Activate the ezapprove2 extension.


4. Clear ini, ini-override and tpl-override cache.


 

5. You must have a cronjob script which runs the workflow cronjob.


Easiest way to set this up is to add the following to


settings/override/cronjob.ini.append.php (create the file if it does


not exist):


 

[CronjobPart-workflow]


Scripts[]=workflow.php


 

Then run the following command at regular intervals from the eZ publish root directory:


 

php runcronjobs.php workflow


 

 

* How to use:


 

After installing the extension, go to the administration interface


 

Simple usage:


1. Go to setup -> workflows


2. Click on "Standard" workflow group


3. Click "New workflow"


4. Add a name like "My approval workflow"


5. Select "Event/Approve2" and click "Add event"


6. Select appropriate options for approval workflow


 

7. Go to setup -> triggers


8. Select in "content publish before" the "My approval workflow" and click "Apply changes"


 

For the "editor":


After he/she have edited content, it will now be sent for approval.


While it is awaiting approval, it will be visible in "My pending items" and


"Collaboration" in "My account"


 

For the "approver":


The content waiting for approval will be shown in the "Collaboration" part of "My account"


 

 

More advanced setups with approval of only some classes and so on,


can be done with the "multiplexer". See


http://ez.no/doc/ez_publish/techn...eference/workflow_events/multiplexer


 

 

Also note that you can get notification-email upon updates. You set this up by going to


 "My account" -> "My notification settings". Check "Approval2" in


"Collaboration notification" and click "Apply"


 

Note: This requires the notification cronjob to run.


http://ez.no/doc/ez_publish/technical_manual/3_8/features/notifications


 

Hi
The functionality is just great.Thx for the contribution!

The one step that I had to add in my workflow setup was that to add the exclude user group without which it was an infinite process and my article never got published!

But I am loving the features
Cheers
Pratibha

This extension is also used as part of the eZ newsletter solution

Nicely done Kåre.
An extra suggestion that I think many people would find useful is the ability for approval to only be needed if there is a change in certain class attributes. For example if someone alters a photo don't ask for approval, or if someone attaches a binary then do ask for approval.
I especially like the fact you can edit the object now too!