• Resolved gevcen

    (@gevcen)


    I’ve run a compatibility check with PHP 7.3 and found the below errors

    FILE: /home/customer/www/gevcen.be/public_html/wp-content/plugins/health-check/includes/class-health-check-site-status.php
    ————————————————————————————————————————–
    FOUND 2 ERRORS AFFECTING 2 LINES
    ————————————————————————————————————————–
    52 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
    1097 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
    ————————————————————————————————————————–

    FILE: /home/customer/www/gevcen.be/public_html/wp-content/plugins/health-check/includes/class-health-check-debug-data.php
    ————————————————————————————————————————-
    FOUND 1 ERROR AFFECTING 1 LINE
    ————————————————————————————————————————-
    766 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
    ————————————————————————————————————————-

Viewing 3 replies - 1 through 3 (of 3 total)
  • Also WRONG
    mcrypt error
    ‘The required module, mcrypt, is not installed, or has been disabled.‘
    My PHP version is 7.2.13. mcrypt module was deprecated in PHP 7.1, and removed in PHP 7.2.0. As a matter of fact this module was never required in PHP.

    Keep in mind that this plugin has backwards compatible code all the way back to php 5.2.
    Also, read the reply here: https://www.ads-software.com/support/topic/highest-supported-php-5-6/

    Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    As @pidengmor mentioned, the warnings from the original poster are related to backwards compatible code for older WordPress installs. There’s unfortunately no way to avoid them throwing errors when doing a static code analysis.

    As for your remark @companyv, mcrypt isn’t required by PHP; it’s required by WordPress, and should only show up if libsodium (the better alternative) is missing for some reason (this was included in PHP from version 7.2.0 and onwards, as you say, but it is possible to build PHP without it, which some hosts have done in the past, this is why the checks are in place).

    If you believe this latter to be in error, I’d appreciate a new topic to cove it, so as not to hijack the original topic from its creator ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin incompatible with PHP 7.3’ is closed to new replies.