[MGNLDAM-164] In the Assets app, if I rename a folder, I can still execute actions on the folder with the old name Created: 05/Mar/13  Updated: 09/Jul/13  Resolved: 09/Jul/13

Status: Closed
Project: Magnolia DAM Module
Component/s: User Interaction
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: alpha3, assets_app
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 1 - the folder before renaming.png     PNG File Screenshot 2 - situation right after renaming.png     PNG File Screenshot 3 - error after another rename.png    
Issue Links:
Relates
relates to MGNLUI-806 In the contacts app, you can still ex... 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
Date of First Response:

 Description   

If I rename a folder, then immediately execute the "new folder" action to add a new sub folder underneath it, I get an error (since the folder was renamed and the selected item still refers to the old folder).

Similarly, you may also rename a folder, then immediately rename it again, without changing the selection, but just by clicking on the "rename folder" action again. This also causes a system error to show up. See screen shots 1 to 3.

Expected behavior:
1. First of all, the folder should remain selected.
2. The actions in the Action bar should refer to the renamed folder.



 Comments   
Comment by Andreas Weder [ 05/Mar/13 ]

Linking two issues which - I suspect - describe the exact same problem.

Comment by Eric Hechinger [ 05/Mar/13 ]

Closed. Resolved by commit done in MGNLUI-806.

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