Skip to content
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

Default store price is showing on search and list page #3

Open
mukdam opened this issue May 9, 2022 · 5 comments
Open

Default store price is showing on search and list page #3

mukdam opened this issue May 9, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@mukdam
Copy link

mukdam commented May 9, 2022

Hello Team,

We facing an issue with store prices not showing correctly on the listing and search list rest all pages showing correctly. on search and list page it is showing the default store price.

MicrosoftTeams-image_1
MicrosoftTeams-image

@mukdam
Copy link
Author

mukdam commented May 9, 2022

Same issue with fresh Magento 2.4.4

Screenshot from 2022-05-09 21-33-12
Screenshot from 2022-05-09 21-33-06
Screenshot from 2022-05-09 21-32-43
Screenshot from 2022-05-09 21-32-29
Screenshot from 2022-05-09 21-32-22
Screenshot from 2022-05-09 21-32-13

@MagePsycho MagePsycho changed the title Showing default store price on on searc and list page Default store price is showing on search and list page May 9, 2022
@mukdam
Copy link
Author

mukdam commented May 11, 2022

Hello Team,

are you able to reproduce the same case?

@MagePsycho MagePsycho added the bug Something isn't working label May 23, 2022
@leissbua
Copy link

The module is completely ignoring the table: "catalog_product_index_price", so pricing in search and category listing is always joined from website default scope. As it is not working for those page types the module is not solving pricing on store view level.
Thank you for your effort anyway, but the module is sadly not usable.

@MagePsycho
Copy link
Owner

@leissbua
Yeah, this is a known issue for category listing pages.

On a high level, this can be fixed on the indexing level by creating a new table ex: catalog_product_index_price_store which will have store_id wise price instead of website_id.
And then in the frontend part, you can tweak the join with catalog_product_index_price_store and add store_id as a filter.

Currently pretty much occupied with other projects. Any PRs are warmly welcome!

@leissbua
Copy link

leissbua commented Nov 24, 2022

The implementation of changing the scope to a store view level is the easy part of the job as its simply an eav attribute. the hard part is the price indexer + catalog rule indexer and that part is missing completely. Thanks for your answer and effort, but we have no time as well currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants