[MAGNOLIA-3862] Rename of module config doesn't null of property in module instance Created: 18/Oct/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core, modulemechanism
Affects Version/s: 4.4.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Split off from MAGNOLIA-3457.

If I have the config loaded and rename a property, the module is reloaded but the property is still there with all old values. I think it should be null.

Renaming property.

2010-12-08 12:21:25,599 INFO AdminTreeMVCHandler.renameNode(564)
Moving node from /modules/kokaihop/config/properties to /modules/kokaihop/config/properties2
2010-12-08 12:21:30,609 INFO ModuleManagerImpl.stopModule(388)
Stopping module kokaihop
2010-12-08 12:21:30,609 INFO KokaihopModule.stop(60)
module stop, during restart
2010-12-08 12:21:30,610 INFO ModuleManagerImpl.startModule(380)
Starting module kokaihop
2010-12-08 12:21:30,610 INFO KokaihopModule.start(49)
module start, during restart

Module restarted but property is still intact.



 Comments   
Comment by Magnolia International [ 11/Dec/13 ]

Tobias, do you have more info on this ? Is this happening when the module class has both properties and properties2 fields ? Or how else to reproduce this ?

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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