Abh Posted June 14, 2010 Share Posted June 14, 2010 I know other people had this problem and i've read all those topics, nothing works.I upgraded from v1.3.0.3 to v1.3.1 and now clients can't make accounts anymore getting that message.If i try to make an acount from BO, i get this: an error occurred while creating object customer (Unknown column 'id_default_group' in 'field list')Is this a bug or did i do something wrong? I imported the DB from the previous version for the upgrade.I also get the "This connection is untrusted" page when entering the cart :| - solved by generating a new .htaccesshttp://www.paranici.ro/ Link to comment Share on other sites More sharing options...
Abh Posted June 14, 2010 Author Share Posted June 14, 2010 Solved.What i did was look for ‘id_default_group’ and found an entry for version 1.3.0.4 inside the CHANGELOG that came with v1.3.1: Fixed bug at install (SQL error with id_default_group in PREFIX_customer) So i took the upgrade for that specific database (they're all inside \install\sql\upgrade\), changed the data inside it to match my tables prefix, then ran it through phpmyadmin and now i'm going to open a bottle of votka and sing 'we are the champions'. Cheers! Link to comment Share on other sites More sharing options...
burpitt Posted August 4, 2010 Share Posted August 4, 2010 Thanks to Abh for putting me onto this fix... To put this a little clearer (took me a little head scratching to fathom ) basically whats being said is that the file structure of the update has been complete, but the SQL structure updates during peoples upgrades have been overlooked. Now obviously where certain columns, fields, etc. are not existant in the SQL, the webshop is throwing up errors to suit..So going by Abh's idea.. I basically went through the whole /install/sql/upgrade folder, changed all the PREFIX_ to my SQL's prefix.. (ie instead of it being PREFIX_group on my DB its ps_group - the PREFIX is just a wildcard for the install to change).. and I then proceeded to work my way through the SQL dump files, importing them into phpMyadmin from the last time I did a version update. The main dumps I think that did the trick, was going up from 1.3.0.1 right up to current. This seemed to fix my problem, registration immediately reactivated after I'd updated the SQL. I also added a new Customer Group (in the BO) just for safety so it wouldn't bug out on any error it may have on the default group (more my pedanticism than a necessity).This IS fixable if thought about logically, and is caused mostly by user error.. So people shouldn't be slating the dev. team, more R T F M! Thanks again for your help guys..! Link to comment Share on other sites More sharing options...
PierreL Posted August 13, 2010 Share Posted August 13, 2010 Hi GuysI did a new install as this is the first time i am using Prestashop.The upgrade fix does not work for me. Don't know how to fix this.Isn't Prestashop releasing a bug fix to run ?I have the following error when adding a new client via adminan error occurred while creating object customer (Unknown column ‘id_default_group’ in ‘field list’)RegardsPierre Link to comment Share on other sites More sharing options...
overdoze Posted August 18, 2010 Share Posted August 18, 2010 Hi guysI read Abh's topic but i don't understand how it solve the problem, how upgrade the DB and the utility of changelog.Plz can u tell me how step by step coz i'm a bigenner and i don't know a lot of thingsregards Thx Link to comment Share on other sites More sharing options...
sam_al Posted September 21, 2010 Share Posted September 21, 2010 The idea is to create 2 new filed in PREFIX_customer:1. Add id_default_group after id_genderint(10), UNSIGNED, No Null, Default 1and 2. Add dni after firstnamevarchar(32), utf8_general_ci, Yes Null, Default NULLThat's all Link to comment Share on other sites More sharing options...
kolamap Posted November 23, 2010 Share Posted November 23, 2010 I followed what sam_al wrote Quote The idea is to create 2 new filed in PREFIX_customer:1. Add id_default_group after id_genderint(10), UNSIGNED, No Null, Default 1and 2. Add dni after firstnamevarchar(32), utf8_general_ci, Yes Null, Default NULLThat's all And it worked perfectly! In my case the table was called ps_customer but it was still mssing the dni, and id_default_group fieldsThanks sam_al! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now