This thread is resolved. Here is a description of the problem and solution.
Problem:
The Types 3 migration wizard fails with the following message (+ PHP errors):
"Oops! There's been a problem when upgrading Toolset data structures. Please make sure your current configuration allows WordPress to alter database tables.If the problem persists, please don't hesitate to contact our support with this technical information:"
Solution:
The issue is solved with an update to Types 3.0.1 as described in the linked erratum
Link to a page where the issue can be seen: hidden link
After update I have on admin panel:
Oops! There's been a problem when upgrading Toolset data structures. Please make sure your current configuration allows WordPress to alter database tables.If the problem persists, please don't hesitate to contact our support with this technical information:
Changed type of spzzjj_toolset_type_sets.id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of spzzjj_toolset_type_sets.set_id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of spzzjj_toolset_type_sets.type from varchar(20) to VARCHAR(20) Table 'amidprestige_11.spzzjj_toolset_relationships' doesn't exist Table 'amidprestige_11.spzzjj_toolset_relationships' doesn't exist Table 'amidprestige_11.spzzjj_toolset_relationships' doesn't exist Table 'amidprestige_11.spzzjj_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.
-------------------
Link to a page where the issue can be seen: hidden link
After update I have on admin panel:
Oops! There's been a problem when upgrading Toolset data structures. Please make sure your current configuration allows WordPress to alter database tables.If the problem persists, please don't hesitate to contact our support with this technical information:
Changed type of mmzjzjz_toolset_type_sets.id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of mmzjzjz_toolset_type_sets.set_id from bigint(20) unsigned to BIGINT(20) UNSIGNED Changed type of mmzjzjz_toolset_type_sets.type from varchar(20) to VARCHAR(20) Table 'motomed.mmzjzjz_toolset_relationships' doesn't exist Table 'motomed.mmzjzjz_toolset_relationships' doesn't exist Table 'motomed.mmzjzjz_toolset_relationships' doesn't exist Table 'motomed.mmzjzjz_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.
I'd like to get a copy of your site to pass to our developers so that they can look at this straight away, and I will mark your next reply as private so that I can get site credentials from you.
Can you please confirm, when did this happen?
As soon as you updated, or when running the migration wizard?
What did you update from? Types 2.3 or one of the Types 3.0 betas?
Yes, you won't lose any settings just be de-activating and re-activating plugins and themes, but in such cases it is always advisable to make sure you have a current backup before you start testing.
Hi there,
I'm receiving a similar error message. I deactivated all plugins except Types 3.0 and changed my theme to 2017 but I still see the same error message.
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 'pantheon.wp_toolset_relationships' doesn't exist Table 'pantheon.wp_toolset_relationships' doesn't exist Table 'pantheon.wp_toolset_relationships' doesn't exist Table 'pantheon.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.
New threads created by Christian Cox and linked to this one are listed below:
Hi zbyszekZ, Nigel is out for the day but will return tomorrow to continue assisting you with this ticket. He already has the cloned files, so he should be able to escalate this problem quickly.
Our developers have had a hard time identifying exactly what the cause of this issue (reported by several users) is, but think they have found it.
They are currently testing an update to Types to fix the issue.
If you want you can try testing the fix with this version of Types: hidden link
Note, this hasn't gone through full testing yet. If you want to install it you should make sure you have a full backup prior first in case you find anything goes wrong.
If you do try it, please let me know if it resolves the problem, thanks.
Yes, you can't upload a plugin with the same name as one already installed, you will have to delete the previous version first, but do that only when you have taken a backup.
You won't lose and content or settings by deleting then re-installing Types.
