I just migrated a site from WP to CP using the plugin. Everything successful.
Edited a Page no problem.
Disabled Classic Editor plugin from WP figuring I would no longer need it.
Wrote post. Published post.
Upon publishing post I was immediately taken to the Block Editor including the welcome overlay.
I went to dashboard. Dashboard had reverted to WordPress 6.0.1.
Ran Classicpress migration plugin again. It confirmed I was back to Wordpress 6.0.1. Converted again. Seemed successful again.
Reactivated Classic Editor plugin because I’m spooked.
What gives, can a migrated site somehow, revert back to Wordpress?
Expected behavior
Please tell us what should happen.
Current behavior
Please describe the bug or issue, tell us what happens instead of the expected behavior. Please also include relevant screenshots.
Possible solution
Not obligatory, but suggest a fix for the bug, or some ideas for how to
implement your addition or change.
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.
2.
3.
4.
Context
How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the
real world.
It shouldn’t revert back as there is no mechanism for that. However, there are possible ways it could happen.
How was your WordPress installed? Did you use any installers such as Softaculuous or Installatron or any other installers they came bundled with your hosting?
Are you by any chance using managed WordPress hosting? Just making sure.
When I’m at my desk, I’ll run a few tests with migration plugin to double check. But so far no issues have been reported.
Looking forward to your answers.
P.S. Thanks for contributing on Open Collective. We really do appreciate your support
Some hosting a have one click WordPress installers that can revert CP to WP. But this happened during updates and I think was fixed…
Might be worth checking with your hosting provider also to understand if they are aware that CP is a fork of WP and it should stay as CP.
Personally I don’t use site ground, worth telling them CP exists because it seems their installer interprets the migration as a malicious change in core files and reverts them. If they are made aware they can change the installer script to avoid this.
That makes sense now. SiteGround has a custom automatic updater for WordPress. ClassicPress is technically seen by it as WordPress 4.9, so it runs the update and brings you back to version 6.
You may want to contact SiteGround support to see if they can disable it or modify their updater to recognize ClassicPress. We can provide more details if we know how they check for updates. Maybe you can send a link to this thread, so their team can review it.
It was the automatic updater. Siteground support says they have disabled the updater for the entire site but asked me to let them know if it happens again.
Yes, a known issue with Siteground indeed. I had tested them for a site, but gave up hosting it with them after I encountered a similar issue with automatic updating. Support was kind, but, based on that experience I had, I wouldn’t advise using them for a CP site.
I’ve contacted Siteground, asking if they were willing to tweak their updater to recognize CP. They said they will get back to me. So if I hear anything, I’ll update this topic.
