Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted December 22, 20213 yr Hi, I get the following error during an upgrade, see screenshot. Did i miss some steps to do before an automatic upgrade?
December 22, 20213 yr Community Expert Hi, I get the following error during an upgrade, see screenshot. Did i miss some steps to do before an automatic upgrade? What version are you upgrading from?
December 22, 20213 yr Community Expert What table type is that table using? Are you using all INNODB tables?
December 23, 20213 yr Author What version are you upgrading from? According to the database last version is/was 4.6.3 What table type is that table using? Are you using all INNODB tables? All InnoDB, except for core_message_posts, core_message_topics and core_search_index
December 23, 20213 yr Community Expert According to the database last version is/was 4.6.3 All InnoDB, except for core_message_posts, core_message_topics and core_search_index I have created a ticket so we can get this resolved for you
December 23, 20213 yr Management Solution If you Google the error message, the suggestion is to do: ALTER TABLE core_themes ROW_FORMAT=DYNAMIC;
December 23, 20213 yr Community Expert Thanks! Please see the subsequent message from my colleague above. The issue you are having here is hosting unfortunately
December 23, 20213 yr Author If you Google the error message, the suggestion is to do: ALTER TABLE core_themes ROW_FORMAT=DYNAMIC; Thanks Charles, this worked! You're better at Googling then i am apparently 🤦♂️
December 23, 20213 yr Author Thanks everyone for helping me fix this. I now have the issue again from before i started the upgrade: friendly url's don't work, they all get a 404. Should i open a new topic for that?
December 23, 20213 yr Community Expert Thanks everyone for helping me fix this. I now have the issue again from before i started the upgrade: friendly url's don't work, they all get a 404. Should i open a new topic for that? Yes, please. I would suggest on that however checking that you have the htaccess file in place