[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 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 I changed the code to version the property nodes as follows;- node.addMixin(JcrConstants.MIX_VERSIONABLE); And executed some more data loads. Now we have a problem because the loaded properties that are versioned cannot be edited from the 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 ( For closer informations please create a support issue. |