Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Update from 2018.02.7 to 2018.08.9: Uncaught PDOException #7013
in my quest to update my Tine20 installation to a more current version, I encountered another difficult puzzle.
I tried to update to version 2018.08.9 coming from version 2018.02.7.
No modules where updated, since the version numbers stayed the same, from what I can remember.
I hope you have some ideas on this.
Trying to go back to the version 2018.02.7 resulted in the following error message when opening any Tine20 web page (login page or setup page):
This issue was resolved without any active intervention from my side in the next morning.
Going back from a half succeded update isn't the best idea imho. I hope you had a backup of your database which could be restored... If you have the choice, try to avoid 2018.02.7 (it is broken according to release page), stick with 2018.02.6.
The missing field 'is_system' was introduced to custom fields in Tinebase Version 11.39. It seems to me that it came with a later minor version of 2018.08.x. Hence, try to upgrade to a smaller minor before you go to the last minor version (normally. this shouldn't be necessary).
I had success upgrading: 2018.02.6 -> 2018.08.3 -> 2018.08.6 -> 2018.08.9.
And your idea concerning the intermediate minor releases did work fine until now.
I would highly appreciate an updated "Update Howto" documentation.
Concerning the next update steps, I will send an update on my success or my next issue here.
Many thanks for your support this far
OK, I managed to get to version 2018.8.6 without any problem.
Unfortunately it did not go on like this, but I encountered another error message while upgrading from 2018.8.6 to 2018.8.9.
The last line in the log seems more serious to me. It says the following:
Any ideas, on how to resolve this?
Hi, glad you did it so far. It is very unfortun that the update took you more than one minor update. But anyways... There are two errors remaining, the first is related to changes in 2018.08.9, I guess. It may go away if you get the seoncd issue fixed (if not please comment).
utf8mb4 is a DB collation and is required since 2018.08.5. Do you have utf8 settings in config.inc.php - if not, try