1054 - Unknown column 'products_length' in 'field list'

[Guest]

Hello,

 

After installing UPS XML 1.3.9 I'm receiving the following error:

 

<start>

 

1054 - Unknown column 'products_length' in 'field list'

 

select pd.products_name, pd.products_description, pd.products_url, p.products_id, p.products_quantity, p.products_model, p.products_image, p.products_price, p.products_weight, products_length, products_width, products_height, products_ready_to_ship, p.products_date_added, p.products_last_modified, date_format(p.products_date_available, '%Y-%m-%d') as products_date_available, p.products_status, p.products_tax_class_id, p.manufacturers_id from products p, products_description pd where p.products_id = '261' and p.products_id = pd.products_id and pd.language_id = '1'

 

[TEP STOP]

 

<end>

 

I receive this message only when trying to Edit existing products. I can add a new product and the fields show fine.

 

Any help would be greatly appreciated.

 

Thanks,

Chet

[♥mdtaylorlrim]

Did you follow the install directions accurately? There should be a SQL statement or php file to run that alters the database and adds the necessary tables and columns to the database. You may have missed that part of the instructions.

 

Did you make sure that Dimensional Support is turned OFF?

[Guest]

Did you follow the install directions accurately? There should be a SQL statement or php file to run that alters the database and adds the necessary tables and columns to the database. You may have missed that part of the instructions.

 

Hello,

 

I definitely ran the .sql file that came with the contrib as per the instructions (Step 1). Here's the SQL code:

 

<START>

 

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) VALUES ('Dimensions Support', 'SHIPPING_DIMENSIONS_SUPPORT', 'No', 'Do you use the additional dimensions support (read dimensions.txt in the UPSXML package)?', '7', '6', 'tep_cfg_select_option(array(\'No\', \'Ready-to-ship only\', \'With product dimensions\'), ', now());

 

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Unit Weight', 'SHIPPING_UNIT_WEIGHT', 'LBS', 'By what unit are your packages weighed?', '7', '7', 'tep_cfg_select_option(array(\'LBS\', \'KGS\'), ', now());

 

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Unit Length', 'SHIPPING_UNIT_LENGTH', 'IN', 'By what unit are your packages sized?', '7', '8', 'tep_cfg_select_option(array(\'IN\', \'CM\'), ', now());

 

<END>

 

Also, Dimension Support is OFF.

[♥mdtaylorlrim]

That appears to be the procedure that is run when you press the INSTALL button in the module configuration in the admin section of your store, not the install of the contribution. If you ran that multiple times then that may be your problem.

 

However, there should be another sql or php file to run that INSERTS the columns in either products or product_descriptions. That is the contribution install directions.

 

THEN, the sql statement in the above original error all of the dimensional column name should either have a p. in front of them or a pd. in front of them.

[Guest]

That appears to be the procedure that is run when you press the INSTALL button in the module configuration in the admin section of your store, not the install of the contribution. If you ran that multiple times then that may be your problem.

 

However, there should be another sql or php file to run that INSERTS the columns in either products or product_descriptions. That is the contribution install directions.

 

THEN, the sql statement in the above original error all of the dimensional column name should either have a p. in front of them or a pd. in front of them.

 

I followed the directions to the letter. The code above is copied from the file configuration_shipping.sql which the instructions state is step 1 to installing this contribution. Step 2 is adding all the files.

 

Also, I'm not using and did not install dimension support. I'm only using the basic UPS XML.

[♥mdtaylorlrim]

This is found in the Dimensional Installation Instructions

 

ALTER TABLE products
ADD products_length DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_width DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_height DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_ready_to_ship INT(1) DEFAULT '0' NOT NULL;

DROP TABLE IF EXISTS packaging;
CREATE TABLE packaging (
 package_id int NOT NULL auto_increment,
 package_name varchar(64) NOT NULL,
 package_description varchar(255) NOT NULL,
 package_length DECIMAL(6,2) default '5' NOT NULL,
 package_width DECIMAL(6,2) default '5' NOT NULL,
 package_height DECIMAL(6,2) default '5' NOT NULL,
 package_empty_weight DECIMAL(6,2) DEFAULT '0' NOT NULL,
 package_max_weight DECIMAL(6,2) DEFAULT '50' NOT NULL,
 package_cost int(5) NOT NULL,
 PRIMARY KEY (package_id)
);

 

Personally I do not use dimensional support so I wont be much more assistance. But you may have missed this part of the instructions. Otherwise, it is because the p. is missing in front of the column names in the original sql statement with the error. Do you see those columns in your products table?

[Guest]

This is found in the Dimensional Installation Instructions

 

ALTER TABLE products
ADD products_length DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_width DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_height DECIMAL(6,2) DEFAULT '12' NOT NULL,
ADD products_ready_to_ship INT(1) DEFAULT '0' NOT NULL;

DROP TABLE IF EXISTS packaging;
CREATE TABLE packaging (
 package_id int NOT NULL auto_increment,
 package_name varchar(64) NOT NULL,
 package_description varchar(255) NOT NULL,
 package_length DECIMAL(6,2) default '5' NOT NULL,
 package_width DECIMAL(6,2) default '5' NOT NULL,
 package_height DECIMAL(6,2) default '5' NOT NULL,
 package_empty_weight DECIMAL(6,2) DEFAULT '0' NOT NULL,
 package_max_weight DECIMAL(6,2) DEFAULT '50' NOT NULL,
 package_cost int(5) NOT NULL,
 PRIMARY KEY (package_id)
);

 

Personally I do not use dimensional support so I wont be much more assistance. But you may have missed this part of the instructions. Otherwise, it is because the p. is missing in front of the column names in the original sql statement with the error. Do you see those columns in your products table?

 

 

1. I'm not using dimension support and did not install it

 

2. Here is the code from my products table:

 

products

 

Field Type Null Default Comments

products_id int(11) No

products_quantity int(4) No

products_model varchar(12) Yes NULL

products_image varchar(64) Yes NULL

products_price decimal(15,4) No

products_date_added datetime No

products_last_modified datetime Yes NULL

products_date_available datetime Yes NULL

products_weight decimal(5,2) No

products_status tinyint(1) No

products_tax_class_id int(11) No

manufacturers_id int(11) Yes NULL

products_ordered int(11) No 0

[♥mdtaylorlrim]

Ok, it looks like the contribution files include the product_length, product_width, and product_height regardless if you install the dimensional support or not. This must be the first contribution that you have installed, right?

 

You will have to make a backup of your /admin/categories.php files

 

Then use an editor to find every instance of those three column references and delete them out of the sql statements.

 

Or you can simply add the columns to the database and fix the references in the sql statements. It's your call.

 

 

It probably added input boxes on your new product and edit product screens, right?