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

Catalog price rule applied configurable products not show oldPrice in product list and Product Detail page #9322

Closed
onepack opened this issue Apr 19, 2017 · 10 comments
Labels
Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue

Comments

@onepack
Copy link

onepack commented Apr 19, 2017

I have the exact same issue as closed issue #7624 on a project that has migrated data from a magento 1 store.

Catalog price rules or special prices applied to simple products related to the main configurable products do not show the oldPrice in product list and Product Detail page.

The products are always assigned later to the configurable products and not on the go while creating the configurable product.
When I apply a special price on a simple product or apply a catalog price rule the old price just never shows in the configurable product just the new discounted price of the related simple products.

This way it is not clear for a customer that this is a special/ discounted price.
This happens in the grids and on a product detail page.
Only when I click a color option in the detail page the display of the price box gets updated with the text "regular: xx,xx" under the new "special price".

Magento version 2.1.6
PHP 7

The magento 2 shop is filled with migrated data from a magento 1 webshop.
The bug happens on old CFG's migrated from magento1 and new CFG's created in magento2.

The bug has been reported before in detail here: #7624

@onepack
Copy link
Author

onepack commented Apr 20, 2017

I checked the file: vendor\magento\module-configurable-product\view\base\templates\product\price\final_price.phtml
There it was:

This styling makes the old price block invisible/ not even rendered on the frontend.
I removed the styling in my theme copy of this template file and after that the old price shows in the grids.

I need to check further how to fix the display. But at least it is clear now what happens.

Ps. I removed all the discounts from the simples that belong to one mother CFG and now it just keeps on showing "as low as" with an old "special" price that is no longer valid. Reindexing and clearing the cache doesn't seem to help.

@joebordo
Copy link

Hi, when i remove the styling it does show up, in the product page (detail page), but in the category page it still does not show up. Is it the same with you?

I can't believe it's june and it's not fixed yet.

@joebordo
Copy link

joebordo commented May 28, 2017

Hi, Line 22 in the the file: vendor\magento\module-configurable-product\view\base\templates\product\price\final_price.phtml

I replaced This: <?php if (!$block->isProductList() && $block->hasSpecialPrice()): ?>
With this: <?php if ($block->hasSpecialPrice()): ?>

Now the old price shows up for me. (on the category page)
And for the styling (i just left class old-price" and now it shows up in the product page, (thanks to you).

hope it helps.

@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Sep 11, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Oct 24, 2017
@magento-engcom-team
Copy link
Contributor

@onepack, thank you for your report.
We've created internal ticket(s) MAGETWO-82627 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 24, 2017
@programmer2-techybirds
Copy link

programmer2-techybirds commented Nov 11, 2017

How to show exclusive price instead of inclusive price in configurable product with tier price.
See below example for more clarification.

Here exclusive price is: 5.04
inclusive price is: 6.10

Now when select any single product from dropdown then calculation is upon inclusive price.
Need instead of that exclusive price instead of inclusive price.

Anyone have solution on this?

This is related to here: #5097

@kfaer
Copy link

kfaer commented Mar 22, 2018

is this issue resolved?

@Brendonwbrown
Copy link

Used @joebordo 's solution - solved for me.

@darren-halo
Copy link

darren-halo commented Sep 18, 2018

@joebordo's solution worked for me in 2.2.5.

Although the change is on line 37 now.
Remove the classes 'sly-old-price no-display' because these forces the old price to be hidden.
Override in file: THEME/Magento_ConfigurableProduct/templates/product/price/final_price.phtml

@m2-assistant
Copy link

m2-assistant bot commented Dec 17, 2019

Hi @krzksz. 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.

  • 2. 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!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


@ghost ghost unassigned krzksz Oct 8, 2020
@ghost ghost removed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Oct 20, 2020
@magento-engcom-team magento-engcom-team added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Nov 30, 2020
@stale
Copy link

stale bot commented Feb 14, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Feb 14, 2021
@stale stale bot closed this as completed Mar 1, 2021
magento-devops-reposync-svc pushed a commit that referenced this issue Oct 29, 2024
…-beta2-28Oct24

[Hammer][2.4.8-beta2] Platform Health Scope
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue
Projects
Development

No branches or pull requests

10 participants