[MGNLUI-6857] Cannot update only non-i18n fields Created: 03/Sep/21  Updated: 22/Sep/21  Resolved: 09/Sep/21

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: 6.2.8
Fix Version/s: 6.2.12

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Roman Kovařík
Resolution: Fixed Votes: 1
Labels: maintenance, ui-team-support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causality
caused by MGNLUI-6724 Forms are always created for all lang... Closed
is causing MGNLPN-586 Preview app not working Closed
duplicate
is duplicated by MGNLUI-6880 Cannot save dialogs in another langua... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Sprint: UI FW 36

 Description   

When having a form with mixed i18n and non-i18n fields it's not possible to only update the non-i18n fields.

Reproduce

  1. Open https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:pages-app:detail;/travel:edit
  2. Switch to DE (in the footer)
  3. Click Edit page properties action.
  4. Change a non i18 field (e.g Hide in navigation checkbox)
  5. Open the dialog again

Expected
The field is changed.

Actual
Non-i18n fields are not updated.

Workaround

  • A] Before saving dialog, switch to default language
  • B] Using a double edit approach you can workaround the issue. Change at least one i18n field to save the non-i18n. Edit again to change back the i18n field.


 Comments   
Comment by Roman Kovařík [ 08/Sep/21 ]

Reopened:

  1. Disable http://nightly.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/publishing-core/config/receivers/magnoliaPublic8080@enabled:treeview:
  2. http://nightly.magnolia-cms.com/.magnolia/admincentral#app:resources;/travel-demo-marketing-tags/decorations/travel-demo/dialogs/pages/pageProperties.yaml::
  3. Set complianceType: emptySelectionAllowed: true
  4. Remove http://nightly.magnolia-cms.com/.magnolia/admincentral#app:jcr-browser-app:browser;/travel/complianceType::
  5. Open http://nightly.magnolia-cms.com/.magnolia/admincentral#app:pages-app:detail;/travel:edit
  6. Edit page properties
  7. Try to save -> validation error
  8. Switch to german
  9. Try to save -> validation error
  10. Set a Compliance type
  11. Try to save -> validation error, the field keeps reseting to empty value, validation error.

Note: this happens in 6.2.11 already.

Comment by Vivian Steller [ 10/Sep/21 ]

Also applies to 6.2.8

Comment by Federico Grilli [ 13/Sep/21 ]

For the record, a service pack for Magnolia UI 6.2.11 with this fix only has been released and is available on Nexus. 
Related commits can be seen here https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/commits?until=refs%2Ftags%2Fmagnolia-ui-6.2.11-sp1

Comment by Jörg Wirsig [ 13/Sep/21 ]

Hi fgrilli,

could you provide one or two hints how to include the Service Pack in maven based project. I couldn't find anything in the documentation regarding that topic.  

That would be awesome.

Best regards

Comment by Federico Grilli [ 14/Sep/21 ]

Hello joergwirsig, the Maven group id and artifact id are the same as a regular release, only the version is different, i.e.

<dependency>
 <groupId>info.magnolia.ui</groupId>
 <artifactId>magnolia-ui-project</artifactId>
 <version>6.2.11-sp1</version>
 <type>pom</type>
</dependency>

EDIT: I published a sample Magnolia project illustrating this case
https://git.magnolia-cms.com/users/fgrilli/repos/override-ui-pom-import/browse

Hope this helps.

 

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