Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Bill in CA Posted April 4, 2022 Posted April 4, 2022 I started an upgrade to my site and quickly got an error message Specified key was too long; max key length is 1000 bytes /home/wfphotos/wfctest.com/system/Db/Db.php::2181 ALTER TABLE `ibf_core_attachments_map` ADD KEY `map_lookup` (`location_key`(250),`id1`,`id2`) I read up on that error and apparently a table type needs to be changed. I really wish that the upgrade program would check for things like that before changing anything. In the upgrade program I have two options - retry and continue. Both lead to a repeat of that error, no option to abort. Trying to access the board gives this: Site Owner This message means an upgrade is in progress. If this is not correct, try visiting the upgrade process again (usually /admin/upgrade) and choose either continue or restart. If the upgrade shows nothing to upgrade, visit the AdminCP and run the Support tool. You can also contact Invision Community support for assistance. In accessing the AdminCP it just gives me the continue option to continue. I was able to do a restore of my site so I'm back in business for now, and will look into changing that table tomorrow, but is there any way to see what else may need to be changed before going through all this again?
Marc Posted April 4, 2022 Posted April 4, 2022 It would seem your tables are likely using the compact row format. You need to ensure your tables are using the dynamic row format. If you are unsure how to do this, you would need to contact your hosting company on this Miss_B 1
Bill in CA Posted April 6, 2022 Author Posted April 6, 2022 Thanks, Marc. I have converted everything to InnoDB and the upgrade to my test system seems to have worked. It's building some indexes now so I'll check back on it later, but at least the upgrade went through and the test looks functional. Just a suggestion - if your upgrade job could scan the database for things likely to kill the job and warn the user before anything is committed it might save a few heads from being pounded on the wall. Hostingunlock 1
Marc Posted April 6, 2022 Posted April 6, 2022 8 hours ago, Bill in CA said: Thanks, Marc. I have converted everything to InnoDB and the upgrade to my test system seems to have worked. It's building some indexes now so I'll check back on it later, but at least the upgrade went through and the test looks functional. Just a suggestion - if your upgrade job could scan the database for things likely to kill the job and warn the user before anything is committed it might save a few heads from being pounded on the wall. While this is not shown on the upgrader, its actually shown as an issue in the support area of your admin CP
Bill in CA Posted April 6, 2022 Author Posted April 6, 2022 I saw that in another post, Marc, but I didn't spot it on my CP. I was about 6 months behind in updates - was that added relatively recently, or did I just plain miss it?
Jim M Posted April 6, 2022 Posted April 6, 2022 16 minutes ago, Bill in CA said: I saw that in another post, Marc, but I didn't spot it on my CP. I was about 6 months behind in updates - was that added relatively recently, or did I just plain miss it? The InnoDB check has been present for some time in the Support Tool/Dashboard. It has been something we recommended, I believe, since the beginning of version 4.
Bill in CA Posted April 6, 2022 Author Posted April 6, 2022 Somehow I managed to miss it. Just a suggestion to run that check as part of the upgrade for folks like me who are somewhat clueless. MikeHolly 1
Marc Posted December 1, 2022 Posted December 1, 2022 On 4/6/2022 at 6:35 PM, Bill in CA said: Somehow I managed to miss it. Just a suggestion to run that check as part of the upgrade for folks like me who are somewhat clueless. Please feel free to post this up within the suggestions are, if you wish to see this change in the future.
Recommended Posts