[TPLTSUSAGE-2] Modules are not displayed, although the documentation implies this Created: 24/Oct/18  Updated: 03/Sep/19  Resolved: 03/Sep/19

Status: Closed
Project: Templates Usage
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Sahin Guener Assignee: Mariusz Chruscielewski
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.7.1 EE Pro
Templates Usage Module 3.0.0


Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

The documentation says the following: "When no configuration done at all, all modules are displayed to all users[...]" I have tried this and can say that it does not work.
First: To be able to see the app, the user must have the role "editor" or "superuser", which wasn't fulfilled in my case. After adding the role "editor" I was able to see the ContentApp. But the modules are not shown. Only "mtk" was shown.

So I have tested several options in the config workspace:
1. I've deleted the property "0" under the path "/modules/templates-usage/config/allowedModules". -> Result: No module was shown in the ContentApp.
2. I've deleted the node "allowedModules" under the path "/modules/templates-usage/config". -> Result: Same result as before.
3. I've deleted the node "config" under the path "/modules/templates-usage". -> Result: Same result as before.

How can I ensure that normal editors can see all modules, without adding them manually?

Best regards

Sahin Güner



 Comments   
Comment by Sahin Guener [ 29/Oct/18 ]

Any updates here?

Comment by Mariusz Chruscielewski [ 31/Oct/18 ]

Hi @Sahin, I think there is a mistake in documentation. Looking at the code, currently it's only possible to show module in a list, if it's added to allowedModules list, or user has a superuser role. So for now, you have to add modules manually. I will create a ticket in our Jira, and fix it when we have some time. Will notify you when it's ready.

Kind regards

Mariusz

Comment by Sahin Guener [ 01/Nov/18 ]

Hello Mariusz,

 

Thanks for the information. We will do it manually.

 

Best regards

 

Sahin

Comment by Mariusz Chruscielewski [ 30/Aug/19 ]

@Sahin - it's fixed in version 3.1.0 for Magnolia 6.1 and in 3.0.3 for Magnolia 5.7.x

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