[MGNLSTK-1257] Create STK app group in app launcher only if not existing Created: 25/Oct/13  Updated: 13/Nov/13  Resolved: 25/Oct/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 2.7

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDATA-212 Weird applauncher states for data apps Closed
causality
is causing MGNLINTEMPL-42 App is not added to app launcher conf... Closed
is causing MGNLRES-76 App is not added to app launcher conf... Closed
relation
is related to MGNLSTK-1272 Order of apps in STK group is differe... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Module UI migration
Sprint: 5.2-beta1

 Description   

Apps installed before STK may register themselves in the STK app group in Admincentral thus creating the parent node config.modules.ui-admincentral.config.appLauncherLayout.groups.stk.apps. STK should check that such node does not exist before trying to create it, else it would remove from app launcher all previously registered apps.



 Comments   
Comment by Mikaël Geljić [ 31/Oct/13 ]

Just the conditional bootstrap will not fully work for 4.5 -> 5 migration, the stk group properties and default permissions will be missing.

What will happen is:
1. inplace-templating is updated, creates the stk group node along the way
2. stk is updated, sees stk group is already there, and won't bootstrap the group's properties

Most noticeable side-effect will be that STK will have no active color (should be yellow), among others.

Finally, MGNLDATA-212 was a very similar issue with the Data group, we can surely apply a similar fix.

Generated at Mon Feb 12 07:34:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.