Duplicate Upgrade to 2.3.5

[Casa Ivar]

Affected version

2.3.5

Ideas?

 

[Chris D]

See here:

Fixed Post in thread 'v2.3.5 Upgrade Error on Step 8 Data too long for column 'provider_metadata''

Jan 30, 2025

Cool You bumped into an issue we didn't hit during testing.

For now run this query:

ALTER TABLE `xf_purchase_request`MODIFY `provider_metadata` VARBINARY(500) DEFAULT NULL;

Then restart the upgrade and it should continue where it left off.

• Chris D

• 

 

[Nicky Vermeersch]

Fix with this query does not work for me

 

[Chris D]

The maximum theoretical length of the data that can appear in that field is considerably less than 500.

My strong suspicion is that somehow the field length change hasn't taken effect. I would have to ask you to check again, making sure you're in the right database (for example).

If everything looks correct, we're happy to take a closer look if you can provide access to your database if you submit a ticket.

 

[Casa Ivar]

The maximum theoretical length of the data that can appear in that field is considerably less than 500.

My strong suspicion is that somehow the field length change hasn't taken effect. I would have to ask you to check again, making sure you're in the right database (for example).

If everything looks correct, we're happy to take a closer look if you can provide access to your database if you submit a ticket.

The query did not work for me either. Had to replace the table with a backup of that table from earlier that day. Now works.