ClassicPress migrator updates to 1.1.1 nightly build instead of 1.2.0

As the title says.

Is this expected? Shouldn’t it update to the latest available stable release instead?

This is the message in the process logs:

Downloading update from…

And after the migration is successful if asks to update to CP 1.2.0

ClassicPress 1.2.0 is available! Please update now

No big deal of course, but a nuance that can confuse/give a outdated impression to new comers.

BTW migrating nuclear WP 5.8 to CP went very smooth.
No issues whatsoever.

I had to re-order and re-save the widgets thou, somehow WP 5.8 thought it does not like my widgets and put them all in a one-sidebar box instead of the areas I did have used before.
Also there where hundreds of errors related to blocks JS in widget editor after I migrated to CP (errors relating to undefined JS objects). I cleared cache and that solved the issue. Seems like WP 5.8 wanted to hunt me down to last instance :stuck_out_tongue:

Other than that, and now manually clearing the ugly <!--wp block--> comments out, there where no other major issues.
I even could proceed using Toolset despite their calls to do_blocks, by adding a sorts of shim to my theme that “fakes” do_blocks (and since I did not use any blocks with Toolset either, this solution works fine and silences any fatal error of “function not defined”)

So far so good, this gives me time to develop another solution in place of Toolset and keep the site running meanwhile using CP
With this, my second site is now officially running CP :partying_face:


Great to hear!

Re installing 1.1.1 instead of 1.2.0 we have an open ticket on GitHub to look into this once we have a stable 1.3.0 out :slight_smile:

1 Like

Perfect then, issue resolved.

1 Like