Exclusive eBooks, Software Solutions, Quality Guaranteed
 
Web NukeBiz
Welcome to NukeBiz · Members
Bugger
 
of 6

 #103 » Database Error
 Date Open: Nov 28, 2009 at 13:00:59    Last Update: Nov 28, 2009 at 17:30:06 Bugger Off: Nov 28, 2009 at 17:30:06 
 Description: During Upgrade of my test site I got this.

CMS Warning line 75: On /rfe/admin.php?op=modules&upgrade=32 While executing query "SELECT config_value FROM cms_cart_config WHERE config_name=companyCountry" the following error occured: Unknown column 'companyCountry' in 'where clause' In: /homepages/12/d91017768/htdocs/LocalQuality_com/rfe/modules/Storez/cpg_inst.php on line: 1142
 Request: Bug
 Application: Module
 Module: storez
 Solution: fixed - unquoted value.
 Bugger From: RickC
 Debugger: Phoenix
 Group Access: All Visitors
 DiscussIt Forum: Storez
 DiscussIt Topic: Database Error
 Status: Done
 Priority: High
 Topic Replies:
 Phoenix
 Nov 28, 2009
 17:28:32
Well, that was a damned stupid mistake Embarassed

Sorry - download updated.

I expect it was the same issue as reported by thewarden.
 thewarden
 Nov 29, 2009
 18:41:31
Still doing it for me. Was there a different file I should have downloaded? After reading your reply, I downloaded the storez package and started over. Still getting the error.

Quote::
includes/db/db.php

* CMS Warning line 75: On /admin.php?op=modules&upgrade=17 While executing query "ALTER TABLE cms_cart_products ADD shiplength FLOAT(6,2) NOT NULL DEFAULT '0.00'" the following error occured: Duplicate column name 'shiplength' In: /home/smithsgr/public_html/modules/Storez/cpg_inst.php on line: 1104

Is this because the previous attempt did make some changes before getting the previous error? And now it's erroring?
 thewarden
 Nov 29, 2009
 18:59:32
Ok, since it appeared that the error was about an existing column, I went ahead and commented out lines 1104, 05, & 06 of cpg_inst.php, and tried again, and no more error. It seems to have worked. So far so good. Will this be ok??
 Phoenix
 Nov 29, 2009
 20:46:31
Quote::
Is this because the previous attempt did make some changes before getting the previous error? And now it's erroring?
Yes - your solution is the best way around it.
150 buggers listed, 109 buggered off, 31 declined, 8 on hold.