Issue fix #18264: Wrong special_price in indexer database tables for bundle products. #23056
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (*)
Issue was already fixed in M2.2.8 but only for Configurable products. Same situation relates to Bundle product prices and it's indexer (SQL). All conditions there are correct, but are not grouped which results with wrong special_price data populating in indexer database tables.
Fixed Issues (if relevant)
Manual testing scenarios (*)
special_price_from
andspecial_price_to
, but having one product with special date valid for the day of testing.Results:
Products are sorted as if they have same (special) price, but displayed price is correct according to dates set in
special_price_from
andspecial_price_to
fields.In
catalog_product_index_price
table all three products have set special_price.Questions or comments
As I checked the issue is presenting in M2.3-develop as well.
Contribution checklist (*)