[MGNLDATA-137] Cannot Edit JCR versioned nodes Created: 07/Nov/11  Updated: 07/Nov/11  Resolved: 07/Nov/11

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Michael de Courci Assignee: Zdenek Skodik
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Unix


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We are using Magnolia Enterprise edition magnolia-4.4.4 and the JCR 170 API.

Our application code reads property content from XML data files to load this into Magnolia Data workspace via the JCR API.

For each property in the XML file a JCR node is created and Magnolia is configured so that you can see properties loaded in the Data Workspace
via the AdminCentral Data Menu.

You can also add and edit loaded properties from the Data Menu.

We have defined our own types in Magnolia which is used as the NodeType when creating
nodes of that type.

I changed the code to version the property nodes as follows;-

node.addMixin(JcrConstants.MIX_VERSIONABLE);
jcrSession.save();
node.checkin();

And executed some more data loads. Now we have a problem because the loaded properties that are versioned cannot be edited from the
AdminCentral Data Menu.

Are we doing something wrong here?



 Comments   
Comment by Zdenek Skodik [ 07/Nov/11 ]

Just the current version can be edited from within the AdminCentral, would you like to see previous versions, you need to restore to that version (eventually compare the current to a previous version with use of the Diff module).

Anyway you should not assign mix:versionable directly (MAGNOLIA-2086), but rather use the versioning API instead - f.e. see how a version gets created during activation by info.magnolia.module.admininterface.commands.VersionCommand, or find the info.magnolia.cms.core.version package.

For closer informations please create a support issue.

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