[MGNLDATA-167] JCRAdminTree doesn't reflect the right activation status for subnodes Created: 12/Mar/13  Updated: 11/Jul/13  Resolved: 27/May/13

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

Type: Improvement Priority: Neutral
Reporter: Zdenek Skodik Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLCAT-62 CLONE - JCRAdminTree doesn't reflect ... Closed
causality
is causing MGNLDATA-190 Nodetype migration script should not ... Closed
relation
is related to MGNLDATA-180 Script for updating node type in bund... Closed
is related to MGNLDATA-185 Update dataItemNode node type in runt... Closed
is related to MAGNOLIA-4968 Add data module bundle into bundle ad... Closed
is related to MGNLEE-269 CLONE - Add data module bundle into b... Closed
is related to MGNLDATA-184 Message for updating custom_nodetypes... Closed
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Date of First Response:

 Description   

To reproduce:

  • at Data/Category activate a Family one
  • compare the node hierarchy for the item at Data/JCR browser of both Author&Public. You should see a subnode with red icon, although it has been activated properly.


 Comments   
Comment by Jan Haderka [ 27/Mar/13 ]

Isn't that registered only on install? Don't you need update task to update type definition on existing instance?

Comment by Jan Haderka [ 10/Apr/13 ]

Release notes need to mention the python script and need to execute this script during update.

Comment by Milan Divilek [ 11/Apr/13 ]

Reopen: Not everything was ported to master

Comment by Milan Divilek [ 24/May/13 ]

Reopen: After update subnodes don't have metadata - > icon is still red after activation.

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