[MGNLDATA-44] versioning of data nodes Created: 15/Aug/08  Updated: 15/Sep/15  Resolved: 27/Jul/09

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2-workflow, 1.4

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

Attachments: Text File data_module_workflow_test_protocol.txt    
Issue Links:
Cloners
supersession
supersedes MGNLDATA-45 Commit-Message-Dialog Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Visible to:
Naresh gangapur, Rammohan Yadavalli, sampath

 Description   
  • add a version command to the activation chain
  • ensure that the recursive activations works
  • ensure that proceeding the workflow activates the formally versioned content
  • add a versions item to the context menu
  • implement the list of versions
  • implement restoring of former versions
  • the version list allows to view the original content. For this the dialog used for editing is opened but with having a single close button.
  • installation / update tasks (apply changes needed in the configuration)


 Comments   
Comment by Jan Haderka [ 19/Aug/08 ]

Could you provide a use case for this?
If you need to version nodes on automatic import, you can have importer class to take care of versioning. If it is while editing content in data repository you can use custom SaveHandler to deal with the versioning.

Comment by Zdenek Skodik [ 18/Jun/09 ]

there were a request for this feature on linked support issue.

Comment by Sunish Abraham [ 21/Jul/09 ]

hi jan,

thank you for the update! so from your above list of items, will Data node be able to participate in workflow approval process?

sunish

Comment by Jan Haderka [ 22/Jul/09 ]

Yes absolutely. Same way as if you activate the item from the website.

Comment by Jan Haderka [ 27/Jul/09 ]

List of extra manual tests performed prior release of the feature.

Comment by Michael Mühlebach [ 15/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:10:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.