Wordfence and ClassicPress

That’s perfect :smile:

Just replied to ZigPress, and added my request for follow-up on the topic from someone there.


Also, here: https://wordpress.org/support/topic/classicpress-support/

AND, it’s been deleted. Link takes you to another post for a different plugin with same title. I think this one is still up because the plugin author replied that he won’t support ClassiPress.

A user representing WordFence has replied on both threads and said he’ll raise it with the team :slight_smile:

1 Like

Great news :slight_smile:

We now have a sample email/message that people can use to send to the developers of their favourite plugins.

It has been added to the online FAQs, but I will paste it here too, that seems easier.

Hi there,

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.x 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,


Love it!

1 Like

glad to hear that you like it :slight_smile:

I am not sure about this part in bold. We are making good progress but there is still a lot to do before v1 final.

Feel free to change it to what you think is more suitable/accurate.


Updated as follows:

It’s in Beta 1 now and the team is working hard on the first production release, ClassicPress 1.0.0.

ok I will adjust the FAQ entry

1 Like

It seems all posts on Wordpress.org that even so much as mention Classicpress, let alone recommend it in any way, are being removed.

This should not surprise anyone.

We need a solid security plugin for CP, as it looks as though Mullenweig/Automattic may be banning any reference to CP in its support forums. All our requests for WordFence support for CP have been removed and Mark Maunder is (so far) not responding to any requests (if he’s even seen them).

All in One Security is my bet if that’s the case.

I’ll reach out to them

1 Like

Hm, their contact form doesn’t work. That alone doesn’t fill me with confidence about their credentials!

WP-Shield or Shield Pro is good too. I use them one of my clients.

Using BPS Pro (commercial but one-off payment for unlimited sites - there is also a free version) and seems fine on three sites I’m running under ClassicPress.

The plugin author seemed willing to look at issues with ClassicPress when I contacted him (see thread and link at https://forums.classicpress.net/t/bulletproof-security-pro-and-classicpress/289