[MGNLDAM-665] "Duplicate asset"-action breaks nodes not containing their correct file extension Created: 07/Jul/16  Updated: 27/Oct/16  Resolved: 27/Jul/16

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 2.1.5
Fix Version/s: 2.1.6

Type: Bug Priority: Neutral
Reporter: Matthias Müller Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 5h
Original Estimate: Not Specified

Attachments: PNG File asset_fail_to_determine_type.png     PNG File asset_fileName_has_no_extension.png     PNG File asset_node_name_has_no_extension.png    
Issue Links:
Relates
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:
Sprint: Basel 54
Story Points: 5

 Description   

The node name of an asset may not contain its file extension:

  • the assets node name was changed by the editor (action 'Rename item')
  • it's an 'old' asset (in older magnolia versions uploaded assets used not to have their file extension in the node name)

When duplicating such assets, they break, as the jcr property 'name' and the jcr content property 'fileName' both seem to get the node name of the original asset (added by a random number) instead of the value of their respective properties in the original asset.

An example using an asset on the public magnolia demo instance is attached.


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