[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: |
|
||||
| Issue Links: |
|
||||
| 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:
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. |