What is ClassicPress?

ClassicPress is a community-led fork of the WordPress content management system that preserves the classic TinyMCE editor as the default option. 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.

What is the difference between ClassicPress and Classic Editor?

ClassicPress is a community-led open source content management system (CMS) that was originally a fork of WordPress.

Classic Editor is the TinyMCE editor, used by WordPress for many years until the introduction of the block-based Gutenberg editor.

Who is ClassicPress for?

ClassicPress is the professonal-quality, 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, group, or individual who wants a powerful, versatile and predictable CMS.

What is your stance on backward compatibility?

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.

You can read all the details on our roadmap.

How does your democracy work?

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.

What is new/different in ClassicPress v1?

Details of the changes in ClassicPress v1 are available in on our forums here. Be sure to also review the Release Notes subforum for additional information.

Will my current plugins and themes work in ClassicPress?

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.

Can I convert a WordPress site to ClassicPress – and what if I don’t like it?

Yes, you can easily convert a WordPress site to ClassicPress using the Migration Plugin.

The rollback process is currently a manual process (below), but we’re working on a way to automate it.

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 you downloaded 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.

I’m a developer, will I need to learn any new language or framework to develop in ClassicPress?

Not unless you want to! We have some exciting features planned for version 2 and beyond, but they will all be optional and fully backwards-compatible.

How can I indicate my plugin/theme is compatible with CP?

Plugins and themes should be tagged ‘ClassicPress’ to allow users to easily find them when searching on the Wordpress.org site or repositories 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.

I think I found a bug – what do I do?

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:

For issues with ClassicPress itself, open an issue here
For issues with the Migration pluginopen an issue here

I need help with something else, what should I do?

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!