Is that because it won’t handle the latest version of WP? This is a problem that I’ve come across a number of times. I’m not sure what the answer is about the lag there.
Yep, just tested it. The migration plugin doesn’t work for WP 5.6. This is a perennial problem and must be putting off a lot of potential users.
On the point of latest WP version not migrating.
Assuming the latest wp update is what brought on the reason to leave WP.
We need that process to be as smooth as possible. Asking the average user to roll back their version of WP before they can migrate would possibly change their mind about migrating.
@David_Waumsley would you be able to provide some more details of why the migration plugin doesn’t work, such as:
- error messages
- plugins installed
- which theme are you using
Or is it simply that you’re already running WP 5.6 and the migration plugin doesn’t give you the option to migrate?
Anything like that would be helpful.
Ah, the last one. I was running 5.6.
It’s seem so. I think I spoke too soon as did not have much time to get to the bottom. I just saw a post with someone reporting similar and the answer seemed aimed at developers.
You gave me an easy solution. Thank you, I clearly missed that the migration plugin only was not working on WP 5.6. It could simply be that I am a bit dumb (certain!), but I bet I am not alone.
Unfortunately, there will always be a delay after a new WP release before the CP migration plugin is compatible. The length of the delay is usually determined by the nature of the WP release - for instance, whether it’s a major or minor release.
We are currently working on updating the migration plugin for WP 5.6 and this should be available soon.
Migrations using some themes do not work for WP 5.6 (more details). We knew something like this would happen eventually, so it’s better to only allow the migration from a new WP version once we’ve tested and confirmed that it works. In this case we’ll need to do a new ClassicPress release in order to fix that issue.
Yes, I understand the need for testing. It just doesn’t seem to get done until someone complains on the forum (from memory I have posted 3 times in the past about this).
Would it be possible to add an option that overrides the usual version checks. So it would say something like “WARNING: CP has not been tested with this version of WP. Proceed at your own risk and make sure you have a good backup”.
I know there is a manual process but as David said…
It might also be good to link it up with this idea: Contributing to ClassicPress
I don’t pay much attention to WP updates, so I am not even aware when one is released. If a “needs doing” job could be posted that says “WP 5.6 needs testing with migration plugin” that would bring it to more people’s attention.
No. There are already a ton of warnings during the migration process and we know they are not being followed. Taking action that has a non-negligible risk of breaking your site should require jumping through a small hoop.
Where? Who’s going to post this?
…and I end up doing it. I think exactly 1 person has asked me how to do that update in the past. I want more people to step up and help with tasks like this.
That may have been me. It involves a PR and I looked at the code and realised I didn’t feel confident in touching it. I would certainly never have picked up the potential 5.6 problem.
There was a suggestion that we set up a central place to post jobs that need doing, so people who want to contribute have some idea of where they can help.
Yep, understood. OK, I would help if I could but I am not a dev. We’ll have to accept that the migration plugin will have a lag with the latest WP version.