Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
MrFragicide Posted May 16, 2020 Posted May 16, 2020 When upgrading from 4.1.7 to 4.4.10, I'm getting this error and cannot continue. Specified key was too long; max key length is 1000 bytes /[...]/system/Application/Application.php::1636 Currently running PHP 7.4.3 and MySQL 8.0.20 running on Ubuntu 20.04 with Apache
Stuart Silvester Posted May 16, 2020 Posted May 16, 2020 1 minute ago, MrFragicide said: When upgrading from 4.1.7 to 4.4.10, I'm getting this error and cannot continue. Specified key was too long; max key length is 1000 bytes /[...]/system/Application/Application.php::1636 Currently running PHP 7.4.3 and MySQL 8.0.20 running on Ubuntu 20.04 with Apache I would recommend submitting a support ticket so we can take a look. (go to 'Client Area' above and then click on 'Support').
MrFragicide Posted May 16, 2020 Author Posted May 16, 2020 Ok, I solved the original issue by converting all the tables to InnoDB from MyISAM, but now I'm coming up against a SQL syntax error. You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-59),`index_object_id`)' at line 1 /[...]/system/Application/Application.php::1636 1 hour ago, Stuart Silvester said: I would recommend submitting a support ticket so we can take a look. (go to 'Client Area' above and then click on 'Support'). I'd rather try fixing this on my own first with ideas from others. Otherwise, what's the point?
bfarber Posted May 18, 2020 Posted May 18, 2020 Try to identify the full SQL query and we might be able to give some more advice. Unfortunately the error isn't showing enough of the query to really give any recommendations.
MrFragicide Posted May 19, 2020 Author Posted May 19, 2020 On 5/18/2020 at 8:42 AM, bfarber said: Try to identify the full SQL query and we might be able to give some more advice. Unfortunately the error isn't showing enough of the query to really give any recommendations. For now, I was able to roll back the server to PHP 7.3 and MySQL 5.7, which seems to have fixed the issue. I was unable to find the error or log of the error in the system to see exactly what the query was, but I will assume it was something that MySQL 8.0 did not like, or a deprecated function in PHP 7.4 outputting something erroneous into the query. Thanks for the assist, yall!
Recommended Posts