Skip Navigation

[Resolved] Database error after update

This support ticket is created 6 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 4 replies, has 2 voices.

Last updated by Sebastian 6 years, 9 months ago.

Assisted by: Minesh.

Author
Posts
#533836

After updating our test server with the latest toolset version we are getting the following error:

WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
CREATE TABLE wp_toolset_post_guid_id ( `guid` varchar(255) NOT NULL DEFAULT '', `post_id` bigint(20) NOT NULL, UNIQUE KEY `post_id` (`post_id`), KEY `guid` (`guid`) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

When I try to upload a new media I'm getting more toolset related errors:

WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
CREATE TABLE wp_toolset_post_guid_id ( `guid` varchar(255) NOT NULL DEFAULT '', `post_id` bigint(20) NOT NULL, UNIQUE KEY `post_id` (`post_id`), KEY `guid` (`guid`) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

WordPress database error: [Table 'db_dom18913.wp_toolset_post_guid_id' doesn't exist]
SELECT post_id FROM wp_toolset_post_guid_id WHERE guid='<em><u>hidden link</u></em>' LIMIT 1

WordPress database error: [Table 'db_dom18913.wp_toolset_post_guid_id' doesn't exist]
SELECT guid FROM wp_toolset_post_guid_id WHERE post_id=13904 LIMIT 1

WordPress database error: [Table 'db_dom18913.wp_toolset_post_guid_id' doesn't exist]
INSERT INTO wp_toolset_post_guid_id (guid,post_id) VALUES ('<em><u>hidden link</u></em>',13904)

Could you please help us? Thanks.

#534092

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This looks like the issue is with your database server. Could you please check with your hosting authority and try to check following solutions.

=> https://stackoverflow.com/questions/30761867/mysql-error-the-maximum-column-size-is-767-bytes
=> https://stackoverflow.com/questions/42043205/how-to-fix-mysql-index-column-size-too-large-laravel-migrate
=> https://stackoverflow.com/questions/24853828/index-column-size-too-large-the-maximum-column-size-is-767-bytes-for-int-dat
=> hidden link

#534745

So, what do you suggest? Making changes in the database configuration for either collation or settings to allow index for larger columns?
I don;t think this is viable.
Does the guid column need to be that large?

#535595

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Could you please update your Types plugin to 2.2.13 version which is published with the hotfix for the issue you have having.

You can download the latest Types plugins from plugins page:
=> https://toolset.com/home/types-manage-post-types-taxonomy-and-custom-fields/

#535607

After installing the upgrade the issue was solved.
Thank you vert much.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.