Order Page Product Advanced Settings??? What do I put in these fields? Anything?

[tallship]

I'm trying to create an order page and I can't
figure out what to put into the "Product/Advanced Settings" area.

I don't know if I can just leave them blank, if there are correct values
to place in there that I must use, or if I can put anything in there
that I want.

Here's an example of what I'm talking about (I borrowed a control panel config page since I had no examples for CPUs):



Here's the only reference I can find at wiki.hostbillapp.com:

http://wiki.hostbillapp.com/index.php?title=Configuring_products#Components

and...

http://wiki.hostbillapp.com/index.php?title=File:Product_Config_Components-crop.png

The only thing I can find from the link on that page is related to
sliders for OnApp. I'm doing drop down boxes and it's not OnApp.

[Lawrence]

1. The CSS class determines what icon appears next to the product component on the order form. Try "ram" or "cpu" for example. (Or cf_ram or cf_cpu, I forget)

2. The group was originally intended for dedicated servers, it's very sloppy. It will only work on the old dedicated server order page as far as I know.

3. The variable is a value that's passed into emails and modules, sends parameters / values to where they need to go.

Hope that helps!

[thetrusteeco]

Not sure if this is useful info for you, but the variable name field is used by the domain registration modules to send variables to the registrars' API.

If you needed an addon for a TLD you could add it with a form, and whatever you enter in the variable name field will be sent to the API with the (value) option the customer picks.  Usage would depend on the API being interacted with.

Examples:
variable-name=1
variable-name=yes
variable-name=true

I leave the CSS and Group fields empty.  I experimented with the CSS when I got HostBill but not since.  Never knew what the Groups were for.

[tallship]

Okay good to know guys! Thanks

I was looking for a while and was real hesitant to enter anything for fear of using some reserved global variable and borking things. Eventually, for the CPUs I just used cf_cpu and cpu, following what I deduced was the naming convention for other classes and variables, and it worked out fine.