-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Culture and LocalizationSet are not set for LocalizationPart if content is created programmatically #15713
Comments
Can you show me how you create your content programatically? |
This can be done for instance via custom mutation:
|
I thought you create it via a normal migration |
Is there any chance to approve related MR #15714? |
I'm still waiting for a unit test or I code snippet to reproduce the issue |
The above code snippet should be enough, Hisham. |
I will try to create another migration for a content type that has a |
Please do that. |
I already did and approved the PR |
Great then! |
Describe the bug
Culture and LocalizationSet are not set for LocalizationPart if content is created programmatically.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Localization settings are available for newly created content.
Screenshots
Localization settings are not available for newly created content.
The text was updated successfully, but these errors were encountered: