[MGNLUI-6838] JCR browser keeps mgnl:tmpDeleted$Node selected Created: 03/Feb/21 Updated: 23/Sep/21 Resolved: 16/Sep/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.12 |
| Fix Version/s: | 6.2.12 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Julian Nodarse | Assignee: | Adam Siska |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | maintenance, ui-team-support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Template: | |||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Sprint: | UI FW 36, UI FW 37 | ||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||
| Description |
|
There is inconsistent behavior when deleting nodes and importing content. For all test cases below, create some content at the root level in the pages app / website workspace and continue with each case's instructions. Case 1 [^Case 1.mov] Case 2 [^Case 2.mov]
Workaround Other Notes |
| Comments |
| Comment by Simon Tourville [ 25/Mar/21 ] |
|
Any fix plan in the next release? |
| Comment by Simon Tourville [ 14/Jun/21 ] |
|
Very happy to see this ticket moving! (I cannot tell you the amount of problems this is causing losing our UUID when deleting and importing content!) Workaround: Using groovy to clean it up every time we delete something. |
| Comment by Marvin Kerkhoff [ 24/Jun/21 ] |
|
Hi @Simon i would be very happy if you can add the groovy script you are using into the ticket. I am currenty getting this issue and my JCR Browser says that the workspace is completly empty and i already tried reindexing whatsover. It seems that every import also with the successful one at the top will create new uuids which creates a lot of other issues. |
| Comment by Simon Tourville [ 28/Jun/21 ] |
|
@Marvin, Here is the script we always have to run after deleting a node and reimporting it. Any plan to solve it in a near future? session = ctx.getJCRSession('website'); try { node = session.getNode('/mgnl:tmpDeleted$Node'); node.remove(); } catch(Exception ex) { println("Erreur 'website': " + ex); } session.save();session = ctx.getJCRSession('dam') try { node = session.getNode('/mgnl:tmpDeleted$Node') node.remove(); } catch(Exception ex) { println("Erreur 'dam': " + ex); } session.save() |
| Comment by Roman Kovařík [ 14/Sep/21 ] |
|
Reopened: still an issue, a little different behaviour not published vs. published node. |