ClassicPress releases Beta 2 version

ClassicPress Beta 2

ClassicPress has released the second Beta version of its CMS. This includes the security updates for WP 4.9.9 as well as some other code improvements and widget changes.

ClassicPress is working towards its release of the first stable version, V1.0.0 and the release of the 1.0.0-beta2 version has brought some much needed changes:

  • Security: Sync with changes from WordPress 4.9.9 (including the same fixes as 5.0.1)
  • Change dashboard news from WordPress News to the ClassicPress Blog
  • Serve translations from ClassicPress infrastructure
  • Add ClassicPress Petitions Dashboard widget
  • Replace all references to WP support with ClassicPress forums
  • Update or remove version strings in enqueued assets and generator tags
  • Keep all build dependencies up to date using Renovate
  • Miscellaneous other fixes and improvements

The problem with Sucuri and some other security sites seeing installations as WP 1.0.0 appears to be fixed, with my sites showing as simply “WordPress” or “WordPress 4.9.9”.

New widgets for the dashboard in the admin panel now link to ClassicPress and not WordPress. This includes linking to the CP blog instead of WP and a new widget displaying the petitions, which are the requests users have made for changes to how CP works.

Unlike WP, if users want to see a change in the CP core, they can add it to the petitions site. If the vote for the change reaches 50, then it is put to the wider community for a vote.

The Beta 1 version introduced the ability to upgrade your installation from the admin panel, so upgrading to Beta 2 simply shows as an update, just like plugins. You merely need to allow it, and your site is upgraded.

The CP team are being kept very busy, not only keeping up with security issues, but working on language translations. More and more people, both users and developers, are hearing about ClassicPress and the effect is snowballing.

With the reviews of the Gutenberg plugin now three to one against (1200:400), it is plain that it is not something people want. Installations of the Classic Editor plugin, which effectively over-rides Gutenberg in WP 5.x.x have exceeded 1 million, showing that users prefer to turn block editing off.

This opens up a huge potential market for disillusioned WP users and developers to try CP. For sites that rely heavily on custom coding, using Gutenberg is not a viable option. Even regular users are shunning Gutenberg and prefer to use the traditional editor or their own page builder plugins.

I think 2019 is going to be an interesting year and one that will reveal whether or not introducing block editing into the core of WordPress was the right thing to do.

 

Leave a Reply

Your email address will not be published. Required fields are marked *