FAQ and Support

What is new/different in ClassicPress v1?Link to this section

Details of the changes in ClassicPress v1 are available in on our forums.

Will my current plugins and themes work in ClassicPress?Link to this section

Yes, however it is generally suggested to use alternatives programmed specifically for ClassicPress.

All WordPress Themes or Plugins that are requiring a WordPress Version: 4.9 or lower will generally work in ClassicPress Version 1 and above.
WordPress Plugins or Themes explicitly requiring Wordpress Version: 5.0 or higher will not work with ClassicPress, and should not be used.
If you’re experiencing something different, we’d appreciate you reporting it in the support forums, Slack, or GitHub.

You can find out if a Theme or Plugin officially still supports WordPress Version 4.9, by navigating to said Plugin or Theme page in the WordPress Repositories and look for the WordPress Version information in the right hand sidebar. Additionally, a Plugin or Theme Developer might decide to explicitly support ClassicPress. In those cases, the Developer will tag their Software with ClassicPress. You can find all Plugins currently tagged with ClassicPress on this list or the ClassicPress Plugin Directory.

This is how you can see on the single WordPress Theme or Plugin Repository page, wether the software is explicitly compatible with ClassicPress, or works with WordPress 4.9, or does not work with WordPress 4.9 and thus also will not work with ClassicPress.

An Incompatible WordPress Theme

An Incompatible WordPress Theme

A ClassicPress Compatible Plugin

A ClassicPress Compatible Plugin

If in doubt, always contact the Plugin Developers and ask if they plan to support WordPress 4.9 for the time to come, or if they perhaps would be interested in explicitly Support ClassicPress. Tell them about the available Tag in the WordPress repo, and also about the ClassicPress Plugin directory, so they can – if they want – promote their plugin or theme to a broader public.

There have also been a few occasions where a plugin update has broken compatibility with both WordPress 4.9.x and ClassicPress without prior notice, either by decision of the Developers, or by accident.
Whatever the case may be, you should contact the plugin developers and ask them if they could maintain compatibility, but you cannot expect them to do so. It is everyone’s own decision what versions to support with their Plugins or Themes. If you are not 100% sure about the plans of a Plugin or Theme Developer, or fear the minimal version required might just be 4.9 by accident, always try to confirm with the Developers their plans. And, start looking for alternatives, as listed below, or on the ClassicPress Plugin Repository, so you do not risk a bad surprise in future.

The best thing to do, if you have the capacity and motivation, is to develop a new Plugin or Theme designated for ClassicPress, that covers the things your favourite software until now did. Of course, this is a huge amount of work and usually suitable only for experienced Developers. But at ClassicPress we have a thriving and eager to help community, thus feel free to join our Forums and ask for suggestions or help, if your favourite plugin or theme isn’t working with the best CMS there is. It might just be that an avid Developer is around and ready to work on a fork of the original or develop a new software.


Note that ClassicPress already provides some alternatives for major Plugins such as WooCommerce, or Yoast SEO. If you switch to ClassicPress, you will want to have a look at these Plugins. You can find them either in the ClassicPress Plugin Directory or consult below replacement list:

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

We think the best thing you can do as a developer is to be open to learn new skills when they are a clear benefit for your work. However, ClassicPress and its plugin ecosystem will continue to be based primarily on PHP, MySQL and the rest of the proven technologies that have worked so well in the “classic” WordPress ecosystem for many years now.

We recommend that all developers learn how to use git and GitHub, because we believe these technologies are the best way to share and organize your code, including collaborative work with other developers. We make heavy use of git and GitHub for our plugin directory.

How can I indicate my plugin/theme is compatible with CP?Link to this section

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?Link to this section

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:

I need help with something else, what should I do?Link to this section

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!