[MAGNOLIA-4437] Public's AdminCentral can't get initialized properly Created: 08/Jun/12  Updated: 08/Aug/12  Resolved: 08/Aug/12

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Milan Divilek
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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   

Changes done to MAGNOLIA-4109 causes the AdminCentral to look and feel like an Author one, i.e. with status column in place etc. The instance itself behave as a Public one otherwise.

One faces the issue only when using custom context parameters in web.xml for the initialization, however it doesn't affect the default locations MgnlServletContextListener looks to, so the bug is not visible on the webapps as preconfigured out of the box.



 Comments   
Comment by Jan Haderka [ 25/Jul/12 ]

Causality to MAGNOLIA-4109 was wrong. This issue was just hiding the real problem, but in fact this issue was introduced when reworking changes in initialization for 4.5 already.

Comment by Milan Divilek [ 08/Aug/12 ]

In the end this is not an issue. Problem was caused misconfiguration where was bootstrap subscriber to the public instance. For more detail see SUPPORT-1698.

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