[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: |
|
||||||||||||
| 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:
child first:
Both lead to an error and a corrupt mgnlVersions workspace. |
| Comments |
| Comment by Jan Haderka [ 23/Jun/11 ] |
|
resolving
|
| Comment by Jan Haderka [ 28/Jun/11 ] |
|
and one extra possibility:
|
| 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. |
| Comment by Jan Haderka [ 08/Sep/11 ] |
|
thx |