[MAGNOLIA-2605] Installation of the STK bundle into a plain CE installation fails. Created: 30/Jan/09  Updated: 23/Jan/13  Resolved: 02/Feb/09

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

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

Issue Links:
Cloners
is cloned by MAGNOLIA-2611 invalidate session after an installation Closed
relation
is related to MAGNOLIA-2606 tree fails to render if no content is... 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   
  • install CE bundle
  • start & stop (install)
  • install STK
  • start & stop (install)

While everything seems to be installed, the content of resources (css & js) and templates is not persisted. It seems as if the content gets installed but the saving fails. This does not happen if one installs both together (by putting the jars before starting up Magnolia for the first time)



 Comments   
Comment by Philipp Bracher [ 30/Jan/09 ]

If I debug I can't reproduce it. I think it might be related to the permissions.

  • The permissions of the superuser are not reloaded?
  • The session and so the user object is actually persisted during a restart of the system.
  • could it be that it depends on how fast you login after an installation?
Comment by Philipp Bracher [ 30/Jan/09 ]

My assumptions were correct. The user is serialized and reused after the installation.

A simple logout / logout solves the issue. What people might confuse is that a restart doesn't solve the issue.

The question is more what we do about that. I actually think that the superuser should not at all use roles but just have all permissions granted (not by using real ACLs).

Comment by Philipp Bracher [ 30/Jan/09 ]

Hm, for time being it might be enough just to invalidate the session after the the installation process finished. After a quick check I don't think it is easy to change the superuser behavior. A specific AccessManager would be needed.

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