[MGNLSTK-1410] Migration problems with Demo project's userroles 4.5.x to 5.x (uri, category and contacts) Created: 29/Jul/14  Updated: 29/Oct/15  Resolved: 31/Jul/14

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: demoproject
Affects Version/s: None
Fix Version/s: 2.7.7, 2.8.2

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-5841 Updated instances behave as freshly i... Closed
relates to MAGNOLIA-5842 Updated instances behave as freshly i... Closed
relates to MGNLSTK-1412 Migration problems with Demo project'... Closed
relates to MGNLSTK-1415 Remove permissions to access dms from... Closed
relation
is related to CNTCTSAPP-86 Contact's userroles are not migrated ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

The following roles differ in migrated instance to fresh install:

  • demo-project-base
  • demo-project-editor
  • demo-project-publisher

See:

This ticket addresses problem related to uri, category and contacts acls.



 Comments   
Comment by Christopher Zimmermann [ 31/Jul/14 ]

Added MVH and MVHtests to reconcile problems on update to 5.3.x
(Once it passes review, fix will be applied to 5.2.x appropriate branch.)

Comment by Cheng Hu [ 01/Aug/14 ]

This is only a minor point since having extraneous permissions doesn't change anything but since the extraneous permissions for the adminInterface module in demo-project-base are removed in the bootstrap file but not the version handler, won't a person who is upgrading STK still have those extraneous permissions?

Comment by Milan Divilek [ 01/Aug/14 ]

From the diff report is visible that the "adminInterface" permissions are present only during fresh installation. Removing (converting to new one) of those permissions is done in ContactsMVH and CategorizationMVH.

CategorizationModuleVersionHandler line 172

.addTask(new ConvertAclToAppPermissionTask("Convert permissions for 'Categories' app", "Convert ACL permissions for old 'Categories' menu to new 'category' app permissions.", "/modules/adminInterface/config/menu/data/category", "/modules/categorization/apps/categories", true))

ContactsModuleVersionHandler line 190

tasks.add(new ConvertAclToAppPermissionTask("Convert permissions for 'Contact' app", "Convert ACL permissions to old 'Contact' menu to new 'contacts' app permissions.", "/modules/adminInterface/config/menu/data/Contact", "/modules/contacts/apps/contacts", true));
Comment by Christopher Zimmermann [ 04/Aug/14 ]

Exactly - I removed the "extraneous" permissions because the tests detected them only in the fresh install, therefore they had to be removed to make the migrated version equivalent to the fresh install.

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