thinguy

I've got a fairly new install with Infobox_skin, Master Products, attribute-setsv3, Local Delivery. Somewhere along the way I'm now getting the following error when I edit a product. Any hints or ideas on what's causing it would be great. 1054 - Unknown column 'products_attributes_sets_name' in 'field list' select products_attributes_sets_id, products_attributes_sets_name from products_attributes_sets order by products_attributes_sets_name [TEP STOP]

Sorry I'm talking about the graphics. What says $cataloglogo=oscommerce.gif for example. Thanks

Ok here's a quick question that's got to be simple but it's driving me crazy. Where are the tags defined? What file says $myaccountlogo=header_account for example. Thanks.

I was wondering if anyone had taken the time to roll up the popular contribs into a fresh install?

I'm trying to install QTPro 3.0 and I get the following error. "Table 'orders_products_attributes' already exists" I've seen other threads mentioning it but no solutions. Anyone have any tips?

Jassa if I understand you're earlier post you were getting the "Table 'orders_products_attributes' already exists" error message with 3.0 also. Can you describe how you fixed it please? Thanks

I'm setting up a site to sell shirts and hats and a few other things. Say the customer picks I want only the options that are possible be pickable by the customer. I don't want them picking a yellow hooded shirt if it's not available in xxlarge for example. SOmething like this. T-Shirt Type Plain Short Sleeve Pocket Long Sleeve Hooded Color[Type Sensitive] Red Yellow [Pocket Not available] Blue Black White Green Light-Blue Size [Type and Color Sensitive] Small Medium Large X-Large [Not available in Light-Blue Hooded] XX-Large [Not available in Green] I'd like the unavailable attributes to gray out or disappear if they've picked another attribute that makes it impossible. Is there anything that does this? If not how are people setting something like this up? Thanks

If you don't want the blanks to show up, then fill in a value for each language (that's where the blanks come from). You could also modify the SQL query to add in the WHERE clause a <> '' piece which will then not show the blanks. Man I should have noticed that. What a newbie mistake. Thanks for the quick help. And thanks Joey for making a slick contrib with great install directions.

I've got a fresh install of OSC and I've inserted Attribute Sets thanks to the great documentation. I have no attributes created. I create one "Color" then go to Attribute Sets hit Insert and I have 2 blank choices in the drop down and than 'Color' If when I add values (Red, blue, etc) I get even more blank choices. Any idea how to correct?