Hi, I've got an unusual situation in that earlier on in my development, I uploaded the beta version of Toolset. It seemed to cause some issues elsewhere, so support suggested I go back to the production version, which I did. I've since largely completed the site and uploaded all of my artists and artworks and related them with _wpcf_belongs_parent_id. Now I've updated Toolset. I do not get the prompt to migrate. Instead the one to many relationship I created in the beta version appears to have restored, and my old relationships are gone. How do I go about restoring relationships without having to go through 264 Artwork posts to assign them to their Artist post?
Response from Amir: "Can you please open a ticket about it in our support? One of our supporters will need access to your database. We'll check the status and help you manually modify the migration status, to trigger again what's needed."
Hi Julia,
I'm sorry for any inconvenience.
I've downloaded a copy of your website database to test the issue on my localhost.
I'm a bit confused about the issue. can you please guide me to the issue?
You may mention an example artist post where the issue exists or anything that guides me to the issue.
Thanks.
Hi Mohammed,
I'm not sure what I can show you, because what I want to see is not there!
I was almost completed this project when Toolset was updated. If you go to any of the Artwork pages on the front end, you can click on a thumbnail and see the image enlarged plus a title, and perhaps a 'SOLD' label. You *should* also see the artist's name. In a handful of cases, you can see the artist name, those are the Artwork posts that I've manually updated since the update.
Before the update, ALL of the Artworks were associated with Artist posts. These are what I'm trying to get back. I presume they are in the database as a special field of the Artwork CPT, and when I ran the update, I was not given an option to migrate relationships because there was already a relationship table there from when I tried out the beta version of the plugin.
Hope that gives you enough information to move forward.
Regards,
Julia
Hi Julia,
OK, let me check the database. hopefully, I can enable you to run the migration wizard again.
I will get back to you ASAP.
Thanks.
Hi Julia,
I contacted the developer and got this answer:
``When the migration is completed, we set an option toolset_is_m2m_enabled to "yes" and leave the previous postmeta in database... simply removing this option or setting it to "no" will bring back the legacy relationships. Obviously, any changes done after the migration will be irreversibly lost after this.
Then, it is possible to run the migration again - the previously created custom tables will be deleted and the whole process starts from the very beginning.
3:09 PM
I would highly discourage from experimenting with this unless it is a testing site, and always create a backup beforehand. Otherwise, more bad things will happen to the client.``
I did the previously mentioned change by the developer on your database to re-run the migration process again.
I found this warning while doing the migration: Unable to migrate an association from post #0 to #1897 to a relationship "artist_artwork": Unable to load posts 0 (0).
So, this should be reported earlier once you saw these warnings.
Anyway, I will escalate this issue so that it can be checked faster.
Please keep watching this ticket and I will notify you once I get anything from the second tier or the development team.
Thanks..
Hi Mohammed,
You can close this ticket, thanks. I've come to the conclusion that it is faster to manually apply relationships again in the new environment.
Regards,
Julia
