[ADMINCTR-174] Admin central - remove dependency on UI-compatibility layer (configuration app) Created: 01/Aug/22  Updated: 25/Jul/23

Status: Open
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Story Priority: Neutral
Reporter: Dominik Maslanka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-8433 DX Core 6.3 Consolidation Selected
duplicate
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ADMINCTR-175 Implementation Sub-task To Do  
ADMINCTR-176 Review Sub-task To Do  
ADMINCTR-177 Pre-Integration QA Sub-task To Do  
ADMINCTR-178 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Decommission legacy UI framework
Team: AuthorX

 Description   

User Story: as a SaaS user, I want to be sure that I'm using the latest stable version of the app so that I don't want to use the app based on the old legacy framework. 

Description: 
Our goal for 6.3 is to altogether remove the old UI framework; i.e. we will migrate all bundled apps to the M6 UI and remove the compatibility layer. This is equally important for SaaS where we do not want to run the legacy UI at all.

We need to

remove configuration app from admincentral
 
https://git.magnolia-cms.com/projects/MODULES/repos/admincentral/pullrequests/44/overview

 

Removing this dependency will let us continue with the complete removal of the compatibility layer 



 Comments   
Comment by Mikaël Geljić [ 25/Aug/22 ]

In this case, as rhayoun identified, the Configuration app (which is a legacy Vaadin 7 / compatibility app) is still provided by the latest "admincentral" module. Removal is fairly trivial, just updating the PR, and meanwhile the JCR config workspace remains editable through the JCR app (a proper UI 6 app).

Generated at Sun Feb 11 23:04:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.