Warning: #1364 Field 'customers_country_id' doesn't have a default value
Warning: #1364 Field 'delivery_country_id' doesn't have a default value
Warning: #1364 Field 'billing_country_id' doesn't have a default value
Warning: #1364 Field 'customer_referral' doesn't have a default value
Make those four columns nullable? I.e. remove the "NOT NULL" if you edit the SQL file. Or change it in phpMyAdmin.
Alternately, backfill them. You should be able to map from the country name to the ID for those three. The customer_referral seems like something that you added (possibly supporters' code), so I'm not clear what should be there. Perhaps that column should have a default.
PHP Notice: Trying to access array offset on value of type null in /home/xxxx/public_html/includes/system/versioned/1.0.7.10/database_order_builder.php on line 82
PHP Notice: Undefined offset: 0 in /home/xxxx/public_html/admin/includes/actions/orders/views/edit.php on line 181
PHP Notice: Undefined offset: 0 in /home/xxxx/public_html/admin/includes/actions/orders/views/edit.php on line 181
PHP Fatal error: DB: [1064] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at
line 1 from <SELECT COUNT(*) AS count FROM customers_wishlist WHERE customers_id = > in /home/xxxx/public_html/includes/system/versioned/1.0.8.1/database_core.php on line 44
PHP Notice: Undefined index: cID in /home/xxxx/public_html/includes/hooks/admin/customers/wishlist.php on line 17
Omar_one wrote: ↑Tue Aug 23, 2022 7:08 pm
PHP Notice: Undefined index: cID in /home/xxxx/public_html/includes/hooks/admin/customers/wishlist.php on line 17
That suggests that you're using the wrong version of Wishlist. You should be using the 1.0.8.5 and newer version, but that doesn't have cID on line 17. The 1.0.8.0 version does but of course won't work properly in 1.0.8.16.
[24-Aug-2022 17:46:25 Europe/Helsinki] Date input as [ucjUXlvxz] and parsed as [ucjUXlvxz]
[24-Aug-2022 17:46:27 Europe/Helsinki] Date input as [PlnaMJqIe] and parsed as [PlnaMJqIe]
[24-Aug-2022 17:46:44 Europe/Helsinki] Date input as [RJDtmQhNqaiyOT] and parsed as [hNqaRJtm]
[24-Aug-2022 17:46:45 Europe/Helsinki] Date input as [HtArWusmUCx] and parsed as [smUCHtrW]
PHP Fatal error: Uncaught TypeError: Argument 1 passed to Text::is_prefixed_by() must be of the type string, null given, called in /home/xxxx/public_html/includes/system/versioned/1.0.8.2/password.php on line 62 and defined in /home/xxxx/public_html/includes/system/versioned/1.0.8.2/text.php:42
Stack trace:
#0 /home/xxxx/public_html/includes/system/versioned/1.0.8.2/password.php(62): Text::is_prefixed_by(NULL, '$P$')
#1 /home/xxxx/public_html/includes/system/versioned/1.0.8.2/password.php(20): Password::type(NULL)
#2 /home/xxxx/public_html/includes/modules/content/login/cm_login_form.php(35): Password::validate('', NULL)
#3 /home/xxxx/public_html/includes/modules/content/login/cm_login_form.php(51): cm_login_form->login()
#4 /home/xxxx/public_html/includes/system/versioned/1.0.8.4/template.php(106): cm_login_form->execute()
#5 /home/xxxx/public_html/login.php(26): Template->get_content('login')
#6 {main}
thrown in /home/xxxx/public_html/includes/system/versioned/1.0.8.2/text.php on line 42
Last edited by ecartz on Wed Aug 24, 2022 3:34 pm, edited 1 time in total.
Reason:Shouldn't post user's password in the forum.
The first one is how the date is being submitted in the form. I do not know why. Spam attempt?
The second is telling you that the password is set to NULL in the database, which should not be possible. Find those rows and set them to a random password. It will never match, so they'll have to reset those passwords to log in.
ecartz wrote: ↑Wed Aug 24, 2022 3:42 pm
The second is telling you that the password is set to NULL in the database, which should not be possible.
My guess is the newsletter-subscription option. I may be a catalyst for that problem then, since I have made a newsletter subscription that just takes the email and creates a customer with no other info than that and subscription, and probably adviced others to do something similar... @Omar_one, I'll post a solution if I think of a good one before you (or others)
//Daniel
I'm not smart, but sometimes even a blind chicken can find a corn.
Here are a lot of corns: Phoenix user guide
ecartz wrote: ↑Wed Aug 24, 2022 3:42 pm
The first one is how the date is being submitted in the form. I do not know why. Spam attempt?
The second is telling you that the password is set to NULL in the database, which should not be possible. Find those rows and set them to a random password. It will never match, so they'll have to reset those passwords to log in.
thank you @ecartz for the first one maybe I will install Site Monitor, View Counter from old site
for the The second set NULL to no and set to the customers whos don't have password a random new password