[MGNLDAM-715] CreateAssetVariantAction throws exception when asset has missing master Created: 15/Jun/17  Updated: 06/May/20  Resolved: 06/May/20

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 2.2.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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

 Description   

To reproduce this issue:

  • Duplicate an asset in the DAM
  • Delete the asset used to create the duplicate
  • Try to duplicate the duplicate.
  • Observe the error.

If the master is missing it results in the exception:

<sv:property sv:name="master" sv:type="WeakReference">
    <sv:value>24bb3d56-cd92-4f07-ab1e-e7760a117807</sv:value>
  </sv:property>


 Comments   
Comment by Richard Gange [ 06/May/20 ]

Not an issue in 6.2

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