-
-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error upgrading to 2.1.13 #228
Comments
In order to check what step failed, I suggest you to do as this:
Please come back |
I had a similar issue - My upgrade was failing when trying to import my SMTP details in to the MISC table. The issue in my case was that my SMTP details in the settings.php were enclosed in single quotes - $smtp_server = 'localhost'; Swap them out for double quotes, reload the upgrade page then launch it again and all upgraded correctly. Cheers, Owen |
Thanks @owindsor, that did the trick. |
Sure I will Thank you for the tip ;-) |
For me, my table and the file match up through these fields: Then, the next line in my table is the field "log_connections", but in the php file it is I guess trying to insert the field "menu_type" which is where it is failing. Also, I also noticed that my mySQL tables are of a different field count, so for example, I am running 2.1.12, and the schema for the items table is different than of .13 from a fresh install. See attached screenshots. |
I had the same issue, this is a double-single-quotes issue as owindsor said. |
In install/upgrade_ajax.php, line 303, single quotes should be removed from SESSION variable values: |
Thank you for this finding! |
Just had the same issue upgrading to 2.1.15, commenting these lines helped, atthough I didn't dig deeper to look which one: // array('admin', 'log_accessed', '1',1), |
Trying again, it failed on one of these: |
Upgrading from a 2.1.9, I get an error at step 4 : "An error appears when inserting datas!" and
"Misc table will be populated with new values" appears with an exclamation mark.
I've been unable to find the actual error, is there a way to trace what went wrong (a log or something)?
Any idea of what can cause this behavior (This is an install that's been updated regurlarly from the cpassman era).
Beside that, the error message should really read : "The error " . $description_of_error_here . "appeared while inserting data."
The text was updated successfully, but these errors were encountered: