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 on the site (documentation).
Along with the addition of the new top-level Security page, version
1.1.0 also includes some minor changes and fixes.
For a full list of the changes in this release, along with update and installation instructions, see our
1.1.0 release notes post on the forums.
In this release we had also hoped to include an option to show the site’s custom logo on the login page instead of the ClassicPress logo (petition). After we released a preview of this feature to the community, some issues with our current implementation became apparent (discussion), so we’ll be backing this feature out and revisiting it for a potential future version of ClassicPress.
As always, we’ll be around if you need any help, just make a new thread on our support forum.
Just over one year ago ClassicPress was started by Scott. Today, we have ClassicPress V1 out in the wild, are working hard towards V2, and are continuing to see our community grow. With the one year mark we are excited to announce a new website for ClassicPress.
This website was built by our community, and it is these same community members who help push ClassicPress forward and will ensure we succeed long term on our mission to become the business CMS.
This website has been a long time coming, so a special thank you to @timkaye, @raygulick, @codepotent, @1stepforward, @horlaes, @blueskyphoenix, (and others I am forgetting) for helping get it ready.
If you notice any issues please let us know on GitHub.
Since ClassicPress began in August of 2018, our all-volunteer team has worked hard to bring ClassicPress to you. Today, we are pleased to announce the first official, stable release of ClassicPress: version 1.0.0, codenamed Aurora, available immediately.
Starting with Aurora, the ClassicPress v1 series is a long-term support (LTS) version for businesses who want the power and stability of WordPress 4.9.x and are seeking an equally stable alternative solution. Since all existing plugins and themes that are supported on WP 4.9.x are supported in ClassicPress 1.0.0, Aurora is also ideal for those that find that WordPress 5.0+ is no longer a fit for them.
ClassicPress 1.0.0 is based on the codebase of the WordPress 4.9 branch (currently WordPress version 4.9.9) and contains all changes from this version of WordPress, including the latest security fixes.
Of course, we’ve also made the codebase our own. Read on for more details…
Major changes from WordPress
- Versioning strategy. We use the industry standard semver specification for predictable, logical ClassicPress version numbers.
- Development process. ClassicPress is developed on GitHub, which allows us to take full advantage of development tools such as Travis CI and Renovate.
- Security Updates.
- GPG signed releases. We publish our releases using signed
git tags and zip files served from GitHub, so that you know what you’re getting. Much more to come in future versions, including release verification during automatic and manual updates!
- Updates. ClassicPress serves new version notifications from our own API servers, again with a well-tested and clearly-defined versioning policy.
- PHP versions. ClassicPress requires PHP 5.6 or higher, as the first step in a strategy for encouraging ClassicPress users to keep their sites up to date. ClassicPress 1.0.0 also adds PHP 7.3 compatibility for all unit-tested code in the core software.
- Translations. ClassicPress serves core translations from our own API servers. ClassicPress core is currently translated into 10 languages, and more to come with help from our community.
- Admin dashboard. WordPress-specific features like community events and featured plugins have been removed and/or replaced with ClassicPress equivalents. For example, we’ve added a “Featured Petitions” widget to encourage community participation in our development process.
- Renaming. We’ve renamed all visual aspects and comments/docblocks from WordPress to ClassicPress. For compatibility, class/function and file names have been left alone.
- Installation. For new sites, ClassicPress has a re-branded installation process, with fewer steps. We also support installation using composer natively.
- Simplifications. We’ve removed the Akismet and Hello Dolly plugins, but they can still be installed from the plugin directory. We’ll be making the core software even leaner in version 2.
- Community. ClassicPress is what it is today due to input and support from our welcoming and thriving community. Thank you for helping us make ClassicPress a reality!
For a list of new or changed functions and filters in ClassicPress 1.0.0, see this post.
There are a lot of other places where we’ve been able to make small improvements to ClassicPress so far, such as better design and typography in parts of the admin dashboard, and other developer experience improvements. For more information, including links to download the release, installation instructions, and a more complete list of changes, please see the release notes on our forums.
We are excited about what the future holds for ClassicPress and encourage you to participate in the ClassicPress Community. We want to be the content management system of choice for businesses worldwide, and we need your support to succeed! Connect with us on Slack and join our forums and petitions sites to add your voice and vote to our community. Your contributions help ClassicPress continue to grow and thrive!
A word from Scott…
Today ClassicPress reaches a major milestone, and again I find myself without words to properly express my gratitude for each person in the Community who has worked to make Aurora happen. The time, effort and passion that has been dedicated to ClassicPress over these last several months has been awe-inspiring, and I am grateful for every hour each of you has given to the project. Thank you from the bottom of my heart. Truly, ClassicPress is Community-led, and I am thrilled to be a part of this journey with each of you.
I look forward to what comes next as we continue on toward creating a world-class content management system for businesses who want to have a powerful, versatile and predictable solution for their website needs.
– Scott Bowler
For more information, including links to download the release, installation instructions, and a more specific list of changes, please see the release announcement on our forums.
One of the most common support questions we get lately is regarding choosing languages in fresh installs of ClassicPress, and we hear you! Let’s break down how we got here, how you can help and what you can do if you want to use a language that’s not in our initial list of 10 translated languages.
How did we get here?
When ClassicPress was started back in August there was no infrastructure, and definitely no localization team, just a dream about how we could be better.
We knew out the gate that making sure ClassicPress was localized would be a monumental task. We needed to have tons of infrastructure in place, a team of translators and user feedback.
Work started on the localization infrastructure at the beginning of October (link). This continued with setting up API endpoints (link), and was finally included in Beta 2 (link).
In order to get translations served from the ClassicPress infrastructure in time for V1 we needed to prioritize which languages we would focus on first. The committee chose the 10 most-used non En-US languages to get started (link, at bottom). These 10 would provide the necessary foundation to begin testing our infrastructure and gathering feedback on which languages to focus on next (link).
A task this large was bound to hit some snags, and in spite of our best efforts, not everything went 100% to plan. After the discovery of some issues relating to wrong file names (link), we responded by quickly pushing out a fix to our servers to ensure users didn’t continue to face this problem.
How can you help?
For the ClassicPress V1 release, we’re focusing on making translations available for 10 of the most-used non-English (US) languages. We’re open to adding more languages once this initial effort is working well, but until then, we have made a temporary plugin that will let you use WordPress language packs for other languages. Please note that these won’t be fully translated and will not be supported long term.
With regard to the first ten languages, we need your help with Turkish, Spanish (Spain), Portuguese (Brazilian), Russian, French (France), and Japanese. If you are interested in helping with the these locales or any others, please join the #i18n channel on Slack or post a new thread in the i18n forum. Your assistance is greatly appreciated and will help to move this important part of ClassicPress forward.
What if I want to use ClassicPress with another language?
If you want to use ClassicPress with another language that is not on our list of 10 initial translations, we recommend installing the Use WordPress Language Packs plugin. This will provide you access to the WordPress Language Packs for the locales that aren’t yet supported in ClassicPress. Please keep in mind that when using a WordPress language pack, most strings will be translated, but not all.
Our community is what makes ClassicPress different, and we are grateful for your participation. Please reach out to any committee member with any questions you have on this or any other topic. Thank you for your support!