Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt November 11, 2024
Flat6 club Posted December 30, 2024 Posted December 30, 2024 Hello, We're trying to upgrade from self-hosted v3 to self-hosted v4. I got this error : I tried to follow the path but there is no setup/ folder in applications/ Thank you for your help.
Jim M Posted December 30, 2024 Posted December 30, 2024 I'm afraid, version 3 is no longer supported. If you need assistance with your migration, I would advise contacting a third party provider in the list here: https://invisioncommunity.com/third-party/providers-directory/
teraßyte Posted December 30, 2024 Posted December 30, 2024 It must be something related to some old modification you installed at some point. I don't recall seeing that error in all the 3.x => 4.x upgrades I've done. 🤔
Miss_B Posted December 30, 2024 Posted December 30, 2024 I'm not familiar with that version myself so I don't know if the aforementioned table is part of Ipb 3.4. or added by a third party plugin/app. You can try to re-add that table in the database and see if it will solve the error.
Flat6 club Posted December 30, 2024 Author Posted December 30, 2024 (edited) Thank you, problem solved! I installed a V4 from scratch, copied the table schema, re-created it, and it worked. Now, I have an even tougher one: Edited December 30, 2024 by Flat6 club
Miss_B Posted December 30, 2024 Posted December 30, 2024 30 minutes ago, Flat6 club said: Thank you, problem solved! I installed a V4 from scratch, copied the table schema, re-created it, and it worked. Now, I have an even tougher one: The error indicates that the total length of an index is too long. But I don't see any further details in the screenshot to point to the precise field and table where this ocurrs. The best way to avoid this type of error is to use InnoDB instead of MyISAM. InnoDB supports up to 3072 bytes for an index length in recent versions of MySQL.
teraßyte Posted December 30, 2024 Posted December 30, 2024 Make sure all your tables are using InnoDB + DYNAMIC row format and utf8mb4 charset. That will help avoid lots of issues during the upgrade.
Flat6 club Posted December 31, 2024 Author Posted December 31, 2024 Thank you so much! I switched to InnoDB, and it worked! However, I've encountered a new error: There's no indication of which file or table is involved, and I can't find any PHP error logs on the server. 😕 Any ideas?
Miss_B Posted December 31, 2024 Posted December 31, 2024 55 minutes ago, Flat6 club said: However, I've encountered a new error: There's no indication of which file or table is involved, and I can't find any PHP error logs on the server. 😕 Any ideas? It looks like to me as if a part of the code somewhere is not php 8 compatible.
teraßyte Posted December 31, 2024 Posted December 31, 2024 I usually update from 3.x to 4.7.3 using PHP 7.4, and after that to the latest version (4.7.19 now) using PHP 8.0/8.1. That's an option only if you have the 4.7.3 files, though. 🙄 Miss_B and Marc 2
Recommended Posts