Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

E-Commerce Modules /

Discuss about the various e-commerce modules available:
Ecommerce, SS Shop, SilverCart and SwipeStripe
Alternatively, have a look the shared mailinglist.

Moderators: martimiz, Nicolaas, Sean, frankmullenger, biapar, Willr, Ingo, Jedateach, swaiba, simon_w

user error on /dev/build after installing ecommerce 0.6


Go to End
Reply


9 Posts   1774 Views

Avatar
Nickt

Community Member, 43 Posts

25 March 2010 at 6:52pm

Edited: 25/03/2010 6:53pm

[User Error] Couldn't run query: ALTER TABLE `Order` CHANGE COLUMN `hasShippingCost` `_obsolete_hasShippingCost` tinyint(1) Duplicate column name '_obsolete_hasShippingCost'

I have given mysql database full permissions (including alter), but when i run /dev/build i get this error.

see full error attached.

Thanks.

Avatar
Henk Poley

30 Posts

29 March 2010 at 2:04am

Did you already have an "_obsolete_hasShippingCost" column in your database?

Avatar
Nickt

Community Member, 43 Posts

29 March 2010 at 4:05pm

Yes, in the table "order". thanks

Avatar
kb

Community Member, 4 Posts

30 March 2010 at 12:50am

Edited: 30/03/2010 12:50am

You seem to have upgraded at a previous moment. Simply remove the column by hand (or with your preferred SQL application). Columns named _obsolete can generally be removed without problems as they are remnants of old code.

(Not handling existing _obsolete columns could/should be considered a bug in /dev/build)

Avatar
Nickt

Community Member, 43 Posts

30 March 2010 at 4:13pm

I deleted _obsolete_hasShippingCost but now i get another error (see attached)

Avatar
Nickt

Community Member, 43 Posts

30 March 2010 at 4:58pm

I just deleted all records from Order (all the orders that people had made) and now i get a new error, see attached:

Avatar
Nickt

Community Member, 43 Posts

31 March 2010 at 4:21pm

please help

Avatar
supermegaultra

Community Member, 33 Posts

13 April 2010 at 11:43am

I have the same original problem and wouldn't have a clue on how to fix it.

The only issue this presents for me is that I get a non specific error while trying to access the reports tab in the backend cms.

Please help!

Go to Top