[MAGNOLIA-1526] Repository names in roles acl page can't be translated for modules Created: 10/May/07  Updated: 23/Jan/13  Resolved: 17/Aug/07

Status: Closed
Project: Magnolia
Component/s: admininterface, core
Affects Version/s: None
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLFORUM-23 i18n for the admin ui Closed
relation
is related to MAGNOLIA-541 security: Allow defining custom Permi... 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
Date of First Response:

 Description   

If a module registers a new repository/workspace, its name isn't translated in the roles/acl dialog. (except if, like for dms, there happens to be a repository.repositoryName key in the admininterface's messages)



 Comments   
Comment by Philipp Bracher [ 15/May/07 ]

I wanted to solve this by making the page configurable (content2bean) so that you define on the acl page which repositories are showed and how there acl behavior is (is there a choose button, what are the selectable permissions,....)

Comment by Philipp Bracher [ 17/Aug/07 ]

conigure acls and repositories in /modules/adminInterface/config/securityConfiguration

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