This mod workes great. one problem with product on spesial.
If a product is on special and there is options, this mod use the product price+ options and not the special price + options
How can I Fix this.
Any help? Thanx
I have the following problem:
e.g.
So if someone buys pack and lets say something costs 100 € with 15% save pay only 85€ if they add options: pack two + 50€, pay only 127,5€ the display is 135€ see only 15% to 100€ more 50€, must show 15% of € 150 = 127€.
Can you do something?
e.g.
So if someone buys pack and lets say something costs 100 € with 15% save pay only 85€ if they add options: pack two + 50€, pay only 127,5€ the display is 135€ see only 15% to 100€ more 50€, must show 15% of € 150 = 127€.
Can you do something?
Is there a way to make it hide the price if the option does not add or subtract anything?
Say im selling medals, and want people to choose a ribbon color at no extra charge,
can I make it so it wont show the prices next to the colors?
Because it might confuse customers into thinking the ribbon costs extra.
if ($option_price == 0) { hide option_price }
Kinda like that, roughly.
Say im selling medals, and want people to choose a ribbon color at no extra charge,
can I make it so it wont show the prices next to the colors?
Because it might confuse customers into thinking the ribbon costs extra.
if ($option_price == 0) { hide option_price }
Kinda like that, roughly.
So as it is now..
Tshirt: $100.00
- Color Red: $100.00 <-- implying a $0 increase
- Color Blue: $110.00 <-- Implying a $10 increase
- Color Green: $115.00 <-- implying a $15 increase
You want to change it to:
Tshirt: $100.00
- Color Red: ____ <-- implying a $0 increase
- Color Blue: $110.00 <-- Implying a $10 increase
- Color Green: $115.00 <-- implying a $15 increase
Because showing $100.00 by the red would make people thing it costs $200 ?
But you don't seem phased that people might think the Blue costs $210 or the green costs $215?
The way it is now means the same logic applies to all prices.
Tshirt: $100.00
- Color Red: $100.00 <-- implying a $0 increase
- Color Blue: $110.00 <-- Implying a $10 increase
- Color Green: $115.00 <-- implying a $15 increase
You want to change it to:
Tshirt: $100.00
- Color Red: ____ <-- implying a $0 increase
- Color Blue: $110.00 <-- Implying a $10 increase
- Color Green: $115.00 <-- implying a $15 increase
Because showing $100.00 by the red would make people thing it costs $200 ?
But you don't seem phased that people might think the Blue costs $210 or the green costs $215?
The way it is now means the same logic applies to all prices.
The problem is that there are options that do not affect prices.
I do agree that not pricetagging just one item in an option list looks odd and confusing,
but on options that have no items that affect price it would look nicer if they didn't have a pricetag.
Say I have a trophy that's available in different sizes and the price differs accordingly.
But those trophies also have an option to be gold, silver or bronze, without affecting the price.
It would look nicer if that color option had no mentioning of price since it doesn't affect it.
So for short:
if(optionprice array != 0) { do what your mod does }
Would make things look nicer in my opinion.
I do agree that not pricetagging just one item in an option list looks odd and confusing,
but on options that have no items that affect price it would look nicer if they didn't have a pricetag.
Say I have a trophy that's available in different sizes and the price differs accordingly.
But those trophies also have an option to be gold, silver or bronze, without affecting the price.
It would look nicer if that color option had no mentioning of price since it doesn't affect it.
So for short:
if(optionprice array != 0) { do what your mod does }
Would make things look nicer in my opinion.
Hello SokonomiSokonomi wrote: Say I have a trophy that's available in different sizes and the price differs accordingly.
But those trophies also have an option to be gold, silver or bronze, without affecting the price.
It would look nicer if that color option had no mentioning of price since it doesn't affect it.
I wanted a similar functionality and so added the following hack to Qphoria's mod. I can't guarantee it'll work for everyone, although it is quite simple and works on my install.
I found
Code: Select all
<![CDATA[Code: Select all
if ($option_value['price'] !='0.0000') { Code: Select all
]]>Code: Select all
} else {}Dan
Last edited by Cosmological on Fri Mar 08, 2013 9:01 pm, edited 1 time in total.
Oh right, sorry to hear it didn't help your situation. The alterations work fine on my site (1.5.4.1) and do exactly what I need; use this mod to display actual prices on the selections rather than +/-, whilst not displaying any price at all on options that cost nothing extra.Sokonomi wrote:That doesn't work because option value price is not a float but a string.
So it involved a heap of string replace and substring select code to deal with it.
It sounds then as if your setup is different to mine if my modification doesn't work for you. Too bad, I was pleased with my hack (I'm primarily a designer and very amateur when it comes to coding) and was hoping it would help you or others too. Maybe Qphoria will come up with a better solution at some point.
Dan
The problem is the comma, Im guessing your shop uses american annotations, thus a dot for decimals. That gets accepted as a float, as where my comma decimal throws a spanner in the works. I had to jump through hoops by converting both $price and $option_value['price'] to floats and then applying math and then reformatting it again. Plus I had to do a dirty hack by turning a products MPN into a toggle switch so it will reformat all or none of the options. Because as Qphoria said, only doing it partially will look weird. But it got done in the end so im pleased with it. :p
Ah right, yeah I'm keeping it simple and sticking to the point... pardon the pun haha. If I wanted to change presentation to use the comma, I'd probably have gone for the easy option and written a bit of jquery using regex to match and switch the points to commas after the fact. Sounds like your solution might be more robust - glad it works for you anyway, that's the main thing!Sokonomi wrote:The problem is the comma, Im guessing your shop uses american annotations,
Dan
There is a little wrong in Cosmological's solution.
You must add
not
and it works
You must add
Code: Select all
} else {}Code: Select all
else {}I am also in a bit of of a fix, my company sells coffee and the prices will show correct for each bag size option, but i don't wan the grind option to show a price. Is there a way to just have this mod apply to certain options.
Using this mod, together with my modification should work for you (at least it does on my install), so long as you set your "Grind" option price to be +/- 0.00.FreshRoastedCoffee wrote:I am also in a bit of of a fix, my company sells coffee and the prices will show correct for each bag size option, but i don't wan the grind option to show a price. Is there a way to just have this mod apply to certain options.
Cheers
Dan
Where did you add it? There are multiple spots and haven't been able to get to work.Cosmological wrote:Hello SokonomiSokonomi wrote: Say I have a trophy that's available in different sizes and the price differs accordingly.
But those trophies also have an option to be gold, silver or bronze, without affecting the price.
It would look nicer if that color option had no mentioning of price since it doesn't affect it.
I wanted a similar functionality and so added the following hack to Qphoria's mod. I can't guarantee it'll work for everyone, although it is quite simple and works on my install.
I foundand added the following immediately after:Code: Select all
<![CDATA[Then, at the end, immediately precedingCode: Select all
if ($option_value['price'] !='0.0000') {added:Code: Select all
]]>Hope this helps, best of luck and thanks Qphoria for making the mod available.Code: Select all
else {}
Dan
You add it in the xml file, here: /vqmod/xml/show_full_option_price.xmlwildrizzo88 wrote:Where did you add it? There are multiple spots and haven't been able to get to work.
On my installation of 1.5.5.1, yes, it works fine.Xciso wrote:Is this working with 1.5.5.x?
Dan
Who is online
Users browsing this forum: No registered users and 28 guests
