Error during upgrade

[Jamie_Beatson]

Hi there.

Getting the following error while I attempt to upgrade to the latest version:

Specified key was too long; max key length is 1000 bytes
/home/weareper/public_html/wapforum/system/Db/Db.php::2184

I'm not entirely sure what to do about this - can anyone help?
Thanks

[Marc]

First of all, revert to your backup, then visit support within the admin CP (top right) In there, address all mysql items that are showing in that area. 

 

[Jamie_Beatson]

Hi there - I've done that but I'm not seeing any issues in Admin CP/Support. The only thing showing is "Enable utf8mb4" - though the system won't let me convert the database.

Is that likely to be the root issue?

[Randy Calvert]

Take a look at:

🙂 

[Marc]

15 hours ago, Jamie_Beatson said:

Hi there - I've done that but I'm not seeing any issues in Admin CP/Support. The only thing showing is "Enable utf8mb4" - though the system won't let me convert the database.

Is that likely to be the root issue?

It is indeed likely related. Also compact row format if that is showing. You mention you the system wont let you convert it. What is actually happening when you try?

[Jamie_Beatson]

It's a bit weird - yesterday it simply wouldn't let me convert the database - it just failed. I didn't save a copy of what came up because I ran out of time and was coming back to work on it today.

Today I've got further with it - it appears to have gone through the conversion process and I then get to this message:

In order to finish the conversion:

1. Open the /home/weareper/public_html/wapforum/conf_global.php on your server.
2. Locate the sql_utf8mb4 declaration, which may look like this:

   'sql_utf8mb4' => false,

   Or like this:

   $INFO['sql_utf8mb4'] = false;

3. Change the false to true. If neither line exists, add the second version to the end of the file and change the false to true. Do not change any other aspect, including any comma or semi-colon after the false

I've gone into the relevant file and the second line already exists in the conf_global.php file. It was already flagged as true. I then click the finish button and it just goes back to the same page - nothing changes and it doesn't appear to complete the process.

[Miss_B]

What is the Collation set to at the database? What version are you upgrading from?

[Marc]

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

 

[Jamie_Beatson]

Hi there, apologies for the delay in replying, I've updated by access information - you should be able to get in now.

[Marc]

You would need to contact your hosting company on this issue. This is cause by compact row type being used. All tables need to use dynamic row type.

[Jamie_Beatson]

Thank you, I'll do that now.

[Jamie_Beatson]

Hi there- bringing this back up as I'm only now getting time after the holidays to revisit this issue.

I've converted my tables to dynamic row format - I've checked the information_schema on my database and they are all showing as dynamic. I've had to alter them all manually as I don't appear to have permissions via my hosting provider to set dynamic as the default row format.

I'm now back with the same issue I was having in my December 1 post - I can't complete the Enable utf8mb4 process. I'm still getting the same issue where it goes through the conversion process then asks me to change the variable in conf_global.php to true (it is already set to true) - but when I press "Finish" nothing happens and it just refreshes the same page.

Any further suggestions?

[Jim M]

This would likely indicate it is not set appropriately or it isn't able to read the set value. Could you please provide us access so we can review your conf_global.php?

[Jamie_Beatson]

You should have access now!

[Marc]

If you have switched the row format, you first need to upgrade (the row format will have been causing your original error)

[Jamie_Beatson]

Ah OK, so I can carry out the upgrade and *then* enable utf8mb4? Apologies - I'll go and try that today and see how it goes!

Thanks,

Jamie

[Marc]

Yes, I would do it in that order

[Jamie_Beatson]

Running the upgrade again and getting the same error as the first time round:

 

Specified key was too long; max key length is 1000 bytes
/home/weareper/public_html/wapforum/system/Db/Db.php::2184

 

Have confirmed that the row in the table is set to Dynamic and I can't see a reason why I can't go any further. Any ideas?

[Stuart Silvester]

Hi Jamie,

We'll take a look at this via a ticket, keep an look out for an email from us.