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.

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

[Bug]: Gender field keeps getting renamed #845

Open
Navino16 opened this issue Feb 24, 2025 · 3 comments
Open

[Bug]: Gender field keeps getting renamed #845

Navino16 opened this issue Feb 24, 2025 · 3 comments
Labels

Comments

@Navino16
Copy link
Contributor

Pimcore version

v2024.4

Steps to reproduce

  1. Create a Gender field on any class
  2. Rename it "testGender" for example
  3. Save your class definition
  4. Reload class definition

Actual Behavior

Your field is now named "gender" instead of "testGender"

Expected Behavior

Either lock field name like firstname or lastname fields.
Or block field rename if a name is already present

@Navino16 Navino16 added the Bug label Feb 24, 2025
@mattamon
Copy link
Contributor

@Navino16 I will move the issue to the admin-ui-classic-bundle since the error occurs there.

@mattamon mattamon transferred this issue from pimcore/pimcore Feb 28, 2025
@mattamon
Copy link
Contributor

mattamon commented Feb 28, 2025

Took a quick look at the code and discovered that is actually saved correctly, but in the frontend it seems to be set as fixed input.
Same behavior actually for first or lastname, but here the name fields are disabled. So I need to investigate a little more if it is actually intended behavior but the disabling was forgotten.

@fashxp
Copy link
Member

fashxp commented Mar 3, 2025

I think 'disabling was forgotten' is the cause - or it got lost some where...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants