If you have been visiting this site for the past few months, you have probably asked yourself what was happening around the ClassicPress project. Well, fear not! There is a lot going on. Unfortunately it has not made its way onto this blog until now. So without further ado, let’s dive in and explore what […]
We are excited to announce the release of ClassicPress 1.1.0, available now. This update comes with the addition of a new top-level Security page to the admin screen. The new Security page is a centralized place for plugins to register their security-related settings, making it easier for users to find and audit all security settings […]
Since our August development update, work has continued on the upcoming ClassicPress version 1.1.0 – see the previous post for more details. At our last Core development meeting this past Thursday, discussion was centered around the tasks left to do. Based on our progress so far, we set an updated release date of Thursday, September 19, […]
ClassicPress 1.0.2 is a security release to match the security changes in WordPress versions 5.2.3 and 4.9.11. It is available now. This is best thought of as a “defense in depth” update. The vulnerabilities fixed here are not enough to let attackers into your site by themselves, but it is still a good idea to make sure your […]
As we near our first birthday as an organization, ClassicPress is finalizing work on version 1.1.0 to make sure it represents the stability and quality that our users love. Read on for more details.
We released stable versions 1.0.0 and 1.0.1 in March, and they are still actively providing a production-quality alternative to WordPress for over 1,600 active sites. Since then, we’ve been planning for the next versions of ClassicPress, and we’re here for the long term.
Testing is critical during the RC phase – if we have any new bugs in ClassicPress 1.0.0-rc2, we need to know now so that we can get them fixed before the final release! Otherwise, the final release will be out on Tuesday, March 5.
Thanks to careful testing and reporting from our users, we’ve become aware of several minor issues with last week’s 1.0.0-rc1 release. None of these issues will affect the functionality of new or existing sites, but they are still worth fixing.
It has taken us longer than we originally planned to get the final, official ClassicPress 1.0.0 version released, but we’re making steady progress. I’m providing a quick update from the core development team.