Issue Creating Locales For Single Types

[seivad]

Bug report

Required System information

• Node.js version: 18.19.1
• NPM version: 10.2.4
• Strapi version: 4.20.4
• Database: Postgres
• Operating system: Mac OS
• Is your project Javascript or Typescript: Javascript

Describe the bug

A clear and concise description of what the bug is.

Steps to reproduce the behavior

Create a single component with a repeatable zone area.

Put in items in English and save.

Select new Locale and fill in from the English version, hit save and the following error occurs:

Error: 1 relation(s) of type api::footer.footer associated with this entity do not exist

Also noticed that the database locale column just gets saved as "en" even though it might be Japanese, German etc...

Expected behavior

Create the single component when multiple dynamic parts, hit save when making it for a new locale and it works

Screenshots

[AndreiMrakov]

@seivad Also reproduced for me. What about issue with replaced localized version it's described in #19652

[angelmadames]

It's also happening to me on v4.20.4.
Seems to be a regression from #19225?

[seivad]

It seems to be an on-going issue now since 4.17.x+, I'm new to Strapi so it hasn't been the best first experience to come across this so early on using it as a CMS. I edited the DB columns manually, but that isn't ideal as new content types get added.

[ihassansattar]

When will this be fixed? It's blocking our new release.

[alex-lechner]

I have the same issue. I tried to change the default locale as a workaround but that did not work.

EDIT: Downgrading from the latest version 4.20.4 to version 4.20.1 worked for me! @derrickmehaffy it seems an unintentional bug was introduced in a subsequent release.

[Marc-Roig]

should be fixed in #19799