[MGNLUI-5598] Upload asset fails due to (wrong) validation exception Created: 16/Dec/19  Updated: 15/Jan/20  Resolved: 15/Jan/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

Type: Bug Priority: Blocker
Reporter: Christoph Meier Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 16m
Original Estimate: Not Specified
Environment:

CE-demo-webapp; 6.2 (Snapshot: 2019.12.10 09:26:46)
and
CE-demo-webapp; 6.2 (Snapshot: 2019.12.14 20:36:46)


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: UI Framework 14
Story Points: 3

 Description   

The attempt of uploading an asset always fails due to a validation exception on the field Asset name ; the message given to the user is 

{$asset-name} already exists.

The validation ex- is thrown always - no matter whether such asset with the given name does exist there or not.

In one of ~50 cases I have seen the asset in the browser later on. But not sure how this hapend.

Generally that bug prevents uploading a single asset.
It is a regression.
(and quite a blocker imho)



 Comments   
Comment by Adam Siska [ 08/Jan/20 ]

> In one of ~50 cases I have seen the asset in the browser later on. But not sure how this hapend.
It is possible to bypass this if one use special (non-JCR) character Node name (with -'s) is not equal to jcrName property then..

 EDIT: even simpler way is commit for second time with same name...

Generated at Mon Feb 12 09:28:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.