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
Product is still visible in catalog search after setting category permission to only logged in customers in magento2.4.6 #38710
Comments
Hi @afzelarshad. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Magento 2.4.6 Enterprise Edition: |
Hi @engcom-Dash. Thank you for working on this issue.
|
Hi @afzelarshad , Verified the issue on 2.4-develop in commerce edition and it is not reproducible. Steps to reproduce:- 1.Go to Catalog ->Categories Please refer the attached screenshot and let us if we are missing something. Catalog->Categories->Selected a category For Not Logged in customers it is allowed We can see the category and product available For Not Logged in customers it is saved as not allowed We are not able tp see the category and product available |
Preconditions and environment
Steps to reproduce
category permission is set to logged-in customers only, but when non-logged-in customers search for any product of this category on the front end the product is visible.
Expected result
if category permission is set to log-in users only then its product shouldn't be displayed for non-logged-in customers,
if a product consists of multiple categories like one category is restricted for non-logged-in customers and one category is allowed for non-logged-in customers then it should display the product on the frontend because it consists of a category whose permission is set to allow for non-logged-in customers. front end
Actual result
No product found matching your query something like that
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: