[MAGNOLIA-3457] Config reload on Module doesn't work if config-node is missing at start. Created: 08/Dec/10  Updated: 13/Mar/12  Resolved: 18/Oct/11

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

Type: Bug Priority: Major
Reporter: Kimmo Björnsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX


Issue Links:
dependency
depends upon MAGNOLIA-2265 Observe module nodes to automatically... Closed
relation
is related to MAGNOLIA-3576 Module startup failure should still s... Closed
is related to MAGNOLIA-3492 Reload of modules after activation re... 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 I have no config-node on my module in the repository at start and then add the config-folder, and a content-node with data with the correct name according to my module. Magnolia do restart my Module but the property on my Module-object is not set, it's still null.



 Comments   
Comment by Magnolia International [ 09/Dec/10 ]

This is in part related to MAGNOLIA-2265 - although the module class should be instantiated whether or not the config node is there.

Comment by Tobias Mattsson [ 18/Oct/11 ]

Created a separate issue for nulling out properties on the module instance, MAGNOLIA-3862.

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