[MAGNOLIA-780] only odd acls are imported! Created: 19/Mar/06  Updated: 17/Mar/09  Resolved: 10/Jun/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.1.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Alessandro Gasparini Assignee: Philipp Bärfuss
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, Windows, JDK 1.5.0, Tomcat 5.5.15


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
Date of First Response:

 Description   

I developed a Magnolia module that initialize some roles defined in a roles.properies loaded using the utility method ModuleUtil.registerProperties().
During the development i found that only the odd acls for the same repository where correctly imported and visible from the administration interface.
Let me explain, i have a roles.properies similar to this:

arscadmin.acl_config.0.path = /modules/adminInterface/Config/menu
arscadmin.acl_config.0.permissions = 8
arscadmin.acl_config.1.path = /modules/adminInterface/Config/menu/website_arsvivendi
arscadmin.acl_config.1.permissions = 8
arscadmin.acl_config.2.path = /modules/adminInterface/Config/menu/users
arscadmin.acl_config.2.permissions = 0
arscadmin.acl_config.3.path = /modules/adminInterface/Config/menu/about
arscadmin.acl_config.3.permissions = 0
arscadmin.acl_config.4.path = /modules/website_arsvivendi/*
arscadmin.acl_config.4.permissions = 0

The acls n. 0,2,4 where correctly imported an the others not. After some tests i noticed that the same strange behaviour also affect the original magnolia module dms-1.0RC3!



 Comments   
Comment by Sameer Charles [ 20/Mar/06 ]

its not a run time problem, probably its in module helper classes

Comment by Magnolia International [ 10/Jun/08 ]

please reopen if this is still valid with Magnolia 3.5, but I seriously doubt it

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