[VANITY-8] Import + export creates duplicate entries Created: 19/Sep/14 Updated: 05/Jul/18 Resolved: 14/Oct/14 |
|
| Status: | Closed |
| Project: | Vanity URL app |
| Component/s: | None |
| Affects Version/s: | 1.3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Christian Haddorp | Assignee: | Frank Sommer |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: | |
| Visible to: |
ameyer, Roland Aust, Werner Rauch
|
| Description |
|
After imported an existing XML dump the Vanity URL shows all entries twice. Seems the entries have an identical ID as it is not possible to select just one. Newly added entries behave normally. Is there anything I can check? Sounds little strange; but I could reproduce it 2-3 times. |
| Comments |
| Comment by Frank Sommer [ 19/Sep/14 ] |
|
It sounds that you create node sibblings by importing the XML dump. How do you import the XML? Over the import page? Do you choose the option "replace nodes with the same id"? |
| Comment by Jan Christian Haddorp [ 19/Sep/14 ] |
|
I've use the XML export/import app from Magnolia (please find our data attached). The initial approach was to copy setting from one system to another. I used the "replace nodes..." options. However as the new system was newly set up there was no existing data. Unluckily I forgot taking a screen shot. Seems both entries have had the same ID as it was not possible to select just one entry. When selecting a single entry the second entry was selected as well. Currently we are using Magnolia 5.3.2 and I plan migrating to 5.3.3 next. |
| Comment by Jan Christian Haddorp [ 24/Sep/14 ] |
|
This is the screen. Interesting point... After publishing an entry it is fixed. |
| Comment by Frank Sommer [ 29/Sep/14 ] |
|
It sounds like a strange caching problem of the vaadin tree. Can you check this? Do a xml export, if you see double nodes or open the app in another browser.
|
| Comment by Jan Christian Haddorp [ 29/Sep/14 ] |
|
Ok, strange... It is not a frontend caching issue. Even after closing the browser I had duplicate entries. I tried it twice via import. But as the issue solves itself during the activation process we can close this ticket. |