Non-localized fields data loss when filling from another locale

[rsandgarten]

Bug report

Required System information

• Node.js version: v18.17.1
• NPM version: 9.6.7 (not using npm)
• Yarn version: 1.22.19 (using yarn)
• Strapi version: 4.15.4 (but was also noted on my prod environment on 4.14.4)
• Database: SQLite (also on prod environment with postgresql)
• Operating system: Windows (also on prod environment linux dockerized)
• Is your project Javascript or Typescript: Javascript

Describe the bug

When using internalization, the fields that are not localized (advanced setting configuration) get lost when using the "Fill in from another locale" button. This is very frustrating when we already filled up a list of images, we lose them, and we need to set those up again.
An additional note, and probably related, is that the "Fill in from another locale" button does not show up right after you switch the language.

UPDATE: This is only happening with media data type fields (images, documents, etc), not with other data types. Still, it's frustrating enough to lose plenty of selected images when setting up a new language.

Steps to reproduce the behavior

1. yarn create strapi-app my-project --quickstart
2. Add new language. In my case: Spanish (Argentina) (es-AR)
3. Add new collection type. Example "Restaurant", and enable Internationalization.
4. Add "name" text field, with "Enable localization on this field" enabled (checked)
5. Add "photo" media field (single image), with "Enable localization on this field" DISABLED (unchecked).
6. Create a dummy entry on default locale (en). Input name, and upload photo image. Save.
7. Change language (es-AR) from selector. Note how "Fill in from another locale" button is missing.
8. Hit Save on new locale
9. Note "Fill in from another locale" button now shows up. Click it and choose English (or whatever default language)
10. Confirm and save.
11. Note only the "name" was filled, but "photo" is empty.
12. Switch back to original language.
13. Note photo is empty for all languages.

Expected behavior

I would expect not to loose data (images or whatever data type field) on non-localized fields, whenever I fill in from another locale. Also, I would expect the "Fill in from another locale" button to show up right after I switch language.

Screenshots

Code snippets

N/A

Additional context

N/A

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/dont-understand-why-fill-in-from-another-locale-is-sometimes-not-available/32842/8

[rsandgarten]

For now, the workaround I've come up with (for new content), is to create entries for both languages BEFORE starting to upload images. Obviously, this is not the desired solution, since I have to make sure the content management team proceeds this way. Otherwise, they'll have to make the same workload twice.

[spenya]

A workaround I found, while this issue remains unresolved, is to use the REST API to create every localized version. This approach does not overwrite existing data in the original language. When you open it, the 'Fill with another locale' button is available. By clicking on it, you can populate the common elements. After that, you can edit the localizable fields with the translations from the admin!

I tryed it from postman, but you I will make a script to automate it as I have many contents with shared data to be translated, as my site is already in production...

Ho to do it:

POST to:

[https://my.strapi.endpoint]/api/[content-type]/:id/localizations

sending a JSON as follows:

{ "locale": "es-ES", }

[PoliPH]

We have the same issue in our company, we had strapi 4.11.1 version and we updated to 4.15.5, now we can not fill the data when we create the entity for other language, but we can fill when the entity is already created.

We need a fix because this save us a lot of time when we create our entities. My package.json:

  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.38.0",
    "@typescript-eslint/parser": "^5.38.0",
    "eslint": "^8.23.1",
    "eslint-config-prettier": "^8.5.0",
    "eslint-import-resolver-typescript": "^3.5.1",
    "eslint-plugin-import": "^2.26.0",
    "eslint-plugin-prettier": "^4.2.1",
    "prettier": "^2.7.1"
  },
  "dependencies": {
    "@offset-dev/strapi-calendar": "^0.0.10",
    "@strapi-community/strapi-provider-upload-google-cloud-storage": "^4.10.5",
    "@strapi/plugin-i18n": "4.15.5",
    "@strapi/plugin-users-permissions": "4.15.5",
    "@strapi/strapi": "4.15.5",
    "axios": "^1.6.2",
    "inversify": "^6.0.1",
    "kafkajs": "^2.2.0",
    "mysql": "2.18.1",
    "reflect-metadata": "^0.1.13",
    "strapi-auto-uuid": "^0.0.8",
    "strapi-plugin-config-sync": "^1.1.2",
    "strapi-plugin-populate-deep": "^3.0.1",
    "uuid": "^9.0.1",
    "vitest": "^0.24.3",
    "winston": "^3.8.2"
  },

[maper89]

Same issue on latest version v4.16.2

[rasander]

I can confirm having the same on v4.16.2

[Nicolas-Deleplace]

Same on 4.17.0

[sevbauer]

Workaround:

• Switch to the other language (don't save)
• Reload the page -> now the button "Fill in from another locale" appears below the Locale-Dropdown
• Now when you fill in from the other locale, the non-localized fields are kept

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/dont-understand-why-fill-in-from-another-locale-is-sometimes-not-available/32842/11