Fekide / strapi-plugin-translate

Strapi plugin for automated translations using different Translate Providers
https://market.strapi.io/plugins/strapi-plugin-translate
MIT License
45 stars 18 forks source link

[BUG]: Translate from another locale Link #349

Closed MarcosVVMK closed 7 months ago

MarcosVVMK commented 10 months ago

Describe the bug

I found a plugin bug that occurs in strapi versions above 4.11.7, in the part where the "Translate from another locale" link of the collection type should appear, it only appears after the screen is reloaded.

To Reproduce Steps to reproduce the behavior:

  1. Install the strapi translate plugin in a strapi project with a version above v4.11.7
  2. Add at least 1 more locale
  3. Access a post of any collection type
  4. Click on the locales dropdown and select another language for translation
  5. The Translate from another locale button does not appear unless the page is reloaded

Expected behavior The button with the text "Translate from another locale" should appear without having to reload the page

Screenshots

https://imgur.com/a/54WBVYo

System (please complete the following information):

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

 translate: {
    enabled: true,
    config: {
      provider: 'chatgpt',
      providerOptions: {
      },
      translatedFieldTypes: [
        'string',
        { type: 'text', format: 'plain' },
        { type: 'richtext', format: 'markdown' },
        'component',
        'dynamiczone',
      ],
      // If relations should be translated (default true)
      translateRelations: false,
    },
  },
sargreal commented 10 months ago

Hi @MarcosVVMK and thanks for opening this issue.

I have tested a bit and found that "Fill in from another locale" does also not work in the i18n Plugin where much of this plugin's code is based on. I have created an upstream issue which addresses the root cause: https://github.com/strapi/strapi/issues/18601

sargreal commented 7 months ago

This issue has most likely been solved in Strapi v4.19.1, at least I don't see the issue anymore