-
Notifications
You must be signed in to change notification settings - Fork 9.4k
MC-40780: Moving category in hierarchy causes url_path to be incorrect when using different url keys in multiple storeviews #32598
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
Hi @victorpetryk. 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 |
01bf963
to
6793d5f
Compare
@magento run all tests |
@magento run Integration Tests |
1 similar comment
@magento run Integration Tests |
@magento run all tests |
@magento run all tests |
1 similar comment
@magento run all tests |
->columns(['c.value']) | ||
->where(implode(' AND ', $whereConditions)); | ||
|
||
return current($connection->fetchCol($select)); |
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.
Why not using fetchOne()?
return current($connection->fetchCol($select)); | |
return $connection->fetchOne($select) ?: null; |
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.
Fixed
* Retrieve 'url_key' value for default store. | ||
* | ||
* @param int $categoryId | ||
* @return string|bool |
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 would be better to return string|null
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.
Fixed
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.
Then we always need add check for a null, which is not good, i think it will be better return always string as per strict type, and in case of empty result empty string. What do you think ?
@@ -90,6 +100,12 @@ public function execute(\Magento\Framework\Event\Observer $observer) | |||
$resultUrlKey = $category->formatUrlKey($category->getOrigData('name')); | |||
$this->updateUrlKey($category, $resultUrlKey); | |||
} | |||
if ($category->hasChildren()) { | |||
$defaultUrlKey = $this->getDefaultUrlKey->execute((int)$category->getId()); | |||
if (!empty($defaultUrlKey)) { |
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.
Could be simplified to:
if (!empty($defaultUrlKey)) { | |
if ($defaultUrlKey) { |
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.
Fixed
…t when using different url keys in multiple storeviews
@magento run all tests |
@zakdma the branch with code successfully imported into |
Hi @victorpetryk, thank you for your contribution! |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
See #16202
Questions or comments
Contribution checklist (*)