Looking at this from a new user’s point of view, I went to the Get ClassicPress page:
I noticed there is nothing to tell me the latest WordPress version I can migrate from - I was looking for that info as well. I wonder if you need an info box at the top of the page that says something like: “Fully compatible to migrate from WordPress version 5.3.1”
The 10 Reasons to Switch to ClassicPress… page is excellent!
This is a really important point. I have tried using the migration plugin a number of times only to be met with “Sorry, it doesn’t work with your version” (my version always being the most up-to-date). It happened again recently when I was testing moving a site from WP5.5 with Woo over to CP and CC. I know it can be done manually but I always like to do things the way an average user would, so I can see any potential hurdles.
The most common scenario I can imagine is a user updating to the latest WP version, finding a bunch of issues and error messages, and thinking: “That’s it! I’ve had it with WP, I’m moving to CP”. So they download and install the migration plugin only to find it won’t do the job. At that point I expect we would lose many of them.
Can someone tell me what is required to bring the migration plugin updated to be working with the latest WP release? I don’t know anything about this; maybe it’s a complicated business that needs lots of testing so there will always be a considerable time lag.
@james is the best person to explain how the plugin is updated to support latest WP.
If I recall correctly there is a line of code specifying latest WP release and this has to be changed, then the plugin should be tested. Take this with a pinch of caution, for I am not able to find where it was explained (I remember there was a post here on the forums about this, but maybe it was on slack and got 10ked?).
Sorry, that was me going (slightly) off-topic. I was wondering about the time lag between a new WP version being released and having it recognised by the migration plugin. In an ideal world you shouldn’t need to have a statement about what WP versions it supports… it would just work with whatever you have. But I realise there is a need for set up and testing, so it can’t be immediate.
@Web242 my post was an answer to @ozfiddler that was wondering about how the plugin compatibility upgrade was made.
As concerns the notice about max version supported, I think it is needed because as the two CMS diverge the migration plugin will change and have a prominent importance.
This plugin is unique because it allows migrating from one to the other seamlessly without having to rebuild, as of now. And with our development proceeding sometimes it may get a delay in the update. So I suggest that whoever updates it to a new WP release also bumps up the number on the page to show it has been upgraded.
I am thinking, adding this force people to manually update page… Unless there is an automated way to do that (something like text changes when github gets an update to the latest WP or similar).
Or we can just include a note that explain how to check the latest supported WP release on the github plugin repo readme and eventually downgrade to that release before migrating… But this is opening another can of worms since not everyone is able to safely downgrade…
The plugin supports versions of WordPress from 4.9.0 up to and including the latest release. However, the plugin does need to be tweaked each time a new version of WP is released. To the best of my knowledge, this has yet to be done for version 5.5.
I have added a paragraph to the Get ClassicPress page confirming the above. Hope this is sufficient, at least for the time being.
Hi @1stepforward Thank you for updating the page so it’s more clear. As @james and core-team do indeed need time to update and test, it still might be good to include a sentence to indicate the current version, at least as a temporary measure.
My reasoning for building in a maximum WP version check is that the migration plugin will probably work fine for newer WP versions, until it doesn’t. I’m open to revisiting this decision, or to other solutions such as linking directly to the “how to override” instructions from within the plugin’s screen in the admin dashboard.