[MAGNOLIA-8040] After deleting node in JCR browser path remains as /mgnl:tmpDeleted$Node Created: 30/Mar/21  Updated: 12/Apr/21  Resolved: 12/Apr/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.6
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2021-03-30 at 16.39.07.png    
Issue Links:
Relates
relates to MGNLUI-6838 JCR browser keeps mgnl:tmpDeleted$Nod... Closed
causality
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   

Steps to reproduce

  1. Open JCR Browser app
  2. Select a node and delete it
  3. Path remains as /mgnl:tmpDeleted$Node
  4. Import a previously exported node

    Expected results

    After removing the node, path goes back to root and the new node can be imported correctly

    Actual results

    After removing the node path remains as /mgnl:tmpDeleted$Node and consequently importing the new node is not correctly done. This can lead to errors in some specific scenarios.

    Workaround

    Click somewhere so that current path is updated


Generated at Mon Feb 12 04:29:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.