Can't get rid of price when priced by attribute

Ajeh:

What happens if you use:
Product Price 0.00
Price by Attribute: YES

then on the two Attributes set them both to:

This will show in the listings as $749 and in the Product Info as $749, but when the customer selects just the Sofa, they get $404 and if just the Loveseat they get $345 ...

The problem here, however, is if they select nothing then they have no charge ...

A possible solution is to use 2 Option Names such as:
Add Sofa
Add Loveseat

and make those Radiobuttons ...

Then on the Option Values create 3 for each Option Name:
Include this (or some such text)
Display Only YES
Default YES
Yes
No

and put the price on the Attribute for YES ...

What this does is force the customer to make a valid choice of YES or NO on the Sofa and/or Loveseat ...

I will give that a try and let you know. Thanks!

Thanks for access, I've emailed you a report of what I've found with regards to your product listing page.

For the forum folks... There is Java built into the exodus template that’s stripping out and generalizing the prices it ‘sees’ then displays after the page loads. That explains why you can see some of the original Zen code, the Java overwrites it!

This Java is not on the product page, explaining why it works as it should :)

The solution is to get the attributes setup correctly and either dump the Java that's interfering with the product listing page, or rewrite it so it will see the pricing correctly.