On Jun 15, 2010, at 3:46 PM, Unger, Richard wrote: > Hi Everyone! > > We have been testing the Activation Workflow (Magnolia EE Tomcat Bundle, > v4.3.2, under Windows), and have found 2 Issues (our point of view): > > 1. Editing Content while page is in activation workflow > > If a page is activated, it enters the activation workflow, and is sent to the > “publishers” inbox. However, the publisher cannot directly edit the page by > clicking on it from within the “inbox”, for example to quickly fix some typos.
Yes, the publisher is not expected to edit the page. Just to approve it or send it back to the editor. > The publisher, assuming he has rights to edit the page, can find the page in > the website repo, and edit it. However, if he then publishes the page from > within the Inbox, the originally submitted version is published. The changes > made do not show up on the live system. Indeed. The publishing process starts when editor clicks on "activate". At this point page is versioned and the version created in the process is what gets published. If the publisher wants to edit the page, he would have to cancel the activation, edit the page and start the process again. The reason for versioning the page, is to make sure, that it is the page as it looks at the moment when editor clicks "Activate" what gets published in the end and not any other interim changes made by other editors and the request have been made to activate the page and before the publisher clicks on "proceed". If this is not what you want, simply disable the versioning and then it will be the page as it looks when publisher clicks "proceed" what will be published instead of what editor has seen when she clicked "activate". > > This is because the first step of the activation command-chain is to create a > version, which is referenced from the workflow work-item. > Our question: What is the logic behind this? Would it not be better to create > the version at the point that the publisher chooses to publish, ensuring that > the most recent content is sent to the live system? > Is it really desirable that the workflow has to be terminated (cancelled, or > rejected back to the editor) to make the smallest change? I believe I described it above. As for my personal take, publishing process is not a trampoline (as a friend of my keeps saying) and editor should be sure this is what she wants to publish before clicking the "activate" button. There is also a possibility to create a multistage review/publishing process using the workflow where once the editor clicks "activate" no versioning would happen, just start of the workflow and say reviewer would be notified and only after the reviewer possibly fixes the typos on the page and clicks "proceed" the versioning would happen before final approval by the publisher. Or you can set up even more complex (or simple) workflows. > > 2. Status Indication is incorrect after edits during activation workflow > > This second issue is closely related to the first, but is in our opinion > definitely a bug: > If the page is edited while it is within the activation workflow, the edits > will be reflected on the authoring system, but the activation workflow will > publish the original version of the page, regardless of the edits, as > described above. Yes and I described above why is that and that you can reconfigure the behavior should you with to do so. > The problem is that the status indication will change to “green” when the > activation workflow completes, even though the version published is not the > most recent one. > So this creates a situation where the page is marked as green on the > authoring system, even though it is not the same version as on the live > system. Is there a reason for this, or is it a bug? Yes this is a bug. The status should be amber (modified). Please create an appropriate Jira issue for it. Thanks. Cheers, Jan > > Regards from Vienna, > > Gerald Madlmayr and > Richard Unger > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- - Best regards, Jan Haderka, PhD. Magnolia International Ltd. http://www.magnolia-cms.com You should join us at Magnolia Conference 2010: http://www.magnolia-cms.com/conference http://twitter.com/magnolia_cms http://facebook.com/Magnolia -------------------------------------- Magnolia® - Simple Open-Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
