[MAGNOLIA-1326] ModuleUtil.bootstrap() could accidentally delete nodes in the Config workspace Created: 31/Jan/07  Updated: 23/Jan/13  Resolved: 31/Jan/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2, 3.1 M1

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1327 ModuleUtil.bootstrap() uselessly crea... Closed
supersession
is superseded by MAGNOLIA-1380 modules: modules should not bootstrap... 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

 Description   

If a bootstrap file maps to foo/bar in the website workspace, and a node with the same exists in the Config workspace, it is going to be deleted.
(lines 176-180 of info.magnolia.cms.module.ModuleUtil)



 Comments   
Comment by Magnolia International [ 31/Jan/07 ]

fixed in 3.0 branch and trunk

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