Jump to content

Recommended Posts

Posted

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.

Screenshot_2024-12-30_at_11_07_32.thumb.webp.0098c7e4dcf7f745cd6adfb0536d9206.webp

Posted

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. 

Posted (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:

image.thumb.png.adb7dced336a64ea7a4f317291df132e.png

Edited by Flat6 club
Posted
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:

image.thumb.png.adb7dced336a64ea7a4f317291df132e.png

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.

Posted

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?

image.png.d93a0de12be676213616ff24677824b7.png

Posted
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. 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...