-
Notifications
You must be signed in to change notification settings - Fork 9.4k
REST API Product update url_key doesnt re-gerenate url_rewites when single store enabled #32009
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
Conversation
…_rewites when single store enabled
Hi @engcom-Charlie. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento run all tests |
@magento give me test instance |
Hi @danielrussob. Thank you for your request. I'm working on Magento instance for you. |
@magento give me 2.4-develop instance |
Hi @danielrussob. Thank you for your request. I'm working on Magento instance for you. |
Hi @danielrussob, here is your Magento Instance: https://f2f49e8e4d9a6bab831636876b374738-2-4-develop.instances.magento-community.engineering |
Hi @danielrussob, here is your Magento Instance: https://f2f49e8e4d9a6bab831636876b374738.instances.magento-community.engineering |
Checking commit 558d527 in data 10 september 18 there was a refactor on foreach that could cause bug |
@@ -828,9 +828,6 @@ public function getStoreIds() | |||
if (!$this->hasStoreIds()) { | |||
$storeIds = []; | |||
if ($websiteIds = $this->getWebsiteIds()) { | |||
if (!$this->isObjectNew() && $this->_storeManager->isSingleStoreMode()) { | |||
$websiteIds = array_keys($websiteIds); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @engcom-Charlie, thanks for your PR.
I agree that removing this code solves the issue and, as we read in the issue, this code doesn't seem to have any meaning. Actually, @danielrussob found the point in time where the array_keys
was introduced causing the error.
But there is a unit test asserting that the method isSingleStoreMode()
is called once; indeed now it fails because the method is no more called.
So in order for this PR to be processed, we also need to remove that expectation from the failing unit test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirm
@@ -828,9 +828,6 @@ public function getStoreIds() | |||
if (!$this->hasStoreIds()) { | |||
$storeIds = []; | |||
if ($websiteIds = $this->getWebsiteIds()) { | |||
if (!$this->isObjectNew() && $this->_storeManager->isSingleStoreMode()) { | |||
$websiteIds = array_keys($websiteIds); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirm
Hi @danielrussob, thank you for the review. |
✔️ QA Passed The result is the same as in the report above #32009 (comment) |
…ewites when single store enabled #32009
Hi @engcom-Charlie, thank you for your contribution! |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)