[MGNLSITE-36] No site definition appears in Site App for users other than superuser Created: 08/Sep/15  Updated: 05/Oct/15  Resolved: 05/Oct/15

Status: Closed
Project: Magnolia Site Module
Component/s: app
Affects Version/s: 1.0.1
Fix Version/s: 1.0.3

Type: Bug Priority: Neutral
Reporter: Brian Warrick Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2015-09-08 at 10.43.23 AM.png    
Issue Links:
dependency
depends upon MGNLDEMO-70 Eric, Peter & Tina should see less apps 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:
Sprint: Basel 13
Story Points: 1

 Description   

In 5.4.1 EE Bundle, when accessing the Site app as any user other than superuser (Eric, Peter or Tina), no site information displays.



 Comments   
Comment by Christopher Zimmermann [ 17/Sep/15 ]

I dont think any of these users should be able to access the site, do you?
I think it would make most sense if these user could not access the Site app - dont you?
Could we close this as a duplicate of https://jira.magnolia-cms.com/browse/MGNLDEMO-70? (and perhaps add a few more notes to that ticket.)

Comment by Brian Warrick [ 17/Sep/15 ]

Agreed, they should not see the Site App. Showing the app in its current state gives the appearance that the product is not functioning correctly. Ok to close and move, just didn't want it to be missed. Thanks.

Comment by Philip Mundt [ 05/Oct/15 ]

I think this issue is independent of MGNLDEMO-70 and we should simply add the permissions node to the site app configuration, limiting access to superuser only.

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