[BUG]: Showing error after translate from default language

[raghav-zwt]

Describe the bug
When clicking on "Yes, fill in" after showing an error like "Woops! Something went wrong. Please, try again."

To Reproduce
Steps to reproduce the behavior:

1. Go to the edit page and click on 'Translate from another locale'
2. Click on "Yes, fill in" https://prnt.sc/CZI9rf4tC5I-
3. After Seeing an error like "Woops! Something went wrong. Please, try again."

Expected behavior
It should filled inputs in selected language

Screenshots

• https://prnt.sc/CZI9rf4tC5I-
• https://prnt.sc/uk5hNCvCv7J3

System (please complete the following information):

• OS: MAC
• Browser chrome
• Versions:
  • strapi: 4.9.0
  • strapi-plugin-translate: 1.1.5
  • provider: [email protected]

Plugin config
Please add your plugin config here, e.g.

module.exports = {
  translate: {
    enabled: true,
    config: {
      provider: 'deepl',
      providerOptions: {
        apiKey: '*************'
      },
      translatedFieldTypes: [
        'string',
        { type: 'text', format: 'plain' },
        { type: 'richtext', format: 'markdown' },
        'component',
        'dynamiczone',
      ],
      translateRelations: true,
    },
  },
}

[layaxx]

Hi @raghav-zwt,
thanks for filing your bug report.
I think I will need additional information in order to investigate this:

• The editor in the background of your screenshot does not look like the default editor, is this a plugin?
• are there any error messages / non-sucssfull requests in the browser console which you could share?

[Imran-cse]

@layaxx I'm facing the same issue. Showing the following error in the console.

[layaxx]

Hi @Imran-cse,

• are you using other plugins besides strapi-plugin-translate?
• what (type of) fields does the entity you are trying to translate consist of?

[Imran-cse]

@layaxx Yes I'm using other plugins but for translating only using this one.

Entity consists of all the types of entity the plugin supports as markdown, dynamiczone, string, components.

[Shekhar-Zealous]

@layaxx Error is generated when click on save for the different locale data after the data is translated. Check the below error image:

[layaxx]

Hi @raghav-zwt @Imran-cse @Shekhar-Zealous,
I have so far not been able to reproduce this problem.
Again, could you please list your others plugins, even if they are not directly related to translation? From the screenshots it looks like you are using a non-default editor for your richtext fields.
Apart from that, would any one of you be able to share a minimal reproduction example?

[Shekhar-Zealous]

Hi @raghav-zwt @Imran-cse @Shekhar-Zealous, I have so far not been able to reproduce this problem. Again, could you please list your others plugins, even if they are not directly related to translation? From the screenshots it looks like you are using a non-default editor for your richtext fields. Apart from that, would any one of you be able to share a minimal reproduction example?

I am using CKEditor 5 plugin for text editor. As far as I know, the editor is not creating any problems :/
There is something wrong with the plugin.

[layaxx]

Ok, i still cannot reproduce this, so CKEditor might in fact not be related to this. There might very well be something wrong with this plugin, but I cannot work on fixing it unless I can reproduce this error.

@Shekhar-Zealous Could you share the schema.json files of the content-types you encountered this issue with? Same actually also goes for your other issue (#232)

[Shekhar-Zealous]

@layaxx It's happening with each of the collections where we have used this SEO component.
Its creating issue only when the SEO component is populated after translate https://prnt.sc/tpugsceGvIHF.
The record is saved after removing this component which is kinda odd.
This console error and image delete error appearing for same component. Not able to find the issue after a lot of debugging :(

[Shekhar-Zealous]

@layaxx @sargreal You can close this bug as it was fixed with this issue #246