Title: PHP8 Status
Last modified: September 17, 2022

---

# PHP8 Status

 *  Resolved [Derek Rippe](https://wordpress.org/support/users/dwrippe/)
 * (@dwrippe)
 * [3 years, 8 months ago](https://wordpress.org/support/topic/php8-status/)
 * What’s the status on PHP8 compatibility?
 * PHP7.4 security support ends in about 2 months, and several hosts are migrating
   to PHP8 on/around that date. I have a site running Simple:Press v6.7.0, which
   doesn’t support PHP8, and I have until November 2, 2022 to either A) get it working,
   or B) find an alternative… which I REALLY don’t want to have to do!

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

 *  Plugin Support [nigel01](https://wordpress.org/support/users/nigel01/)
 * (@nigel01)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16021469)
 * Hi:
 * We’re working on it. Core is almost ready but we have 70+ addons that we have
   to handle before we can release it.
 * Thanks.
 *  Thread Starter [Derek Rippe](https://wordpress.org/support/users/dwrippe/)
 * (@dwrippe)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16023831)
 * Thanks for the update, [@nigel01](https://wordpress.org/support/users/nigel01/).
   Any sense on a timeline?
 * I obviously have a few weeks before any critical issues on my end. I can push
   the client a few weeks past November 2nd if necessary knowing an update is coming,
   but if we’re realistically looking at mid-2023 or something like that, I need
   to start looking for another solution now rather than later.
 *  Plugin Support [nigel01](https://wordpress.org/support/users/nigel01/)
 * (@nigel01)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16032621)
 * If you’re not using any add-ons, you can grab the dev branch from github and 
   use it on php 8.0:
 * [https://github.com/Simple-Press/simple-press/tree/dev](https://github.com/Simple-Press/simple-press/tree/dev)
 * If for some reason you find any issues that show up in 8.x and not in 7.4, please
   log an issue on github here: [https://github.com/Simple-Press/simple-press/issues](https://github.com/Simple-Press/simple-press/issues)
 * Thanks.
 *  [xberg](https://wordpress.org/support/users/xberg/)
 * (@xberg)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16053817)
 * Thank you for the update on PHP 8. I was also getting very worried.
    A timeline
   would indeed be nice. I understand you have 70 add-ons but certainly some are
   more used then others. Perhaps a tiered approach would be acceptable if you think
   it’s going to be a challenge to convert them all before November. Thanks
 *  Plugin Support [nigel01](https://wordpress.org/support/users/nigel01/)
 * (@nigel01)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16056421)
 * Hi:
 * Since you’re not using the premium plugins it probably shouldn’t matter that 
   much for your use case. All you need are the files from the current dev branch
   on github.
 * Here’s a direct link that will download them as a .zip:
 * [https://github.com/Simple-Press/simple-press/archive/refs/heads/dev.zip](https://github.com/Simple-Press/simple-press/archive/refs/heads/dev.zip)
 * Thanks.

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

The topic ‘PHP8 Status’ is closed to new replies.

 * ![](https://ps.w.org/simplepress/assets/icon-256x256.png?rev=2920002)
 * [Simple:Press Forum](https://wordpress.org/plugins/simplepress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/simplepress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/simplepress/)
 * [Active Topics](https://wordpress.org/support/plugin/simplepress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/simplepress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/simplepress/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [nigel01](https://wordpress.org/support/users/nigel01/)
 * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/php8-status/#post-16056421)
 * Status: resolved