[MGNLCT-145] Magnolia UI 6 - Form definition properties i18n and required Created: 21/May/20  Updated: 22/Apr/22  Resolved: 18/Jun/20

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Attachments: PNG File Screenshot 2022-04-08 at 09.40.17.png     Zip Archive example1.zip    
Issue Links:
Problem/Incident
Relates
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:

 Description   

Summary:

By setting the i18n and required properties to true of a field in a dialog and a contentType, the dialog can't be saved if you don't fill the field in all languages.

If only the default language is fulfilled then the following error is thrown:

[RpcInvocationException: Unable to invoke method click in com.vaadin.shared.ui.button.ButtonServerRpc caused by InvocationTargetException]

Steps to reproduce:

  1. Copy the imported zip in light-modules folder
  2. Check that the workspace and the app has been created
  3. Open Publicaciones app
  4. Clic on add an Item
  5. Fulfill only the field Title in one language and clic on Save
  6. Check that RpcInvocationException error is thrown

Expected results:

The field Title, as far as it's required should be fulfilled in, at least, one language.

Actual results:

The field Title must be fulfilled in all available languages, otherwise it throws an error and the values are not saved (dialog is not even closed).

Workaround:

N/A

Development notes:

N/A



 Comments   
Comment by Mercedes Iruela [ 18/Jun/20 ]

Issue fixed by MGNLUI-5874

Comment by Anne Meister [ 08/Apr/22 ]

Hi Mercedes!

I am still having this problem on 6.2.17 and don't believe it's solved with MGNLUI-5874 – it's two different issues IMO. One has a validation exception (this is solved), but the issue here is not showing a validation exception but not letting me save a dialog at all, jumping to a language where the field is not filled in. 

IMO it should check for content in at least one language, but allow others to be empty. Up until Mgnl 6.1, I was able to work around by changing the language of the dialog back to the one that has content for the required fields and save. This does not work any more with Mgnl 6.2, where it jumps back to the language where there is no content and refuses to save the dialog.

Let me know what you think!

Cheers, Anne

Comment by Mercedes Iruela [ 22/Apr/22 ]

Hello Anne,

We have been revisiting this topic many times in the latest releases, could you please open a Support ticket and attach a sample dialog/app so that we can understand the problem?

Best regards,
Mercedes

Generated at Mon Feb 12 00:37:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.