Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unique and localisation - checks in all languages #12248

Closed
HannesOberreiter opened this issue Jan 19, 2022 · 3 comments
Closed

Unique and localisation - checks in all languages #12248

HannesOberreiter opened this issue Jan 19, 2022 · 3 comments
Labels
fix:5 Fixed in Strapi 5 issue: feature request Issue suggesting a new feature source: core:content-manager Source is core/content-manager package
Projects
Content - Old

Comments

@HannesOberreiter
Copy link

Bug report

Describe the bug

Unique fields are checked in all languages and therefore you cannot same value in different languages. To be honest, I don't know if that is expected.

Steps to reproduce the behavior

  1. Create a Content-Type with a text-field with attributes "Enable Unique" and "Enable localization for this field" enabled.
  2. Create a "New Entry" for this Content-Type and write for example the text value "Tourist" for English
  3. Now create for example the "German" localisation which would be the same: "Tourist"
  4. You get an error that the value is not "Unique"

Expected behavior

The "unique" check should only apply to one language.

System

  • Docker: strapi/base:latest (tag 14)
  • Strapi version: 4.0.4

Additional context

Somewhat similar issue: #10694

Cheers
Hannes
@derrickmehaffy derrickmehaffy added issue: bug Issue reporting a bug severity: medium If it breaks the basic use of the product but can be worked around source: core:content-manager Source is core/content-manager package status: confirmed Confirmed by a Strapi Team member or multiple community members labels Jan 20, 2022
@derrickmehaffy derrickmehaffy added this to To be reviewed (Open) in Content - Old via automation Jan 20, 2022
@petersg83 petersg83 added issue: feature request Issue suggesting a new feature and removed issue: bug Issue reporting a bug severity: medium If it breaks the basic use of the product but can be worked around status: confirmed Confirmed by a Strapi Team member or multiple community members labels Jan 25, 2022
@yanniskadiri
Copy link

This is an issue related to this one too: #10107
It's not the same use case but it's the same cause. It's a feature request we will address in the future. Thanks for sharing your use case :)

@yanniskadiri yanniskadiri moved this from To be reviewed (Open) to Reviewed in Content - Old Jan 25, 2022
@petersg83 petersg83 mentioned this issue Feb 15, 2022
Closed
@derrickmehaffy derrickmehaffy mentioned this issue Feb 15, 2022
Closed
@derrickmehaffy
Copy link
Member

Closing and locking in favor of the tracking issue: #12538

Content - Old automation moved this from Reviewed to Fixed/Shipped Feb 15, 2022
@strapi strapi locked and limited conversation to collaborators Feb 15, 2022
@jhoward1994
Copy link
Contributor

This issue has been fixed in v5 from 5.0.0-beta.13 onwards via #20427

@jhoward1994 jhoward1994 added the fix:5 Fixed in Strapi 5 label Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
fix:5 Fixed in Strapi 5 issue: feature request Issue suggesting a new feature source: core:content-manager Source is core/content-manager package
Projects
Developer Experience Squad
Status: Fixed/Shipped
Content - Old
Fixed/Shipped
Milestone
No milestone
Development

No branches or pull requests
5 participants
@derrickmehaffy @petersg83 @HannesOberreiter @yanniskadiri @jhoward1994