Can't switch to CP with plugin

[ozfiddler]

Expected behavior

Migrate to CP plugin should migrate my WP 5.3.3 site to CP.

Current behavior

I get this message: " This plugin supports WordPress versions 4.9.0 to 5.3.2 (and some newer development versions).
You are running WordPress version 5.3.3 ."

Possible solution

Update the migration plugin for later WP versions? I am using the one I downloaded direct from the CP site (says version 1.2.0)

Steps to reproduce

Provide a link to a live example, or an unambiguous set of steps to reproduce
this bug. Include code to reproduce, if relevant.

1. Try to migrate a WP 5.3.3+ site to CP.

Context

Testing Classic Commerce on a WP site on localhost. Trying to convert it to CP.

[ozfiddler]

I tested this on another, live WP site. Same result:

[wadestriebel]

If you use the advanced option you should be able to force the migration (ideally on a test site). If it works we can use the API endpoint to allow migrating from those versions.

[azurecurve]

I used the plugin to successfully migrate a site from 5.4 a few weeks ago.

[ozfiddler]

@wadestriebel

If you use the advanced option…

I know I could do it other ways. I was thinking more about the novice who is following instructions on the website on the “Get ClassicPress” page.

@azurecurve

I used the plugin to successfully migrate a site from 5.4 a few weeks ago.

Has anything changed recently? I can see in the plugin there is this in the comments:

 * @return array {
 *     "wordpress": {
 *         "min": "4.9.0",
 *         "max": "5.x.x",

But the API endpoint has this:

// WordPress versions allowed for migration.
'wordpress' => [
	'min'   => '4.9.0',
	'max'   => '5.3.2',

[wadestriebel]

@ozfiddler

I know I could do it other ways. I was thinking more about the novice who is following instructions on the website on the “Get ClassicPress” page.

I understand - but there will always be a slight delayed between versions until people can verify the migration works correctly. The best thing to do once verified it works is to open a PR saying so.

So if someone else can verify the migration works for 5.3.3 and 5.4.1 with no issues we can open a PR on that repo to adjust the max amount

[ozfiddler]

@wadestriebel

So if someone else can verify the migration works for 5.3.3 and 5.4.1 with no issues

Hmmm… how does one do that if the migration plugin doesn’t work. There is no mention of any “advanced option” on my page.

Don’t worry. I’ll ftp in the files.

[azurecurve]

I edited the migration plugin to up the version number so it would run.

[wadestriebel]

You could also just use the advanced controls that I mentioned above: https://github.com/ClassicPress/ClassicPress-Migration-Plugin/pull/56

[wadestriebel]

Here is a video showing the process. As mentioned, once we verify that the migration works successfully we can turn that on via the API for future users. At the end of the day someone has to test it to make sure it works before we push it live.

Preform Custom Migration with CP Migration Plugin

To show the form, paste the following JavaScript snippet in the developer console and run it:

jQuery('#cp-advanced-migration-form').removeClass('hidden')

To use it, enter a valid build URL. Or copy the link below for the most recent valid migration build.

https://github.com/ClassyBot/ClassicPress-nightly/releases/download/1.1.1%2Bmigration.20191019/ClassicPress-nightly-1.1.1-migration.20191019.zip

---

PS. Here is the open PR now that I have tested it: https://github.com/ClassicPress/ClassicPress-APIs/pull/20

[ozfiddler]

@wadestriebel

You could also just use the advanced controls that I mentioned above:

And, as I mentioned above, I don’t have them. This is what I see…

It just tells me to contact my hosting provider (?)

Wait… I just watched the video again. You have to do something in devtools to make the option appear? Is that right? I’m confused.

[wadestriebel]

@wadestriebel

To show the form, paste the following JavaScript snippet in the developer console and run it:

jQuery('#cp-advanced-migration-form').removeClass('hidden')

To use it, enter a valid build URL.

You need to paste the javascript snippet into the devtools. Or, wait until this PR is merged.

[james]

Thanks for the test and the PR Wade, I’ve merged it so the migration plugin will start working for WP 5.4.1 now.

The “advanced controls” section is disabled/hidden if any of the migration plugin’s checks don’t succeed. This is mostly out of an abundance of caution, I think we can just show the button if the only thing that’s wrong is the WP version. This will require a new version of the migration plugin, but it will remove the need to paste special code into the browser console as Wade did.

@wadestriebel

To use it, enter a valid build URL.

Only the migration builds will work when switching from WP. We’ll need to document this.