[MGNLDATA-124] activation of hierarchical data fails Created: 19/May/11  Updated: 08/Sep/11  Resolved: 08/Sep/11

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

Type: Bug Priority: Critical
Reporter: Philipp Bärfuss Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
dependency
depends upon MAGNOLIA-3704 versioning: clean mgnlVersions worksp... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Tested with the demo company 'Big Flower Inc.'

There are two scenarios which fail:

parent first:

  1. activate the company
  2. then a department

child first:

  1. activate an employee
  2. activate a parent node

Both lead to an error and a corrupt mgnlVersions workspace.



 Comments   
Comment by Jan Haderka [ 23/Jun/11 ]

resolving MAGNOLIA-3704 might be difficult. In the mean time there should be possible 2 workarounds specific to Data module:

  • disallow separate activation of subtypes w/o activation of parent type. This would be no different from activation of pages only in website repo. In a sense subtype is to a parent type what paragraph is to a page.
  • disallow activation of any content w/o parent being activated already. This workaround would work only as long as nobody changes configuration of versioning for the module or doesn't end up with clean mgnlVersion workspace.
Comment by Jan Haderka [ 28/Jun/11 ]

and one extra possibility:

  • try to setup rules in such a way that subtypes are always activated as separate items and not as part of the super type.
Comment by Jan Haderka [ 23/Aug/11 ]

The implemented solution checks for configuration of the types and enables activation selectively based on the settings. If subtypes are configured to be activated together with the parent type, they can no longer be activated on their own. If on the other hand subtypes are not configured to be activated together with the parent types they can still be activated separately or via parent using "activate incl subpages".

Comment by Jan Haderka [ 23/Aug/11 ]

If the issue actually occurred it will not be fixed by the fix here. To fix such problem one has to decide - either enable activation of parent type only with the subtypes and delete the subtype node from mgnlVersion or change configuration and activate parent type separately from subtypes (And use "activate incl. subpages" to activate all).

Comment by Ondrej Chytil [ 07/Sep/11 ]

Activation is not launched now.
Also there is "500" on Contact, Category and RSS pages.

Comment by Jan Haderka [ 08/Sep/11 ]

thx

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