Non-localizable fields don't keep their value after locale switch and no "fill in from another locale" button in collection types

[drazik]

Bug report

Required System information

• Node.js version: 18.12.1
• NPM version: 8.19.2
• Strapi version: 4.12.5
• Database: MySQL 5.7
• Operating system: Ubuntu 22.04.3
• Is your project Javascript or Typescript: Typescript

Describe the bug

I have two locales in my application: fr (default) and en. I have a team-member collection type with 3 non-localizable fields and 1 localizable field. When I fill the FR locale data and save it, then switch to English locale, I don't see the "Fill in from another locale" button and all the fields are empty, forcing me to re-type all the non-localizable fields data.

After filling the EN data and saving, the "Fill in from another locale" button appears.

The problem also exist on edit.

Steps to reproduce the behavior

1. Create an item in a collection type with localizable fields
2. Fill all fields of the default locale
3. Save it
4. Switch to another locale
5. Non-localizable fields are empty and "Fill in from another locale" button is absent

Expected behavior

The non-localizable fields should keep the value entered for the default locale, and the "Fill in from another locale" button should be visible.

Screenshots

Default locale (FR) data entered and saved:

After switch to other locale (EN):

Code snippets

N/A

Additional context

N/A

[bennyhoyer]

i have the same issue as described by @drazik after updating from 4.10.5 to 4.12.5. (node 18.17.1)

reloading the page loads the "Fill from another locale" button, but it would be helpful to have the old behavior back.

[lukesmmr]

We have the same issue after updating from 4.10.5 to 4.12.5. As @BennyMoser points out, reloading the page fixes it and allows our editors to populate from the other locale. This is particularly important if you have non-localized fields that you don't want to type in again. Having to reload the page is not an ideal flow.

Interesting enough, I cannot reproduce this locally with 4.12.5 with a sqlite database on Mac OS.
We are running on:

• Node.js version: 18
• Strapi version: 4.12.5
• Database: Postgres
• Operating system: Ubuntu
• Is your project Javascript or Typescript: JavaScript

[rktyt]

Same issue.
strapi v4.12.6

We have upgraded from 4.11.3 to 4.12.1 and then to 4.12.6.
However, we are not upgrading the production environment because of a critical bug for us.
This is one of them.

[derrickmehaffy]

Might be related to (or duplicate of #17860)

[Eventyret]

Escalated due to confirmation from TID 4804

[MAxiaq]

Any update on this, I ran into the same problem after updating to 4.14.0. Is this being looked into?

[Boegie19]

I am 99% sure it does since they escalated it due to an internal ticket of an enterprise user.
And if not they will look at it shortly.

[lukesmmr]

Any update on this issue? We can still verify this behaviour in 4.14.3.

[derrickmehaffy]

I've mentioned it to our engineers in a call yesterday (specifically to an engineering manager) and they will take a look.

However it looks like a community member has made a PR that might also resolve it.

[joshuaellis]

I've just taken a look at this issue using our latest main version and i've not been able to reproduce (see video attached) have you upgraded and rechecked the issue is still happening?

CleanShot.2023-10-19.at.10.25.46.mp4

[github-actions]

This is a templated message

Hello @drazik,

Thank you for reporting this bug, however we are unable to reproduce the issue you described given the information we have on hand. Can you please create a fresh project that you are able to reproduce the issue in, provide clear steps to reproduce this issue, and either upload this fresh project to a new GitHub repo or compress it into a .zip and upload it on this issue?

We would greatly appreciate your assistance with this, by working in a fresh project it will cut out any possible variables that might be unrelated.
Please note that issues labeled with status: can not reproduce will be closed in 14 days if there is no activity.

Thank you!

[JustTB]

I can still reproduce it after update to current version v4.14.5
Since this is a race condition (looking at the fix above) you might try more complex types with relations.
v4.14.5 did not solve that for us.

[bennyhoyer]

I can confirm that this problem occurs in the latest version 4.14.5.

It took me 5 minutes to reproduce this error with the normal strapi create cli. All I did was add a localizable collection type and even with just one field the error is reproducible.
Here is the link for my project, hoping someone can fix this problem:
https://github.com/BennyMoser/strapi-localization-bug

strapi-bug.mp4

[derrickmehaffy]

I'm also able to reproduce the issue but the "fill in button" doesn't even exist anymore for me either:

https://www.loom.com/share/9c0393ec505b4f1aab724e7719089eed?sid=27ca6f0e-7a46-40fb-8fe8-cdc853990c41

[sam-gre]

I can confirm the same. I have upgraded to the latest stable version of strapi (4.15.4) and have the exact same issues. Something i noticed is that if the locale already has content, the "fill from another localed" appears. If no content, then it requires the reload for it to appear.

[JustTB]

It would be really nice if this issue gets some attention. Since the PR is open with a comment from January that it will be fixed in the afternoon. Please, please fix. 🙏🏽 🥺

[hanpaine]

Thanks for your patience folks - we're hoping to get the fix merged this week and deployed next 🤞🏻

[derrickmehaffy]

It would be really nice if this issue gets some attention. Since the PR is open with a comment from January that it will be fixed in the afternoon. Please, please fix. 🙏🏽 🥺

Sorry about that, fell off my radar. PR updated and hopefully should be merged soon.