[MGNLUI-3193] Upload field do not support correctly i18n specially during D&D Created: 08/Oct/14  Updated: 29/Sep/22  Resolved: 13/Feb/17

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

Type: Bug Priority: Neutral
Reporter: Eric Hechinger Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File magnolia_ui.patch    
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:
Epic Link: I18n fields issues

 Description   

Defining an Upload field as supporting i18n generate error during D&D.

To reproduce:
In admin central, go to
/modules/dam-app/apps/assets/subApps/detail/editor/form/tabs/asset/fields/resource
add a property i18n = true

If you go now to the DAM app, and create a new document using D&D you will face exceptions and the upload will not be performed.

Reason is that the FileTransformer do not correctly support i18n.

Proposed patch in attachment.

In addition you will need to change the info.magnolia.ui.form.field.upload.AbstractUploadField<T>#setLocale(... implementation

@Override
public void setLocale(Locale locale) {
if (getRootLayout() != null)

{ updateDisplay(); getUpload().setReceiver((Receiver) getValue()); }

}



 Comments   
Comment by Mikaël Geljić [ 13/Feb/17 ]

Had a successful go with DnD as of 5.5.1, while MGNLUI-3602 restored i18n support for upload fields. Closing as obsolete.

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