-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Category Update without "name" cannot be saved in scope "all" with REST API #22309
Comments
Hi @cmuench. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. @cmuench do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @cmuench. Thank you for working on this issue.
|
Hi @shikhamis11. Thank you for working on this issue.
|
@magento-engcom-team give me 2.3-develop instance |
Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
Hi @shikhamis11, here is your Magento instance. |
✅ Confirmed by @shikhamis11 Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
Hi @niravkrish. Thank you for working on this issue.
|
Hi @cmuench. Thank you for your report. The fix will be available with the upcoming 2.3.2 release. |
Hi @cmuench. Thank you for your report. The fix will be available with the upcoming 2.2.9 release. |
Preconditions
Steps to reproduce
Expected result
Actual result
1.Exception "Could not save category" with message
The "Name" attribute value is empty. Set the attribute and try again.
PUT /rest/all/V1/categories/11 (throws error)
PUT /rest/default/V1/categories/11 (no error)
The text was updated successfully, but these errors were encountered: