Matt E Posted April 30, 2020 Share Posted April 30, 2020 After importing 4,000+ customers to a new store, I received the following error when trying to update any values like name, email, etc.: [PrestaShop\PrestaShop\Core\Domain\Customer\Exception\CustomerException code 0] After searching I found a solution in the following thread: https://www.prestashop.com/forums/topic/997945-category-problem-176-prestashopprestashopcoredomaincategoryexceptioncategoryconstraintexception-code-6/?tab=comments#comment-3200605 The problem was that the date_upd column is automatically populated with '0000-00-00 00:00:00' for every imported customer, instead of using the current date or registration date (date_add). The solution above requires manually updating the database to change these to a non-zero value, which I can confirm does fix the problem. This seems like a known issue since I am not the first to encounter it and should be a relatively simple fix. Can someone forward this to the right people so it gets fixed in the next version? Link to comment Share on other sites More sharing options...
Hsaneipour Posted December 25, 2020 Share Posted December 25, 2020 On 4/30/2020 at 8:09 AM, Matt E said: After importing 4,000+ customers to a new store, I received the following error when trying to update any values like name, email, etc.: [PrestaShop\PrestaShop\Core\Domain\Customer\Exception\CustomerException code 0] After searching I found a solution in the following thread: https://www.prestashop.com/forums/topic/997945-category-problem-176-prestashopprestashopcoredomaincategoryexceptioncategoryconstraintexception-code-6/?tab=comments#comment-3200605 The problem was that the date_upd column is automatically populated with '0000-00-00 00:00:00' for every imported customer, instead of using the current date or registration date (date_add). The solution above requires manually updating the database to change these to a non-zero value, which I can confirm does fix the problem. This seems like a known issue since I am not the first to encounter it and should be a relatively simple fix. Can someone forward this to the right people so it gets fixed in the next version? I have same problem some people say it is related to customer date_add or date_update, however I think it is related to other issues, Link to comment Share on other sites More sharing options...
Hsaneipour Posted December 25, 2020 Share Posted December 25, 2020 I found the solution pls check customer class and then see your database customer table and look which field is not compatible with type is defined in class 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