[MAGNOLIA-2910] Preserve DMS specific versioning command upon workflow installation Created: 27/Oct/09  Updated: 23/Jan/13  Resolved: 27/Oct/09

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 4.0.3, 4.1.1, 4.2
Fix Version/s: 4.2.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-2955 CLONE -Preserve DMS specific versioni... Closed
relation
is related to MGNLDMS-158 Versioning of document with content i... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

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.



 Comments   
Comment by Jan Haderka [ 27/Oct/09 ]

Done as of r28822.

Comment by Jan Haderka [ 26/Nov/09 ]

To solve your issue if occurs in versions earlier then 4.2.1, 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

Generated at Mon Feb 12 03:41:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.