lee carroll wrote:
Hi BMur,

We got ourselves into a state over this. However we ended up thinking
it was a good thing. Although still not sure 100%

the reasoning is

editor 1 edits the page
editor 2 deactivates the page
editor 1 promotes their changes live
editor 2 has in effect had work over written

by freezing the deactivate you avoid this. Once an edit begins changes
by another user should be "locked" out, including deactivates.

hth

lee c

On 3/15/07, BMur <[EMAIL PROTECTED]> wrote:


Michael Wechner wrote:
>
> BMur wrote:
>>>Hello,
>>>
>>>I'm using Lenya 1.2.4 and I've noticed that the "Workflow"->"Deactivate" >>>menu item is greyed out if the page has been edited but not submitted and >>>published (or rejected). Is this the intended behavior and if so does
>>>anyone know why it works like this.
>>>
>>
>>AFAIK this is the intended bahaviour because deactivate means to me that
>>this page exists as published page. If it was never published, then
>>there is nothing to deactivate.
>>
>>Is it possible that you are rather refering to "delete"?
>>
>>HTH
>>
>>Michael
>>
>>>  If the page has child pages I could see
>>>not allowing a deactivate however if there are no children I don't see
why
>>>the deactivate isn't available.
>>>
>>>If someone knows that this is the intended behavior please help me
>>>understand why, otherwise if there isn't really a good reason for it to
be
>>>working in this fashion and someone knows how to always make the
deactivate
>>>available (assuming the page has been published) please let me know how.
>>>
>>>Any advise/help would be great.  Thanks, Brad
>>>
>>>
>

No, I'm not referring to delete however my wording was terrible (sorry). I
should have included that this occurs after already publishing the page.
So, if I publish a page I can deactivate it, however once I edit the page again in the authoring environment I won't be able to deactivate the live version until I publish the edited version of the page in authoring. IMO,
if the page is in a live state in the Live environment deactivate should
always be available regardless of what state it's in in the authoring state.

Your email says 1.2.4. Someone changed the subject to [1.4]. Which is it?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to