[FRONTIFY-16] Widget causes issue with internationalized fields inside a multivalue field Created: 14/Mar/23  Updated: 21/Sep/23  Resolved: 21/Sep/23

Status: Closed
Project: Frontify
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: 1.0.2

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Riste Drangovski
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by JSFIELD-34 i18n multifield values not saved in J... Resolved
dependency
depends upon JSFIELD-34 i18n multifield values not saved in J... Resolved
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Consider the following configuration for a dialog:

form:
  implementationClass: info.magnolia.ui.javascript.form.FormViewWithChangeListener
  properties:
    title:
      $type: textField
      i18n: true
      required: true
    keySellingPoints:
      required: true
      $type: jcrMultiField
      field:
        $type: compositeField
        properties:
          title:
            label: Title
            i18n: true
            $type: textField
          description:
            label: Description
            i18n: true
            rows: 3
            $type: textField
    image:
      $type: frontifyWidgetField
      height: 220

Reproduce
Try filling out the internationalized fields with content. Save the dialog. Reopen the dialog.

Expected
When reopening the dialog all internationalized fields should display their content.

Actual
Only some language data is displayed within the multivalue field. In the case of two languages (en and de) you only get one language. If you toggle the language selector in the detail subapp it can happen that both data go missing after a few tries of closing and reopening the dialog.

Notes

  • When removing the frontifyWidgetField the dialog behaves as expected.
  • Data is saved correctly to the JCR.


 Comments   
Comment by Alberto Ramirez [ 21/Mar/23 ]

Hi,

any estimated dates?

Thanks!

Comment by Riste Drangovski [ 21/Mar/23 ]

Hi Alberto,
Not yet, I would suggest as workaround to put "i18n: true" on the multifield "keySellingPoints" and not on the subfields.
I know it's not a same behaviour, but at least you will be able to translate the multifield until we solve this issue.

BTW, issue comes from javascript field that frontify field extends, so we need to dig a bit deeper in the code.

Regards,
Riste

Comment by Alberto Ramirez [ 21/Mar/23 ]

Thanks for your fast answer Riste.

Unfortunately we cant do that, because we have alreadedy a lot of information contributed thats depends on our current structure.

We will wait until you come with a solution to upgrade the module.

Best,

Alberto.

Comment by Riste Drangovski [ 17/Apr/23 ]

Hi Alberto,

for your information, this ticket is transferred to jsFields module: https://jira.magnolia-cms.com/browse/JSFIELD-34
work on the issue is in progress and fix is scheduled for the next (2.0.1) release.

Regards,
Riste

Comment by Riste Drangovski [ 17/May/23 ]

Hi Alberto,

Sorry, it took a bit longer then expected, but we have a hotfix for this issue.
You can check the frontify-dam-connector-1.0.3-MGNLUI-8037 hotfix release.
You can add it with

<dependency>
  <groupId>info.magnolia.external.dam</groupId>
  <artifactId>frontify-dam-connector</artifactId>
  <version>1.0.3-MGNLUI-8037</version>
</dependency>

in the project.

I hope it will solve the problem. Please let us know if this works for you!

Regards,
Riste

Comment by Alberto Ramirez [ 17/May/23 ]

Hi Riste,

Thanks for the update!!

We are going to try it now. Reading your respositories, it seems we can go with the 6.2.33 version of magnolia and dont need to update to the 6.2.34, is it that correct?

Thanks again.

Comment by Riste Drangovski [ 18/May/23 ]

Hi Alberto,

yes, you don't need to update to 6.2.34 version.

Regards,
Riste

Generated at Mon Feb 12 02:03:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.