Jump to content
thirty bees forum
  • 0

Problem with price on product page after upgrade to 1.0,4


elund

Question

After upgrading to version 1.0.4 I have problems with the price shown on the product page when using quantity discount as shown below.

0_1531076255856_e9be7d49-fec2-4887-a253-c453b00407bf-image.png

Is this a bug in vesrion 1.0.4 or a compatibilty problem with my theme and version 1.0.4? It worked fine with version 1.0.3.

Link to comment
Share on other sites

12 answers to this question

Recommended Posts

  • 0

Hmm. @yaniv14 can't reproduce this on 1.0.6, see comment on the Github issue.

Which leads to the question: what is different between your installation and Yanivs? Any additional modules? A custom theme? Does it happen with new products as well (it might be result of something stored in the wrong place in the database)?

Link to comment
Share on other sites

  • 0

What I did is to install a fresh new 1.0.6 with Hebrew language and all demo products. After that I've edited one of the products and added 2 different quantity discounts. Both shows fine in the quantity discount table and both changed the product price once reached the desire amount.

Link to comment
Share on other sites

  • 0

@traumflug said in Problem with price on product page after upgrade to 1.0,4:

Hmm. @yaniv14 can't reproduce this on 1.0.6, see comment on the Github issue.

Which leads to the question: what is different between your installation and Yanivs? Any additional modules? A custom theme? Does it happen with new products as well (it might be result of something stored in the wrong place in the database)?

I use the TB compatible Panda theme from https://www.sunnytoo.com/product/panda-creative-responsive-prestashop-theme.

If the line below is the only change to the community theme, then it unfortunately doesn't help me, so I have to investigate further.

~~if (discountedPrice != 0) {~~ if (displayDiscountPrice != 0 && discountedPrice != 0) {

SInce it worked before I would assume there must have been a correction to the core code causing this issue. The correction to the core can of course be the right thing to do.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...