Loading...

XML

Word

Printable

Type: Improvement
Resolution: Fixed
Priority: Neutral
Fix Version/s: 1.7.5, 2.0
Affects Version/s: None
Labels:
None

Template:
Acceptance criteria:

Empty

show more show less
Release notes required:

Yes

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.

Acceptance criteria

is causing

MGNLDATA-190 Nodetype migration script should not require Python - and should probably be moved to magnolia-tools

Closed

is cloned by

MGNLCAT-62 CLONE - JCRAdminTree doesn't reflect the right activation status for subnodes

Closed

is related to

MGNLDATA-180 Script for updating node type in bundle has DOS line endings and hasn't got 'x' flag

Closed

MGNLDATA-185 Update dataItemNode node type in runtime instead of doing it manually

Closed

MAGNOLIA-4968 Add data module bundle into bundle addons folder

Closed

MGNLEE-269 CLONE - Add data module bundle into bundle addons folder

Closed

MGNLDATA-184 Message for updating custom_nodetypes.xml should be more explanatory

Closed

(2 is related to)

Assignee:: Jaroslav Simak

Reporter:: Zdenek Skodik

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 12/Mar/13 1:18 PM

Updated:: 11/Jul/13 5:41 PM

Resolved:: 27/May/13 1:57 PM

Date of First Response:: 27/Mar/13 4:29 PM