Title: Incompatibility with PHP 7.1 Last modified: February 3, 2018 --- # Incompatibility with PHP 7.1 * Resolved [r3p4](https://wordpress.org/support/users/r3p4/) * (@r3p4) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/) * When i tried to use PHP 7.1 my website is down. Here the report from the php compatibiliy plugin : FILE: /home/bleusingqj/www/wp-content/plugins/wordfence/ vendor/wordfence/wf-waf/src/lib/utils.php ————————————————————————————————————————————– FOUND 4 ERRORS AND 4 WARNINGS AFFECTING 6 LINES ————————————————————————————————————————————– 293 | WARNING | Function mcrypt_create_iv() is deprecated since PHP 7.1; Use random_bytes() or OpenSSL instead 293 | WARNING | Extension ‘mcrypt’ is deprecated since PHP 7.1; Use openssl (preferred) or pecl/mcrypt once available instead 293 | WARNING | The constant “MCRYPT_DEV_URANDOM” is deprecated since PHP 7.1 347 | WARNING | INI directive ‘magic_quotes_sybase’ is deprecated since PHP 5.3 and removed since PHP 5.4 842 | ERROR | Global variable ‘$HTTP_RAW_POST_DATA’ is deprecated since PHP 5.6 and removed since PHP 7.0; Use php://input instead 843 | ERROR | Global variable ‘$HTTP_RAW_POST_DATA’ is deprecated since PHP 5.6 and removed since PHP 7.0; Use php://input instead 848 | ERROR | Global variable‘ $HTTP_RAW_POST_DATA’ is deprecated since PHP 5.6 and removed since PHP 7.0; Use php://input instead 851 | ERROR | Global variable ‘$HTTP_RAW_POST_DATA’ is deprecated since PHP 5.6 and removed since PHP 7.0; Use php://input instead ————————————————————————————————————————————– * FILE: /home/bleusingqj/www/wp-content/plugins/wordfence/lib/wfConfig.php ———————————————————————————————————— FOUND 1 ERROR AFFECTING 1 LINE ———————————————————————————————————— 651 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead ———————————————————————————————————— Everything goes back to normal when I come back to php 7.0 Is there a solution Thanks Viewing 6 replies - 1 through 6 (of 6 total) * [mountainguy2](https://wordpress.org/support/users/mountainguy2/) * (@mountainguy2) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9933869) * Wow that does not look good. I’m using PHP 7.0.27, I do tend to upgrade when new PHP available, but I always run the compatibility checker. Will do so and return here with results. Thanks for the heads up. * I tried to scan Wordfence with the PHP Compatibility Checker set to scan for PHP 7.1 (from WPengine) and it skips scanning Wordfence because it’s “too large.”( Any tips on how to get the scan to work?) * But, it appears Compatibility Checker does generate false positives, perhaps try a test site using Wordfence and PHP 7.1, meanwhile it’ll be interesting to see what the Wordfence folks have to say about this. * Out of curiosity, having been burned before by plugin bloat, I checked sizes of Wordfence plugin folders on my systems: * Wordfence 6 folder is 7.62 MB Wordfence 7 folder is 8.54 MB * Disappointing, as in, what in the world are they doing that needs 13% bloat, perhaps all those additional tabs and the whitespace? * MTN - This reply was modified 8 years, 3 months ago by [mountainguy2](https://wordpress.org/support/users/mountainguy2/). * [wfalaa](https://wordpress.org/support/users/wfalaa/) * (@wfalaa) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9945696) * Hi, All of these warnings are false positive, these lines referenced are being used for backwards compatibility, you don’t have to worry about that. * Check these similar posts. ([1](https://wordpress.org/support/topic/php-7-0-7-1-7-2-warnings-and-errors/), [2](https://wordpress.org/support/topic/php-7-2-errors-2/)) * Thanks. * [wfalaa](https://wordpress.org/support/users/wfalaa/) * (@wfalaa) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9945699) * Posted my reply twice by mistake! * Thread Starter [r3p4](https://wordpress.org/support/users/r3p4/) * (@r3p4) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9955683) * Hi, I’m sorry but when i try to update PHP (7.1) my website is down with the following error : Not Implemented GET to / not supported. Additionally, a 501 Not Implemented error was encountered while trying to use an ErrorDocument to handle the request. Everything goes back to normal when I come back to php 7.0 Thanks Rémi * [wfalaa](https://wordpress.org/support/users/wfalaa/) * (@wfalaa) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9956893) * Hi Rémi I’m not sure I can understand how this error is related to Wordfence? I would recommend reporting this issue to your hosting provider and let me know if anything related to Wordfence has been detected. * Thanks. * Thread Starter [r3p4](https://wordpress.org/support/users/r3p4/) * (@r3p4) * [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9964232) * My apologies wfalaa, the problem was caming from my hosting provider. Wordfence works fine with PHP 7.1 and 7.2 Best regards Remi Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Incompatibility with PHP 7.1’ 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 * [PHP7](https://wordpress.org/support/topic-tag/php7/) * 6 replies * 3 participants * Last reply from: [r3p4](https://wordpress.org/support/users/r3p4/) * Last activity: [8 years, 3 months ago](https://wordpress.org/support/topic/incompatibility-with-php-7-1/#post-9964232) * Status: resolved