3.0.14 cart variant by custom field bug? (it's not a bug)

[MarioP]

HI,
I see a problem with cart select variant by custom fields. More specifically it concerns the products whose prices have been overridden. So when we select one of the custom field variants which affects on the final price of the product - indeed it does what it should but not in the case when we have an overridden price. I mean the +/- variant affects on the wrong price. It changes the 'standard' final price instead of the overridden one - which is the final one in that case. So it should change that one. Isn't it?

Any help, please?

Generally it leads to very confusing situations like those from the attachment . Even though we have applied the" - " variant, the sales price didn't change.

[jenkinhill]

AS decsribed several times here, a price override is exactly that. It overrides all other prices, including customs, for that product.

[Jörgen]

Hello

Instead of having an overridden price, You should create an unpublished category let´s say "Discount 25%" and an calculation rule for the same in our case Discount 25%.
Apply this category to the product and You get an discount. Can not be applied to child products only to parent products.

http://docs.virtuemart.net/manual/products-menu/taxes-and-calculation-rules.html

regards

Jörgen @ Kreativ Fotografi

[MarioP]

AS decsribed several times here, a price override is exactly that. It overrides all other prices, including customs, for that product.

hmmm... I think we talk about different things.... Price override itself is not a problem.. It works well. The problem is that the -/+ custom field cart variant doesn't affect on this overridden price. Please look at the image. As you can see we have the 'base price' which has been overridden (of course it's the 'sales price'). Now look what happens when we use the custom field cart variant. It decreases the 'base price' instead of the 'sales price'. It should be the opposite, isn't it? The price at which we sell a product is a 'sale price' so the 'cart input' should affect on this one, not on the 'base price'. That's the problem and bug in my humble opinion...

Simple example:
We have a mp3 player in two variants: 2GB (external memory included) and 4GB. We have a temporary promotion on the standard (2GB) variant so we use a 'price override' option.
4GB is a custom field cart variant (+10E)

And now we have:

Base price: 100E
Sales price (overridden price): 80E

We choose 4GB (+10E) variant and we see as follow:

Base price: 110E
Sales price: 80E - here is the problem: the sales price didn't change, yet it should.

Shouldn't be that the variant modifies both the 'base price' and the 'sale price' ?:

Base price: 110E
Sales price: 90E

[MarioP]

Hello
Instead of having an overridden price, You should create an unpublished category let´s say "Discount 25%" and an calculation rule for the same in our case Discount 25%.

Hello
Calculation rule for a single product in which we have a temporary change of the price? Hmm. So what for is the 'override price' option?...  Maybe I was misunderstood  - override price is not a problem.

The problem is that the -/+ custom field cart variant doesn't affect on this overridden price. Please look at the image. As you can see we have the 'base price' which has been overridden (of course it's the 'sales price'). Now look what happens when we use the custom field cart variant. It decreases the 'base price' instead of the 'sales price'. The price at which we sell a product is a 'sale price' so the 'cart input' should affect on this one, not on the 'base price'. That's the problem and bug in my humble opinion...

[MarioP]

Ok, maybe the first sketch could be misunderstood so I've placed the other one which should clearly explain what's the problem.

[Jörgen]

Hello

We understand exactly what You mean, but You don´t understand us.

As jenkin clearly pointed out, price override is price override, thats it. No other customfield is going to change this price. This was a temporary solution to transfer old discount prices from VM 1.1. It works this way, thats it. Use other ways of changing Your prices,  making a discount or similar pricechange is to me made with calculation rules. This is not a bug.

regards

Jörgen @ Kreativ Fotografi

[MarioP]

Thank you Jörgen for a clarification. Anyway, it's, at least, confusing for me...  Ok. if it has to be like that and you say it's a normal thing... Ok I get it.  Thank you once again and sorry for bothering you this (as it turned out ) silly matter.

By the way - I get it - I can create some discount calculation rules in order to change temporarily the current price. But since the price override it's not an option in that case - how can I show the difference between the previous and the discounted price - with the 'override option' we have the old price crossed out. How to show, at first sight, that the price has been decreased and how much?

[Jörgen]

Hello

In my case there is no difference, make a rule and check it out. It displays with crossed out price. You should find some examples on how to discover discount in the standard template.

best regards

Jörgen @ Kreativ Fotografi