Skip Navigation

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

This support ticket is created 6 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 6 replies, has 2 voices.

Last updated by janeC-2 6 years, 5 months ago.

Assisted by: Nigel.

Author
Posts
#746501
beta3.jpg
beta2.jpg
beta1.jpg

Continuing on from the following support query: https://toolset.com/forums/topic/how-to-prepare-your-sites-for-the-new-post-relationships-coming-in-types-2-3/

I am testing the Beta candidate on my staging server.

I installed the gutenberg plugin plus BC for Types, Views, Layouts and Forms

I ran the migration wizard and which indicated all was okay with some minor warnings (see screenshot beta3).

I then clicked 'finish' and it is hanging with the Relationships title at the top of the screen - (see screenshot beta1)

If I click on the CPT called QAs and scroll down to the related info the hanging progress bar shows (screenshot beta2)

#746692

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Jane

This is the same site as before? Where the wizard had worked (but you had the UI issue)?

I was going to take a copy to pass straight to the developers to analyse, but the password you provided is incorrect.

Let me mark your next reply as private so that you can update it.

#746732
#746889

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Thanks for that. I have passed a copy of your site straight to the developers to analyse.

I'll get back to you with their findings.

#765804

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Jane

We are having problems reproducing the problem with the copies of your site.

staging10 appears to be a version of the site where the migration wizard has already been run with the RC versions of the plugins, while staging11 is a "before" version with the current stable plugins.

On a locally-installed version of staging10 I don't see any problems when I try to edit a QA post, scrolling down to the bottom to see the related posts.

On a locally-installed version of staging11 I saw a couple of warnings about missing posts while running the migration, which otherwise worked as expected. Upon completion I was able to edit QA posts and see the related content.

Can I try the same on the staging11 site on your own server?

#765805

Yes that's fine you can try it on Staging 11

#775465

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Jane

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.

Note the two screenshots. One is from your staging site but shows the production site for the URLs. The other is my locally installed copy of your site (where I did not experience any problems), which shows the URLs updated for the location of my install.

I don't know how you are generating your staging versions, but normally updating the URL would happen automatically when you use a tool such as Duplicator or All in One WP Migration (which you have installed).

If you create a new staging version from the current production site and make sure the site URLs are correct (updating manually if required) then try again with the RC's and you should find they work correctly.

Let me know what you find.

#1074782

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