web28:
at WriteAtHome
You have two things to change:
1: Attribute 6'' set the price to +0.0001 or use a dropdown
2: for="attrib-29-109">Same as Color 1<br> (+$0.00) - the problem is the <br> tag. Dynamic Price Updater can't read the price (+$0.00)
The code for Radiobuttons and Checkboxes read out the html-text until the next html-tag (nextSibling):
prArr[objInp.name]['n'] = objInp.nextSibling.innerHTML.replace(seeker, '');
web28
Hi Web28, lankeeyankee, and everyone using the Dynamic Price Updater,
After many wonderful suggestions by WEb 28 and lankeeyankee I've perfected the price updater on my test website. You can view it here: http://welcomingwalls.com/index.php?main_page=product_info&cPath=65&products_id=181
It's not exactly what I wanted the page to look, but having the updater work properly far outweighs the small details I had to forego. To help anyone else out there trying to make the updater work on their site, I'm going to give a rundown of everything I had to tweak to make it work for me. Maybe some of these suggestions will work for you as well.
-
I had too many custom tweaks to begin with that interfered with the updater, so my first suggestion would be to start with fresh and "untampered with" product_info pages. Once you get the updater working properly then you can make custom changes and test to make sure it doesn't mess with the updater. Web28 mentioned that you have to keep the "Starting at:" text or at least the ":" to make this work. This was one of the tweaks I had made that messed with the updater working for me.
-
My website uses radio buttons rather than dropdown menus because I needed to add images to my options. BUT, only some of the radio "Attribute Style for Radio Buttons/Checkbox" work:
Image Styles:
0= Images Below Option Names
1= Element, Image and Option Value
2= Element, Image and Option Name Below
3= Option Name Below Element and Image
4= Element Below Image and Option Name
5= Element Above Image and Option Name
Test them out for yourself, but for me the only one that worked was #3. I think this had something to do with Web28's suggestion in Post #272 about the (+3.00) being on a certain line.
-
My actual product I set a price of $0.00 because the pricing was based on the size chosen in the first attribute. The first attribute flags were all set to "no", except the discounted setting which is could be either way, and the first attribute is set as the default. As lankeeyankee stated in Post #264, the first attribute doesn't need the "+" in the pricing to work. Because I am using it as my base pricing I left the "+" out and it works fine.
-
The second attribute is color #1. I don't charge anything for the first color because it's part of the original price. So, I was able to take out the "+" and the pricing all together. Each of these attributes work independently from one another, so it didn't have any negative effect on the other attributes to leave the pricing out. All the attribute flags were set to "no", except discount and base price. These could go either way because their is no pricing involved.
-
For the third attribute, Color 2, this was the kicker. My first option value is "Same as Color 1", which means their is not an additional price because they didn't want a second color. The other option values added $3.00 for the second color of their choice. The options that added $3.00 worked fine, but if I then again chose "Same as Color 1" it wouldn't subtract the $3.00 back off. The only thing different between it and the other options was the price difference and the fact it didn't have an image. So, I added an image . . . and it worked perfectly. I don't know why it also has to have an image for the updater to work, but I suspect it has to do with Web28's suggestion in Post #272. For this attribute, the flags were all set to "no", except the discounted could go either way and the "Same as Color 1" is set as the default.
Anyway, I'd like to thank everyone who posted here, because I read all 27 pages trying to find the answers to my problems. I hope that maybe the settings I've posted here might help someone else who is having trouble.
Kim :smile: