[MGNLDAM-399] Error on duplicating asset Created: 20/Feb/14  Updated: 20/May/14  Resolved: 20/May/14

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 1.2.2
Fix Version/s: 1.2.5

Type: Bug Priority: Major
Reporter: Oliver Emke Assignee: Eric Hechinger
Resolution: Fixed Votes: 1
Labels: aperto, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia CMS Demo (see environment.png)


Attachments: PNG File environment.png     PNG File errorMessageInPulse.png    
Issue Links:
causality
caused by MAGNOLIA-5776 MgnlPropertySetting wrapper fails aft... 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:
Visible to:
Frank Sommer, Rainer Blumenthal

 Description   

Tried to duplicate an audio asset. First the following error message occured:

"Can't execute repository operation. property /myfileName/mgnl:lastModified: the property cannot be saved because it has been modified externally." (see errorMessageInPulse.png)

After reloading the app the new duplicate asset is shown. But shouldn't it be shown immediately without reloading?



 Comments   
Comment by Frank Sommer [ 25/Feb/14 ]

The reason seems to be the activites in CreateVariantAction. Why does Magnolia use this action in assets app? What is deeper sense or use case for that?

Comment by Eric Hechinger [ 20/May/14 ]

Solved by changes done in MAGNOLIA-5776

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