[MGNLUI-2595] When activating nodes in config workspace all sub nodes of mgnl:contentNode type are accidentally pulled in as well. Created: 17/Jan/14  Updated: 29/Jan/14  Resolved: 28/Jan/14

Status: Closed
Project: Magnolia UI
Component/s: configuration
Affects Version/s: 5.0
Fix Version/s: 5.2.2

Type: Bug Priority: Critical
Reporter: Jan Haderka Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: maintenance, quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-502 Difference between activation from we... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:

 Description   

This is due to default rule being applied on activation trigged by "publish" action in config. Setting itemTypes to empty string on this action should be enough to work around.
However since other apps (e.g. jcr browser) tend to extend from "configuration" app, be careful that this doesn't break activation or versioning from other apps. ... all apps extending the browser or actions from configuration need to be checked.



 Comments   
Comment by Milan Divilek [ 28/Jan/14 ]

Apps which use extended activate actions from configuration app are websiteJcrBrowser, stkSiteApp, stkThemesApp, stkChannelsApp, stkDialogsApp, stkTemplateDefsApp and all of those should behave as configuration app during activation. It means only selected node should be activated not his subNodes.

Generated at Mon Feb 12 08:58:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.