[MGNLUI-4729] Revise the field validation when switching languages Created: 24/Oct/18  Updated: 29/Mar/22  Resolved: 17/Feb/22

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

Type: Improvement Priority: Neutral
Reporter: Ondrej Chytil Assignee: Fernando Cherchi
Resolution: Obsolete Votes: 0
Labels: maintenance, nucleus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-3491 Switching the language in a content a... Closed
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)
Date of First Response:
Epic Link: Support
Sprint: Nucleus 4
Story Points: 2
Team: Nucleus

 Description   

MGNLUI-3491 fixed an issue with validation being skipped for non-active locales in dialogs by forcing an user to meet all the requirement before switching the locale of the dialog.

However that brings a new set of issues since inability to use the locale switcher is limiting for editors. Two use-cases:

  • even though there's always a fallback locale it doesn't have to be filled for a particular node, in that case it's impossible to fill other locales if there are required fields in place.
  • if editor writes a content in the fallback locale and switches to other locale, it's impossible to go back and/or save the content if there are any required fields.

This can of course be avoided by dividing the content into multiple trees but not every time is this solution possible.

Ideally the validation should be performed for all locales during the save dialog step.



 Comments   
Comment by Fernando Cherchi [ 17/Feb/22 ]

Checked with ochytil that the issue is obsolete:

I just checked and with the 6.x UI the issue is gone. Now you can switch between locales and the validation is done only upon save action. So the ticket can be closed as obsolete/not an issue.

Comment by Fernando Cherchi [ 17/Feb/22 ]

As per Ondrej Comment:

I just checked and with the 6.x UI the issue is gone. Now you can switch between locales and the validation is done only upon save action. So the ticket can be closed as obsolete/not an issue.

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