[Resolved] Relationship Migration errors on upgrading

[Author]

Posts

[Christian Cox]

So any warning/error messages other than that one legacy relationship are not needed.
Aside from unnecessary messages, is there any problem you can see with the relationships that were successfully migrated?

[jeffC-3]

I really didn't verify everything. Because of all the error messages, I figured something didn't work correctly. If I could get it to work again like that first run, I'd be happy.

[Christian Cox]

Can you describe the process you go through to replicate the Production site in your Development environment, in technical terms? Are you using a system like Duplicator, or All-in-One WP Migration? Are you using Toolset's Import/Export tools? Are you using WordPress's Import/Export tools? Are you manually modifying URLs in a database dump file? Are you completely wiping the development database and filebase first, or overwriting? Are your server environments identical in terms of memory and PHP configurations?

Any additional information you can provide to help me replicate the problem will be helpful.

[jeffC-3]

My web host is Nestify. It comes with a staging environment. All I have to do is go to manage the staging site and pull the database and files by clicking a button. I am not sure how it does it automatically.

[Christian Cox]

After you pull down to staging using their automatic process, can you create a database dump file from the staging database? I can try to replicate the problem using that file and make comparisons to the production migration.

[Christian Cox]

I get exactly the same results with this database set - the migration log text is identical to the log produced by migrating the production database.

[jeffC-3]

Sorry for the delay but your website has been down. After your message, I did the migration using the same set of data on staging. Sure enough, it worked like the first log I sent. Go figure.

I'm just going to take the chance on Saturday morning when it's quieter on the site and upgrade on production. If it fails, at least I have the data in these tables on staging to insert into the empty tables on production:
wp_toolset_associations, wp_toolset_relationships, wp_toolset_type_sets tables (BTW, wrong table name listed for the last one in the migration log)

I thought it didn't work correctly showing my Views, but then realized I hadn't upgraded the Views on staging, and then it worked. BTW, when looking at the Views problem, I have had recent problems with the popups even before this release while in edit mode with the popups showing all the data, cancel buttons, etc. (attached) I have not determined if it's browser-specific or what, but I'll write another ticket if needed for that.

Will update this based on my upgrade Saturday morning. Thanks.

[Christian Cox]

Okay great, I'll stand by for your update.

[jeffC-3]

I couldn't wait, so I ran the migration early this morning on production. Thankfully it migrated and produced the same log file as the first along with the error messages of items that shouldn't be there.

I'm still not confident though if I can delete safely from the database the warning messages that contain: vineyard_twitter-account, vineyard_contact, wine-trail_wine-trail-member, winery_twitter-account, winery_wine-trail-member, winetrail_wine-trail-member
These shouldn't be used anywhere because all the post types, content templates, views, etc. were deleted using Toolkit.