Thanks, Annie.
I have applied the patch and everything seems to work fine. This is not
very satisfactory for me yet, because i could not reproduce the strange
behaviour in a proper fashion. It just went wrong from time to time. I
think i'll just wait and see what happens.
Do you happen to have a way to reproduce this bug and test the patch?
Kind regards, Robert
Annie Dumont wrote:
Hi Robert, hi Andreas, hi all,
Andreas Hartmann a écrit :
Robert Goene wrote:
Hi,
Some of my clients are experiencing problems with the 1.2.1 version
of Lenya: when a document is deleted without deactivating it,
That shouldn't be possible. Maybe there's a problem with the workflow
configuration? If deleting without deactivating is allowed, the
problem you describe is inevitable.
I had the same problem with my lenya version 1.2.3.
See the file [your_publication]/config/workflow/workflow.xml
If you can delete without desactivating maybe you have these lines :
<transition source="authoring" destination="trash">
<event id="delete"/>
<condition
class="org.apache.lenya.cms.workflow.RoleCondition">edit</condition>
<assign variable="is_live" value="false"/>
</transition>
Nowhere it is said that the the is_live parameter has to be at false.
So instead of the previous code insert another condition :
<transition source="authoring" destination="trash">
<event id="delete"/>
*<condition
class="org.apache.lenya.workflow.impl.BooleanVariableCondition">
is_live = false
</condition> *
<condition
class="org.apache.lenya.cms.workflow.RoleCondition">edit</condition>
<assign variable="is_live" value="false"/>
</transition>
With this my problem was fixed.
For more explanations see the workflow configuration page :
http://lenya.apache.org/1_2_x/components/workflow/configuration.html
Kind regards, annie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
