[MGNLDAM-310] renaming an asset node does not rename the name of the asset, makes the asset unreachable Created: 26/Sep/13  Updated: 27/Sep/13  Resolved: 27/Sep/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: 1.1

Type: Bug Priority: Critical
Reporter: Karel de Witte Assignee: Eric Hechinger
Resolution: Cannot Reproduce 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   

open assets demo site, rename the node, try to reach the asset on the new url (doe snot work) try to reach the asset on the previous url (with jcr:content/name of asset) does not work. Works only if asset name and node name are identical.



 Comments   
Comment by Eric Hechinger [ 27/Sep/13 ]

Checked with reporter....

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