At the moment our Frequently Asked Questions page is a work in progress and we apologise for the inconvenience. Feel free to suggest both Questions and Answers via Slack or our Forums.
What will be new/different in ClassicPress V1?
What will be new, improved or different in ClassicPress v1 compared to WordPress v5? This list should represent where we want to be for v1, and not where we currently are with the alpha/beta versions.
No Gutenberg: Keep the editing experience you know and love [complete]
All API communications must happen over SSL [complete]
GPG used on GitHub to sign the tags that publish our releases. This is a first step towards full verification of the contents of a release build, and a more secure approach to updates [complete]
Support for PHP <= 5.5 dropped [complete]
Developer improvements / changes:
Full support of semantic versioning (https://semver.org/) [complete]
All build dependencies updated. This mostly makes it easier for developers working on ClassicPress itself, and also people doing custom builds. [complete]
Git used instead of Subversion for version control [complete]
ClassicPress release on packagist for use with composer (We’re shipping a composer.json file with 1.0.0-beta1, but this feature may need some further refinement.)
Automated nightly builds [complete]
Automated dependancy updates [complete]
New constant LOAD_CONFIG_ONLY which will load wp-config.php without it loading wp-settings.php. Great for allowing external PHP apps (such as automated tools) to load the ClassicPress config (e.g. to get db credentials) without it trying to load all of ClassicPress. It also paves the way for web hosts to decouple wp-config.php from their page load bootstrap process
"Akismet" and "Hello Dolly" plugins removed from the default installation (which are usually the first plugins to be removed for a business website) [complete]
Removal of quirky language such as “Howdy [name]” which doesn’t portray a professional image [complete]
Removal of Dashboard widgets that are not useful for business users (e.g. upcoming WordPress events will be replaced with widgets that allow people to vote on features proposed by the community)
Will WP plugins/themes work with CP?
If your current plugins and themes work in WordPress 4.9.x, they will work in ClassicPress too. If you're seeing something otherwise, that’s probably a bug with ClassicPress, and we'd appreciate you reporting it on Slack, the support forums, or GitHub.
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 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.
What can I do at a local level to help promote ClassicPress?
I just share posts I see on Twitter and suggest also sharing on Facebook. Any social networking platform really. Talk to friends, family and coworkers, mouth to mouth, email. Of course, I will be posting on the pub site where others can also share from and to.
Because I deal with design agencies on a daily basis I have been ‘soft-pressure’ selling the idea that an alternative to WP is coming, pass along information about what CP is all about (vs. the Luddite hype I am hearing from, frankly young, WP aficionados). I am getting positive feedback and setting to be a local resource for what is happening, what works and what is on the roadmap.
Knowledge WILL rule the world!
At a local level, I’ve contacted every one of my clients to let them know of the upcoming changes, as well as posting to my various social media feeds – and offered ClassicPress as a viable solution. I’ve also been in touch with other agency owners in the area to discuss options and how they plan to handle WP changes. I’m also considering doing a workshop with the local Chamber of Commerce after the holiday to help local business owners.
Is there a sample email we can send to plugin developers to ask for ClassicPress compatibility?
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.
The power of the people so to say 🙂
You can adapt the sample below to your wishes and/or needs.
You might already have heard of ClassicPress (https://www.classicpress.net), the hard fork of WordPress 4.9.8. It’s in Beta 1 now and the team is working hard on the first production release, ClassicPress 1.0.0. Version 1 of ClassicPress will always stay backward compatible with WP 4.9.x.
Although I have read that you are working hard to make [PLUGIN_NAME] compatible with the new editor that WP will introduce in version 5.0, I assume (hope) that it also remains compatible with earlier versions of WordPress, such as 4.9.8?
I really hope it is, because as long as your plugin remains compatible with WP 4.9.x, it will also be compatible with version 1.x of ClassicPress.
You probably know this already, but there is even a handy condition that you can use in your plugin:
function_exists( 'classicpress_version' )
And if you want to go even further, you can add somewhere in the plugin's readme.txt that your plugin is compatible with ClassicPress. Once you do, it will be very easy for people to search in the WP Plugins Directory on ClassicPress compatible plugins: https://wordpress.org/plugins/search/classicpress/
Looking forward to hearing from you,
Thank you very much,
Can I convert a WP site to CP – and what if I don’t like it?