Negative price filter in Layered Nav Magento 2.2
Currently experiencing issue with layered Nav price filter. The price ranges are completely incorrect. Default filter is showing price range -10 to 395
http://prntscr.com/jp1r63
Applying price range filter just seems to throw random products in the results.
Tried: Reindexing via CL Disabling Side bar extension (native magento
side bar still having same issue) Checked price attribute setup in
admin
Env:
- Magento 2.2.0
- PHP 7.1
- Centos 7
Any hints appreciated
magento2 magento2.2 layered-navigation filter php-7.1
add a comment |
Currently experiencing issue with layered Nav price filter. The price ranges are completely incorrect. Default filter is showing price range -10 to 395
http://prntscr.com/jp1r63
Applying price range filter just seems to throw random products in the results.
Tried: Reindexing via CL Disabling Side bar extension (native magento
side bar still having same issue) Checked price attribute setup in
admin
Env:
- Magento 2.2.0
- PHP 7.1
- Centos 7
Any hints appreciated
magento2 magento2.2 layered-navigation filter php-7.1
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46
add a comment |
Currently experiencing issue with layered Nav price filter. The price ranges are completely incorrect. Default filter is showing price range -10 to 395
http://prntscr.com/jp1r63
Applying price range filter just seems to throw random products in the results.
Tried: Reindexing via CL Disabling Side bar extension (native magento
side bar still having same issue) Checked price attribute setup in
admin
Env:
- Magento 2.2.0
- PHP 7.1
- Centos 7
Any hints appreciated
magento2 magento2.2 layered-navigation filter php-7.1
Currently experiencing issue with layered Nav price filter. The price ranges are completely incorrect. Default filter is showing price range -10 to 395
http://prntscr.com/jp1r63
Applying price range filter just seems to throw random products in the results.
Tried: Reindexing via CL Disabling Side bar extension (native magento
side bar still having same issue) Checked price attribute setup in
admin
Env:
- Magento 2.2.0
- PHP 7.1
- Centos 7
Any hints appreciated
magento2 magento2.2 layered-navigation filter php-7.1
magento2 magento2.2 layered-navigation filter php-7.1
edited 14 mins ago
Muhammad Hasham
1,9391424
1,9391424
asked May 31 '18 at 13:45
Nadroj467Nadroj467
61
61
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46
add a comment |
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46
add a comment |
1 Answer
1
active
oldest
votes
I've seen this before.
This was caused in my case by configurable (it can happen from other composite products maybe) that had a price set.
In magento 2, configurable products should not have price related data. No price, no special price. They are all calculated from the prices of the simeple products.
In Magento 1, each product had a price and the configuration prices were relative to the price of the configurable product.
Because of this price for configurable products, the product price index calculates negative prices and they end up displayed in the frontend.
You can easily check in the db if there are configurable products with specified prices or special prices.
select attribute_id from eav_attribute where attribute_code in ('price', 'special_price');
//this should return 2 ids (let's say they are 75 and 76)
SELECT * FROM catalog_product_entity_decimal d
LEFT JOIN catalog_product_entity e ON d.entity_id = e.entity_id
WHERE d.attribute_id in (75, 76) AND
d.value IS NOT NULL AND
e.type_id = 'configurable';
Remove all the entries that you get, but please back up your database first.
After you are done, rerun the price index.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f228225%2fnegative-price-filter-in-layered-nav-magento-2-2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've seen this before.
This was caused in my case by configurable (it can happen from other composite products maybe) that had a price set.
In magento 2, configurable products should not have price related data. No price, no special price. They are all calculated from the prices of the simeple products.
In Magento 1, each product had a price and the configuration prices were relative to the price of the configurable product.
Because of this price for configurable products, the product price index calculates negative prices and they end up displayed in the frontend.
You can easily check in the db if there are configurable products with specified prices or special prices.
select attribute_id from eav_attribute where attribute_code in ('price', 'special_price');
//this should return 2 ids (let's say they are 75 and 76)
SELECT * FROM catalog_product_entity_decimal d
LEFT JOIN catalog_product_entity e ON d.entity_id = e.entity_id
WHERE d.attribute_id in (75, 76) AND
d.value IS NOT NULL AND
e.type_id = 'configurable';
Remove all the entries that you get, but please back up your database first.
After you are done, rerun the price index.
add a comment |
I've seen this before.
This was caused in my case by configurable (it can happen from other composite products maybe) that had a price set.
In magento 2, configurable products should not have price related data. No price, no special price. They are all calculated from the prices of the simeple products.
In Magento 1, each product had a price and the configuration prices were relative to the price of the configurable product.
Because of this price for configurable products, the product price index calculates negative prices and they end up displayed in the frontend.
You can easily check in the db if there are configurable products with specified prices or special prices.
select attribute_id from eav_attribute where attribute_code in ('price', 'special_price');
//this should return 2 ids (let's say they are 75 and 76)
SELECT * FROM catalog_product_entity_decimal d
LEFT JOIN catalog_product_entity e ON d.entity_id = e.entity_id
WHERE d.attribute_id in (75, 76) AND
d.value IS NOT NULL AND
e.type_id = 'configurable';
Remove all the entries that you get, but please back up your database first.
After you are done, rerun the price index.
add a comment |
I've seen this before.
This was caused in my case by configurable (it can happen from other composite products maybe) that had a price set.
In magento 2, configurable products should not have price related data. No price, no special price. They are all calculated from the prices of the simeple products.
In Magento 1, each product had a price and the configuration prices were relative to the price of the configurable product.
Because of this price for configurable products, the product price index calculates negative prices and they end up displayed in the frontend.
You can easily check in the db if there are configurable products with specified prices or special prices.
select attribute_id from eav_attribute where attribute_code in ('price', 'special_price');
//this should return 2 ids (let's say they are 75 and 76)
SELECT * FROM catalog_product_entity_decimal d
LEFT JOIN catalog_product_entity e ON d.entity_id = e.entity_id
WHERE d.attribute_id in (75, 76) AND
d.value IS NOT NULL AND
e.type_id = 'configurable';
Remove all the entries that you get, but please back up your database first.
After you are done, rerun the price index.
I've seen this before.
This was caused in my case by configurable (it can happen from other composite products maybe) that had a price set.
In magento 2, configurable products should not have price related data. No price, no special price. They are all calculated from the prices of the simeple products.
In Magento 1, each product had a price and the configuration prices were relative to the price of the configurable product.
Because of this price for configurable products, the product price index calculates negative prices and they end up displayed in the frontend.
You can easily check in the db if there are configurable products with specified prices or special prices.
select attribute_id from eav_attribute where attribute_code in ('price', 'special_price');
//this should return 2 ids (let's say they are 75 and 76)
SELECT * FROM catalog_product_entity_decimal d
LEFT JOIN catalog_product_entity e ON d.entity_id = e.entity_id
WHERE d.attribute_id in (75, 76) AND
d.value IS NOT NULL AND
e.type_id = 'configurable';
Remove all the entries that you get, but please back up your database first.
After you are done, rerun the price index.
answered 2 mins ago
Marius♦Marius
166k28317677
166k28317677
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f228225%2fnegative-price-filter-in-layered-nav-magento-2-2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Migrated from Magento 1.9 using data migration tool
– Nadroj467
May 31 '18 at 13:46