Price by attrib pulling unknown price

http://www.raretvclassics.com/index.php?main_page=product_info&cPath=10&products_id=111

Note the cheapest case is 1.60, but it says starting at $3.00. The main product is set to 0.00. Where is it getting 3.00 from?

Just taking a wild guess here... but is that Starting at $3.00 hand typed in??? as a part of your script... when i goto check out the price is right.....

!--bof Product Price block -->

look for that in your developers tool kit.... it may help you solve this.......

g0d4lm1ty:

Just taking a wild guess here... but is that Starting at $3.00 hand typed in??? as a part of your script... when i goto check out the price is right.....

!--bof Product Price block -->

<h2 id="productPrices" class="productGeneral"> Starting at: $3.00</h2> <!--eof Product Price block -->

look for that in your developers tool kit.... it may help you solve this.......

ya i know the price is right at checkout..and no its not typed.. it even shows 3.00 in the admin area when i preview changes, but when i see the full edit area it shows 0.00

can you cut and paste your admin screen.. just the pricing info.....

Your cheapest case is the 2-disc case at $1.00, but you also have the attribute Case Art Upgrade (Title of show) with a price of +$2.00. This is apparently added in by the "starting at" logic, giving $1.00 + $2.00 = $3.00 minimum price.

It does work correctly in the shopping cart, adding the charge only when the field is not blank.

gjh42:

Your cheapest case is the 2-disc case at $1.00, but you also have the attribute Case Art Upgrade (Title of show) with a price of +$2.00. This is apparently added in by the "starting at" logic, giving $1.00 + $2.00 = $3.00 minimum price.

It does work correctly in the shopping cart, adding the charge only when the field is not blank.

aha! good catch! that makes sense. I guess its the logistics of "groups" of attribs. Thanks !

If this is actually what's happening, it is a flaw in the code and ought to be reported in the Bug Reports section. I don't expect it would take Ajeh long to fix it, or give a workaround if there is one.

It is not a flaw in the code ...

It is a flaw in the user's set up of the Product ... :eek:

Sounds like you have said Priced by Attribute and the Product is not ...

Ajeh:

It is not a flaw in the code ...

It is a flaw in the user's set up of the Product ... :eek:

Sounds like you have said Priced by Attribute and the Product is not ...

It's not?

I have a general description and 5 options that decide price. Another secondary option is the text part. Technically the product is set up correctly, but like I said I think its just not the way it was designed to work. I dont think its an easy fix nor do I think it is a bug.. its just a design issue. There is no such thing as a "secondary option" so it is trying to price by attribs from 2 different attrib sets, so the fact that it adds them together rather than just take note of the first attrib is a rather pleasant surprise.

But no biggie, I just wanted to figure it out.

Price by Attribute takes the lowest price of each Option Name group to build the Product Price ...

If you have an optional $2.00 charge ... plus the other group has the lowest price of the $1.00 that is $3.00 ...

If you have a Product Option where there is only 1 price and it is optional and your Product does not have a Product Price, then you can use the Priced by Attribute but you need to turn off the single Option Name Price from being included in the displayed Product Price or base price of the Product ...

Otherwise, the price will display as $3.00 when you really mean $1.00 with other choices to increase the price ...

As you are showing the prices as:
+2.00
+1.00
etc.

You could also make the Product not Priced by Attribute and set to the Products Price to $1.00 ...

Then set the attribute that costs $1.00 to 0.00 and the one that costs +2.00 to +1.00 ...

ajeh is right dude... listen to the masta..... she is "spot on"

even tho it is an optional charge it is there until the customer decides they don't want it...
so like linda said $3. untill they say no.....

i think the easier way is like linda said.. set the price to a buck.... quick corrections and less headache.....

You could take a look at this link http://www.london-directory.biz/store/index.php?main_page=product_info&cPath=452_477_482&products_id=2209 here I have a single product listing with about 864 Product and 32 price permutations. I have used the atribute system to cover all of the permutations including another dropdown for shipping to various parts of the uk.

I have had to do a trade off by leaving the price factor at zero which results in the message 'Starting at:' appearing. But I dont mind this for the time being. If anyone knows how to get rid of this on individual products please let me know.

