[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25109#action_25109
]
Jan Haderka commented on MAGNOLIA-2955:
---------------------------------------
You should have opened a support issue for this. MAGNOLIA-2910 states that
version 4.1.1 is affected by the issue, so there is no point in cloning this
issue as it doesn't reveal any new facts about the problem.
To solve your issue, you have to change the command back manually - go to
{{config:/modules/dms/commands/dms/activate}} and change value of {{class}}
from {{info.magnolia.module.admininterface.commands.VersionCommand}} to
{{info.magnolia.module.dms.commands.DocumentVersionCommand}}
> CLONE -Preserve DMS specific versioning command upon workflow installation
> --------------------------------------------------------------------------
>
> Key: MAGNOLIA-2955
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2955
> Project: Magnolia
> Issue Type: Bug
> Components: workflow
> Affects Versions: 4.0.3, 4.1.1, 4.2
> Reporter: Rainer Blumenthal
> Assignee: Jan Haderka
>
> Since version 4.0/DMS 1.4, DMS is using its own versioning command to
> overcome issue MGNLDMS-158. When installing workflow, this command is
> overwritten with the default.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
