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]: publishing object with Localized Fields set as mandatory with no mandatory languages result in validation error. #904

Open
br33f opened this issue Oct 25, 2024 · 1 comment

Comments

@br33f
Copy link

br33f commented Oct 25, 2024

Expected behavior

Object is published successfully, since all localized fields are filled in.

Actual behavior

An error: "Validation failed: Empty mandatory field [ Name ][ localizedfields- ]" is thrown.

Steps to reproduce

Pimcore 11.4.1
DataHub: 1.8.2
PHP: 8.2.19

  1. In System Settings make sure none of the frontend languages in "Localization & Internationalization (i18n/l10n) is marked as "Mandatory language"
  2. Create a class of object which contains at least one "Localized Fields", in my example "Name".
  3. Make sure this field inside "Localized Fields" is marked as "Mandatory field"
  4. Create a new object of that class. Fill all the data for this Localized Field (every language).
  5. Try to Save & Publish this object.

And the validation error is thrown despite this field being filled in all languages and even though none of the languages is even marked as Mandatory.

@br33f br33f added the Bug label Oct 25, 2024
@br33f br33f changed the title [Bug]: publishing object with Localized Fields set as required with no required languages result in validation error. [Bug]: publishing object with Localized Fields set as mandatory with no mandatory languages result in validation error. Oct 25, 2024
Copy link

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.

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

No branches or pull requests

1 participant