The reason for the dropdown for shipping cost is because I use the table rate for another very large section of the site and didnt want to confuse customers with multiple shipping tables. Also, each design company has their own rates and this would mean a load of shipping tables at the checkout.
Anyway, take a look, maybe you could use it or improve on it.
Kind regards
Stephan Toth https://www.london-directory.biz

Oh, I nearly forgot.
If your going to do a product as large and complicated as this is then I would recomend that you create a product called xyz product template, configure all of your atributes in that one without the price data. Copy it as many times as necessary to cover your expected product range. Then open them one by one and cange the xyz product template to the product name and fill in the details. For the table, create the table in note pad and save it as product name template, then just cut and paste it into the product catagory. If the products have diferent data such as sizes and prices then leave these blank in the template otherwise you will have to overtype them time and time again and that gets confusing.
I hope this helps some of you.
Kind regards
Stephan Toth https://www.london-directory.biz

Ajeh:

Price by Attribute takes the lowest price of each Option Name group to build the Product Price ...

If you have an optional $2.00 charge ... plus the other group has the lowest price of the $1.00 that is $3.00 ...

If you have a Product Option where there is only 1 price and it is optional and your Product does not have a Product Price, then you can use the Priced by Attribute but you need to turn off the single Option Name Price from being included in the displayed Product Price or base price of the Product ...

Otherwise, the price will display as $3.00 when you really mean $1.00 with other choices to increase the price ...

As you are showing the prices as:
+2.00
+1.00
etc.

You could also make the Product not Priced by Attribute and set to the Products Price to $1.00 ...

Then set the attribute that costs $1.00 to 0.00 and the one that costs +2.00 to +1.00 ...

Well lets stop for a sec. Currently I am able to add this product to the cart without checking any of the options. How would I make it give an error if nothing was checked? Does this have to do with the way I am using the options?

I figured out how to fix my problem as well.. By putting an X in the base price option of the textbox option, I essentially turned it into a secondary, non-included price. Which kinda reiterates what I was saying before, that it adds all the option groups together, which I guess would make sense if u were building a PC, you'd have at least one mandatory level of CPU, one mandatory level of RAM, etc. But still, the options are not mandatory for me, as I can still add to cart without checking the boxes.

You have setup your attributes as checkboxes ...

Checkboxes are used when the customer is suppose to be able to choose 0 to many selections from the choices ...

Is this what you intend the customer to do?

Radiobuttons and Dropdowns can be setup so that there is a Display Only selection that is not allowed to be added to the shopping cart so that the customer has to make a valid choice ...

How are you intending these choices to work?

Ajeh:

You have setup your attributes as checkboxes ...

Checkboxes are used when the customer is suppose to be able to choose 0 to many selections from the choices ...

Is this what you intend the customer to do?

Radiobuttons and Dropdowns can be setup so that there is a Display Only selection that is not allowed to be added to the shopping cart so that the customer has to make a valid choice ...

How are you intending these choices to work?

That's what I figured.
I was intending for people to be able to select one or more checkboxes, but forced to check at least one checkbox.

There is not a forced selection available on the checkboxes at this time ...

It is something to be added in a future release ...

The problem with your current method is I want 3 of 2-Disc and 6 of 12-Disc but there is not an intuitive way for me, the customer, to figure out how to do that ...

With the Radiobuttons, the customer can select one choice and how many they want then select another choice and how many they want ... and in both cases the "force a valid selection" can be used ...

Ajeh:

There is not a forced selection available on the checkboxes at this time ...

It is something to be added in a future release ...

The problem with your current method is I want 3 of 2-Disc and 6 of 12-Disc but there is not an intuitive way for me, the customer, to figure out how to do that ...

With the Radiobuttons, the customer can select one choice and how many they want then select another choice and how many they want ... and in both cases the "force a valid selection" can be used ...

Ya i know currently its a bit overcomplexed by my attempts to simplify, I actually had radio buttons set at one time but the checkbox method came to me in a dream :P

Or ... a nightmare ... :eek:

It really is up to you and how bright your customer's are in placing orders ...

I think the checkboxes may be more troublesome than helpful on this product ...

Ajeh:

Or ... a nightmare ... :eek:

It really is up to you and how bright your customer's are in placing orders ...

I think the checkboxes may be more troublesome than helpful on this product ...

And "bright customers" is more or less an oxymoron :P I've changed back to radio boxes