If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

/*For some unknown freak reason that I can't get Attributes 25, 26, 27, 28 and 29 line up all together the next roll,
I created Attribute 30 to do a 'roll break'.*/
#wAttrib-30 {clear: left;}/*this will sit on a new line*/
#wAttrib-30 .attribsOptions {display: none;}/*for a read-only attribute to hide all but comments*/

/*For some unknown freak reason that I can't get Attributes 25, 26, 27, 28 and 29 line up all together the next roll,
I created Attribute 30 to do a 'roll break'.*/
#wAttrib-30 {clear: left;}/*this will sit on a new line*/
#wAttrib-30 .attribsOptions {display: none;}/*for a read-only attribute to hide all but comments*/

Re: Flexible Attributes support

If you read my reply on this post earlier I gave you a pretty good setup to go with for the attributes, including positioning and such, I did the same thing a few days ago.

Now I need to add both RE's QTY and LE's QTY to Shopping Cart's QTY total. Can anyone direct me to a forum discussion that address this issue please?

You need to make all of your products priced by attribute, and build a product template to apply price factoring values for the two qty fields (That's how I did it anyway). In my case I also made the base price a hidden read only attribute.

The next issue after adding all the attributes, is probably server load. I've found that the queries go through the roof. You seem to have a good load speed so far... what host are you on?

Re: Flexible Attributes support

If you read my reply on this post earlier I gave you a pretty good setup to go with for the attributes, including positioning and such, I did the same thing a few days ago.

You need to make all of your products priced by attribute, and build a product template to apply price factoring values for the two qty fields (That's how I did it anyway). In my case I also made the base price a hidden read only attribute.

The next issue after adding all the attributes, is probably server load. I've found that the queries go through the roof. You seem to have a good load speed so far... what host are you on?

anyway, i saw your site. i had tried adding up the price by attributes before. honestly, i have no problem with doing that but there is one problem: the QTY displayed in the shopping cart is always 1 -- no matter how many boxes or quantity we (the customers) declared for our order in the product info page.

Hence, if we (the website designers, ie, you and I) are going to use the option of adding up price by attributes, we have to get rid of the QTY display inside the shopping cart. Off hand, I dunno where or how to do it.

I had learn progamming in my computer games design and development diploma earlier (DarkBASIC) and if I am not wrong, the attributes values are "Text" where as the value for the QTY in the Shopping Cart is "Numbers" -- and they are not linked.

If I know where is the code that adds up the shopping cart quantity total and the code for my customed attributes (QTY) are physically written, I may be able to link them like this (somthing like this):

ShoppingCart_QTY = Attrib_QTY(RE) + Attrib_QTY(LE) /*names for each element in the formula is not the real names declared in the real script*/

Re: Flexible Attributes support

I would advise taking the value "-" out of cyl and axis, so they can be suppressed, and not show up unless they are needed.

My site has horrible load times at the moment but you can see that I've done most of this already over the last few weeks. If I can help, I will. Also, check the thread over here to get more on topic.

Based on my php coding knowledge, which is ZERO, it leaves me to no choice as I have to keep my option names and values to the minimal to avoid future confusion and simplicity for creating future product info pages.

/*For some unknown freak reason that I can't get Attributes 25, 26, 27, 28 and 29 line up all together the next roll,
I created Attribute 30 to do a 'roll break'.*/
#wAttrib-30 {clear: left;}/*this will sit on a new line*/
#wAttrib-30 .attribsOptions {display: none;}/*for a read-only attribute to hide all but comments*/
/*This line aligns all Left Eye attributes in one roll(third roll)*/
#wAttrib-25 {float: left; width: 12em;} /*This line ensures 'Left Eye, LE(OS)' is displayed with enough column width.*/
#wAttrib-26, #wAttrib-27, #wAttrib-28, #wAttrib-29 ,#wAttrib-33, #wAttrib-34 {float: left; width: 7em;}

Now I need to add both RE's QTY and LE's QTY to Shopping Cart's QTY total. Can anyone direct me to a forum discussion that address this issue please?

Thanks.

Oh yar. For people who wonder what is Attribute 30 and 35, they are actually 'Blank Space 002' and 'Blank Space 001' respectively, which I further hide their Option Name discription using the script provided in the module.

I did this after some trial and error with the earlier version of my script and found out how to by pass the bug (if it is, or whatsoever freak reason that what supposed to be joint together in one roll are not).

The 4 lines (2 lines for each blank space) is written base on the rule -- Visual Arts is all about visual illusion.

If we can't get the expected visual result in one solution, use another -- so long it looks what it supposed to looks like!

Re: Flexible Attributes support

It seems you have complicated the layout elements quite a bit to get back to something like the layout you had before, with two rows (not "rolls") of attribute dropdowns... but if it works now, maybe better not to try to fix it more.
Specifically, #wAttrib-20 and #wAttrib-25 no longer have the clear: left; that made them start on new lines, so you introduced new attributes with a bunch of styling to do the job.

There is a PHP operator called (int) that you can put before a variable to cast its type to an integer.
$variable = (int)$variable_old;

This would convert text numerals to a numeric value.
As for where to apply it, I haven't explored that part of the code to be able to advise.