[MAGNOLIA-806] Config tree allows duplicates on import, but does not display them Created: 12/Apr/06  Updated: 14/Aug/06  Resolved: 14/Aug/06

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.1.5
Fix Version/s: 3.0 RC3

Type: Bug Priority: Major
Reporter: Andrew Sterling Hanenkamp Assignee: Fabrizio Giustina
Resolution: Fixed 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   

Sorry if this is a duplicate, but I just ran into this in 2.1.5:

1. Export some template from instance A, we'll say:

config.modules.templating.Templates.foo.xml

2. Import that file into instance B into "config/modules/templating/Templates", where instance B already has a folder at "config/modules/templating/Templates/foo".

3. The import appears to succeed, but there are no entries shown.

4. Now export from instance B, "config/modules/templating/Templates" to get:

config.modules.templating.Templates.xml

5. Open the file in your favorite editor and note that there are two sv:node entries for "foo".



 Comments   
Comment by Sameer Charles [ 16/May/06 ]

need HierarchyManager.refresh(true) or parentNode.refresh(true) after importing any data

Comment by Fabrizio Giustina [ 14/Aug/06 ]

duplicates are still allowed in 3.0, but admininterface properly show them.

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