ClassicPress is a community-led fork of the WordPress content management system. We want to get back to basics and focus on open dialogue and democratic decisions. To learn more, view our mission statement.
ClassicPress is released under the GNU General Public License version 2 (GPLv2) (or later) license from the Free Software Foundation. A copy of the license is included with every copy of ClassicPress, but you can also read the text of the license at https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html.
Among other things, the GPLv2 license requires that any code you write that derives from ClassicPress, and which you distribute for use by others, will automatically be covered by the GPLv2 license.
ClassicPress is a community-led fork of the WordPress Content Management System; Classic Editor is the TinyMCE editor, used by WordPress for many years until the introduction of the block-based Gutenberg editor.
ClassicPress is the business-focused CMS; our tag-line is:
Powerful. Versatile. Predictable.
ClassicPress is a modified and enhanced version of WordPress (without Gutenberg) that primarily serves the business website market, but can be used by any organisation, large or small, or individual who wants a powerful, versatile and predictable CMS.
ClassicPress Version 1 will remain fully compatible with WordPress 4.9.x and will be an LTS version (Long Term Support) as we plan to support the ClassicPress v1.x release series with bugfixes and security updates for as long as people need it. ClassicPress is following the semver versioning scheme, which means that in the 1.x.x release series there can be no breaking changes from 1.0.0.
If there are potentially breaking changes in ClassicPress v2.x, we will add a new screen to the upgrade process explaining the changes very clearly and carefully. We will also do as much as possible to automatically confirm that your site can be safely upgraded to the new version.
Upgrades to a new major version which contains potentially breaking changes will always be optional and clearly communicated.
ClassicPress is a democratic community-led fork of WordPress that enables all stakeholders to shape the direction that the project takes. The Democracy page aims to explain how we handle this process to ensure that power doesn’t become centralised and that every voice can be heard; no single person within any group has the power to force through a valid Topic which affects ClassicPress. This ensures that we stay true to our goal of being a community-led fork.
Additional information on our democracy can be found on the ClassicPress Democracy page.
Below are a list of changes which have been made in ClassicPress since the fork from WordPress 4.9.8. These changes will be included in version 1 upon release.
All plugins and themes which work in WordPress 4.9.x, will work in ClassicPress too. If you experience something different, that’s probably a bug with ClassicPress, and we’d appreciate you reporting it on the support forums, Slack, or GitHub.
Plugins which have been tested and confirmed working are listed here.
Yes, you can easily convert a WordPress site to ClassicPress using the Migration Plugin.
To rollback to WordPress, you can download any WordPress version without the wp-content folder (i.e. https://wordpress.org/wordpress-4.9.8-no-content.zip).
To revert to it you simply delete all the files on the server EXCEPT the wp-content folder and the wp-config.php file.
Upload the files from the archive and your site will be back to WP 4.9.8. Please note that if you upload the zip and unpack it on the server it will be in a [wordpress] folder and not the root of your public_html unless you tell it to unpack there.
We are working on a way to automate the rollback.
We’re a team of volunteers working on ClassicPress in our spare time. We’re attempting to change the world on borrowed time and shoestring budgets – any help you can give us will be gratefully received; even just a couple of hours can make a difference.
Promotion of ClassicPress can be done in a variety of ways, including, but not limited to:
That is a great question and the answer is Yes!
We indeed encourage people to send emails or messages via the support forums to the developers of their favourite plugins to ask for ClassicPress compatibility.
Here is an example message. It's best to write in your own words about why you want ClassicPress compatibility, but feel free to use this for inspiration. Be sure to replace the [PLUGIN NAME] and [YOUR NAME] text before sending.
You might already have heard of ClassicPress (https://www.classicpress.net), the hard fork of WordPress 4.9.x.
Version 1 of ClassicPress is stable and production-ready, and all releases in the version 1 series will stay backwards compatible with WP 4.9.x. This means that as long as [PLUGIN NAME] remains compatible with WP 4.9.x, it will be compatible with ClassicPress too.
However, planning is already underway for more changes in ClassicPress v2, including a new plugin directory, and with these changes plugin developers will need to make a commitment to support ClassicPress. There are already a number of developers indicating their willingness to do so, and ClassicPress users are now compiling a list of ClassicPress-friendly plugins which are quickly becoming their preferred options.
This presents a great opportunity for developers to gain access to a whole new market, and as a keen user of [PLUGIN NAME] I would very much like to see it added to that list.
[Insert any specifics about the compatibility of this plugin here. For example: if the plugin has functions related to updates or system files, then explain any changes that need to be made for the plugin to work completely under ClassicPress.]
I'm looking forward to hearing back from you.
Thank you very much,
P.S. In case you didn't know, there is a handy check for ClassicPress that you can use in your plugin:
function_exists( 'classicpress_version' )
Another great way to help ClassicPress users now is to add in your plugin's
readme.txtthat the plugin is compatible with ClassicPress. Many plugin authors have already done this, which makes it very easy for people to search for plugins that support ClassicPress: https://wordpress.org/plugins/search/classicpress/
Plugins and themes should be tagged ClassicPress to allow users to easily find them when searching on the Wordpress.org site or repository via the ClassicPress admin panel.
A number of plugins have already been tagged as compatible with ClassicPress and can easily be found in the WordPress Plugin Repository.
Bugs can be reported on the support forums or, if you know how to write a bug report, via GitHub. If logging via GitHub, please make sure to follow the template instructions:
All current plugins and themes which work in WordPress 4.9.x, will work in ClassicPress v1. If you're experiencing something different, that's probably a bug with ClassicPress, and we'd appreciate you reporting it in the support forums, Slack, or GitHub.
Not unless you want to! ClassicPress is a hard-fork of WordPress 4.9.8 so any plugins or themes developed for WordPress will work on ClassicPress.
We have some exciting features planned for version 2 and beyond, but they will all be optional and fully backwards-compatible.
If you have an issue with ClassicPress that you'd like some help resolving, go to our support forum and make a new topic. Be sure to search existing posts first to make sure your question hasn't already been answered.
If you just have a question or want to chat with us about something, you can join our Slack group.
Please remember that like all of ClassicPress, our support is a volunteer effort by the community. If you are able to help answer support questions in the forum, that is also more than welcome!