[Resolved] Beta candidate hangs when I use the migration wizard – continued

[Author]

Posts

[janeC-2]

Continuing on from the past support ticket:

Hi,
I have revisited this issue and tried to use the migration wizard but it does not work for me.

you said: Some of the Toolset assets are not loading correctly, and it appears to be because the URLs are not being formed correctly.

And that is because the URL settings for your staging site are wrong—they point to the production server, not to the staging site.

So I did this: Instead of using the Staging server which you said is my problem, I have created a subdirectory called test and migrated a copy of the site there using All in One Migration.

example of the problem

go to Dashboard>QA's> Select first post
Scroll down to qanda_related_service
click "Connect existing service provider"

it says 'no results found'

--
In your email response to me you said that you could get it to work - can you please explain the steps?

I can provide you with a login to a copy of the website set up in a sub-directory.

Jane

[Nigel]

Hi Jane

It's been a while so I don't remember the details, I'll have to investigate again.

The new site, it looks like the migration has not yet been run.

So, where you describe not being able to "Connect existing service provider", that is after running the wizard, would that be correct?

[janeC-2]

yes that's correct. It is after running the wizard. When we worked through this before, you said the following:

You may have noticed my colleague has updated staging 11 with the RC's and run the wizard, where he was able to observe the issue, and also identify the problem.

Some of the Toolset assets are not loading correctly, and it appears to be because the URLs are not being formed correctly.

And that is because the URL settings for your staging site are wrong—they point to the production server, not to the staging site.

So instead of a staging server, I just cloned the site to a subdirectory (/toolset) and ran the wizard. I still experienced the same issue. I thought it would be good if you just tried running the wizard to see for yourself that it causes an issue.

[Nigel]

Hi Jane

I think I see what the problem is.

I took a copy of the site with All in One WP Migration and installed it locally.

I went to Toolset > Relationships and it said the migration had not been performed yet (screenshot), so I ran it.

It mostly worked fine, there were some individual posts that could not be connected, presumably because of existing errors with the relationships as defined in Types 2. You can review the complete log here: hidden link

I then went to edit the first QA post ("How can I get my relative's super after they die?"), and scrolled down and found lots of existing connected posts (screenshot).

Now, the problem is a change in the UI which means you can't connect an existing Service Provider from this page as you did before.

Recall that in the prior version you simulated a many-to-many relationship with two one-to-many relationships, like this:

    Q&A            Service Providers
      \                  /
       \                /
        \              /
     related service providers

Now in the new version (Types 3) you can create actual m2m relationships, and when you do the UI lets you add connections to existing posts from the post edit screen of one side of the relationship.

But your migrated relationships are still two separate one-2-many relationships, and the UI isn't designed around adding "related" posts with such simulated m2m relationships.

That was partly an oversight, partly a question of developer priorities.

We are aware of the problem, and the solution is an additional step with the migration where simulated m2m relationships can be converted to actual m2m relationships. That will be included in the next version of Types (3.1) which is about to head into QA testing, and so should be available, realistically, in a couple of weeks.

So, looking at your site, everything works, but with a known UI deficiency that will be fixed soon.

Can you wait for Types 3.1 and then merge your one-2-m relationships into real m2m relationships, and then you'll find the UI updated accordingly.

[janeC-2]

Thanks Nigel,
I am happy to wait. I may need to double check with you about the simulated m2m relationships can be converted to actual m2m relationship

Should I still perform updates to the plugins as they become available? I have been updating but always wonder whether that's the correct thing to do if I haven't migrated the site.

Jane

[Nigel]

Hi Jane

You can continue updating, just hold off from running the migration wizard (which you will want to perform on a test site in any case to ensure it works as expected).

You might want to close this and then open a new ticket when you are ready to try the update (you can assign the ticket to me as I'm familiar with it).