[MAGNOLIA-2955] CLONE -Preserve DMS specific versioning command upon workflow installation Created: 25/Nov/09  Updated: 03/Nov/15  Resolved: 03/Nov/15

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

Type: Bug Priority: Major
Reporter: Rainer Blumenthal Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-2910 Preserve DMS specific versioning comm... 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
Date of First Response:

 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 Rainer Blumenthal [ 25/Nov/09 ]

I couldn't reopen - so i had to clone this issue... hope this is right.

I am running in exactly the described problem - what is the solution for now.

How can i get back the original DMS Versioning command that has been overwritten in my case? I have the error from MGNLDMS-158 using DMS 1.4 in Magnolia 4.1.1.

Comment by Jan Haderka [ 25/Nov/09 ]

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

Comment by Michael Mühlebach [ 03/Nov/15 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an outdated version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is together with it's associated version no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

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