-
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
BUG: Category Repository get()'s argument store_id
does not work
#27044
Comments
Hi @lbajsarowicz. 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. @lbajsarowicz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
store_id
does not workstore_id
does not work
I can't reproduce this issue on version 2.4-develop. Please take a look at my record: https://youtu.be/oVCcF9Av06E |
Let me verify that, as I also covered that with integration test and... Isolated, that problem does not occur. |
…$storeId) attribute
Problem is actually related to internal cache storage. |
Hi @lbajsarowicz. Thank you for your report. The fix will be available with the upcoming 2.4.0 release. |
…Repository `get()` #27048
Description
The implementation of
$storeId
support was never finished.Preconditions (*)
2.4-develop
Steps to reproduce (*)
default
with ID1
extra
with ID2
url_key
value:category-1
(let's assume it's ID is333
)extra
storeurl_key
to valuesome-magic-key
CategoryRepositoryInterface
$categoryRepository->get(333, 2)
Data is properly saved in the MySQL table:
Expected result (*)
url_key
=some-magic-key
is returnedActual result (*)
url_key
=category-1
is returnedRelated issues
Not related issues
The text was updated successfully, but these errors were encountered: