Error notice after upgrading to Types 3.0

Symptoms

After upgrade to Types 3.0. you may have seen an error notice such as this:

The technical information part says something like this:

Changed type of wp_toolset_type_sets.id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of wp_toolset_type_sets.set_id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of wp_toolset_type_sets.type from varchar(20) to VARCHAR(20) Table 'db_dom25784.wp_toolset_relationships' doesn't exist Table 'db_dom25784.wp_toolset_relationships' doesn't exist Table 'db_dom25784.wp_toolset_relationships' doesn't exist Table 'db_dom25784.wp_toolset_relationships' doesn't exist Duplicate column name 'relationship_id' Can't DROP 'relationship'; check that column/key exists Duplicate key name 'relationship_id' The m2m-v1 database structure upgrade to m2m-v2 seems to have failed.

It would be displayed only to administrators and only in rare cases; we didn’t fully understand all the conditions needed for it to happen, but it is happening only on sites that:

• do not use any post relationships,
• run on MySQL 5.6 or lower
• have default database encoding utf8mb4 or similar (with more than three bytes per character).

Other than being unable to start using post relationships, we are currently not aware of any other side-effects.

Workaround

This issue will be fixed in the upcoming release, Types 3.0.1.

The workaround is more complex than usual and requires using a development version of Types.

This version is based directly on 3.0 and contains only other minor changes mentioned in other errata on this site.

If you decide to apply it, please make sure that:

• you create a backup of your site that you can easily restore in case something goes wrong
• you re-check errata you might have applied before – it is theoretically possible that you may need to re-apply some of them

You can download this version here: types.develop.195107.