GET /rest/test/V1/products/?searchCriteria[pageSize]=1&searchCriteria[currentPage]=50
HTTP/1.1
Host: m2.localhost:8000
Authorization: OAuth oauth_consumer_key="sitoq7tu4b1aj7kikj4irkog8tggh1ch",oauth_token="kr3bly2kbbnrr9flyws9r4mxdaagxngo",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1484095699",oauth_nonce="TivkWr",oauth_version="1.0",oauth_signature="Q02C2wk4AgkDPkYAbACUoLMoXa4%3D"
Cache-Control: no-cache
Is it intended that using a non-"default" store code exposes a global product repository? Reading the documentation it sounds like the request should be limited to the store that's specified:
The value of
store_codecan be one of the following:
- default
- The assigned store code
- all. This value only applies to the CMS and Product modules. If this value is specified, the API call affects all the merchant's stores. GEToperations cannot be performed when you specify all.
I have also attempted a search criteria filter against the following fields: store, store_id, store_code, website, website_id, website_code, all of which return "Invalid attribute name: %1".
I'm unable to find any other alternatives in the documentation. Is there currently no multistore support in the product API, or have I missed something obvious?
Thanks for reporting this. Internal issue is MAGETWO-63667. Related: GH #4806
There is patch available for this ?
Here you go.
https://github.com/magento/magento2/commit/ab6cc894334df162cf4d09fb2ae16d521e8e19e3
you can add .patch to the end of the url to create a patch.
You can find the relevant commits yourself by cloning the repo and grepping the git logs for the internal ticket number, something along the lines of
clone develop from [email protected]:magento/magento2.git
git log | grep -C3 MAGETWO-63667
The output will give you the needed commits.
Was this not merged to 2.2? We're having the same issue still. (see #15461)
problem was reported fixed but problem stil exsist. Hope it wil be fixed soon becouse is a major problem with multiple stores with there own products.
I have the same problem running magento 2.2.6. Thought this was fixed?
Most helpful comment
Was this not merged to 2.2? We're having the same issue still. (see #15461)