Title: ClassicPress support
Last modified: December 13, 2018

---

# ClassicPress support

 *  [David](https://wordpress.org/support/users/affordablewebsitesdenvercom/)
 * (@affordablewebsitesdenvercom)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/classicpress-support-3/)
 * Can you please respond to requests to support ClassicPress? I noticed all requests
   are being removed very quickly from the repository. Can Mark Maunder respond 
   in any way?

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [zigpress](https://wordpress.org/support/users/zigpress/)
 * (@zigpress)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10983757)
 * +1 for this. It would be great if WordFence would make an official statement 
   about whether they plan to support ClassicPress.
 *  Thread Starter [David](https://wordpress.org/support/users/affordablewebsitesdenvercom/)
 * (@affordablewebsitesdenvercom)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10985846)
 * You should consider getting in touch directly because our post is likely to be
   banned or removed very soon as the other references were and we may be banned
   or removed as well for even mentioning it.
 *  [wfdave](https://wordpress.org/support/users/wfdave/)
 * (@wfdave)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10989546)
 * Hi [@affordablewebsitesdenvercom](https://wordpress.org/support/users/affordablewebsitesdenvercom/),
 * We don’t have the power to remove posts or ban anyone on these forums!
 * As for ClassicPress support, we have been closely monitoring the forums, blog
   post comments, and support tickets. We assure you that all requests have been
   documented.
 * There are no current plans to support ClassicPress at this time, however this
   may change with the influx of forum posts and interest in ClassicPress.
 * We ask for patience and understanding in the meantime!
 * Dave
 *  [Ski_K2](https://wordpress.org/support/users/ski_k2/)
 * (@ski_k2)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10991041)
 * Please support ClassicPress.
 *  [PeterS](https://wordpress.org/support/users/4dtoday/)
 * (@4dtoday)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10994943)
 * We have upgrade a few sites to WP 5 – but still using the Classic Editor. What
   I see from the test sites, we will not switch the next 12 months. The product
   is just too new.
 *  [baterista](https://wordpress.org/support/users/baterista/)
 * (@baterista)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10997104)
 * I would really appreciate that Wordfence would support ClassicPress. WordPress
   5.xx and the way the development is going is no longer an option for me. I tested
   WP 5.0 on a client site which was broken after updating. So I really look forward
   to switch to ClassicPress and I definitely would love to be able using WordFence
   for my projects.
    Please support ClassicPress!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘ClassicPress support’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [Updates](https://wordpress.org/support/topic-tag/updates/)

 * 6 replies
 * 6 participants
 * Last reply from: [baterista](https://wordpress.org/support/users/baterista/)
 * Last activity: [7 years, 4 months ago](https://wordpress.org/support/topic/classicpress-support-3/#post-10997104)
 * Status: not a support question