Magento2: Requesting products via REST API using store code in URL returns products from all stores

Created on 23 May 2018  路  13Comments  路  Source: magento/magento2

Preconditions

  • Magento 2.4-develop;
  • Integration created;

Steps to reproduce

  1. Create a website with code wb2.
  2. Create a store st2 and assign it to the wb2 website.
  3. Create a store view with code sv2 and assign to the new store.
    image

  4. Create product and assign only to wb2 website.
    image

  5. Perform REST API GET request using the store code in the URL, eg:
    GET /rest/default/V1/products/?searchCriteria[currentPage]=10

Expected result

Only products assigned to the test website are returned (or no products if none assigned).

Actual result

All products in the Magento instance are returned.
image

FrameworWebapi Clear Description Confirmed Format is valid Ready for Work P2 done Reproduced on 2.1.x Reproduced on 2.2.x Reproduced on 2.3.x Reproduced on 2.4.x S2 Dev.Experience

Most helpful comment

dont think this will ever be fixed.
this is second time that this problem is in Magento and i have posted this more then a year ago and no response anymore in that time.
Only sollution (what we are also working on nowe) is to stop using magento.
We are building a new webshop now on other ecommerce software becouse of this problem.

All 13 comments

@Vossie1975, thank you for your report.
We've acknowledged the issue and added to our backlog.

any idea when this bug wil be fixed (again)?

Typical Magento. Another major bug that is being left to gather dust...

Any update?

probably not....
Does not seem interesting for Magento to solve this.
This bug was previously in the system and would have been resolved then.
But is there again / still in it.
I have now reported this almost a year ago, but not a single update since that time.
Recently also other bugs found (in MSI function) but why would you still take the trouble to report it if nothing is done with it ....

Will this be resolved? Am still seeing this issue on 2.3.1

I am running magento 2.2.6 and this is a huge problem for us right now. Is there anyway to workaround this?

dont think this will ever be fixed.
this is second time that this problem is in Magento and i have posted this more then a year ago and no response anymore in that time.
Only sollution (what we are also working on nowe) is to stop using magento.
We are building a new webshop now on other ecommerce software becouse of this problem.

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:


    1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
    1. If the issue is not relevant or is not reproducible any more, feel free to close it.

are there any updates ?

Hi @anansin-magento. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:


    1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
    1. If the issue is not relevant or is not reproducible any more, feel free to close it.

now after more than 2.5 years, but this problem remains.
Fixing bugs like this is clearly not a priority.
I have not even reported other bugs.
In the meantime, therefore, also busy with dumping Magento and switching to other webshop software that is more user-friendly and where problems are solved.

Just go use other software. This Wil never be solved by magento

Was this page helpful?
0 / 5 - 0 ratings