Support » Plugin: Cloudflare » PHP 7.2.5 error, no access to settings

  • George

    (@quantum_leap)



    I am hosted on Siteground and when PHP 7.2.5 is activated, I don’t have access to settings and getting a no access message at the bottom. PHP 7.1.17 works fine.

Viewing 2 replies - 1 through 2 (of 2 total)
  • 7.2 has some significant depreciations, and cloudflare hasn’t modified it. Will be especially important when security updates stop in dec 2018.

    vendor/cloudflare/cloudflare-plugin-backend/src/SecurityUtil.php
    ——————————————————————————————————————————————————
    FOUND 2 ERRORS AFFECTING 1 LINE
    ——————————————————————————————————————————————————
    16 | ERROR | Function mcrypt_create_iv() is deprecated since PHP 7.1 and removed since PHP 7.2; Use random_bytes() or OpenSSL instead
    16 | ERROR | Extension ‘mcrypt’ is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
    ——————————————————————————————————————————————————

    vendor/symfony/yaml/Parser.php
    ——————————————————————————————————————–
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ——————————————————————————————————————–
    76 | WARNING | INI directive ‘mbstring.func_overload’ is deprecated since PHP 7.2
    ——————————————————————————————————————–

    vendor/symfony/yaml/Inline.php
    ——————————————————————————————————————–
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ——————————————————————————————————————–
    55 | WARNING | INI directive ‘mbstring.func_overload’ is deprecated since PHP 7.2
    ——————————————————————————————————————–

    looks like the mcrypt stuff is okay, but perhaps something else is relying on this warning code:

    mbstring.func_overload

    ie
    vendor/symfony/yaml/Parser.php
    and
    vendor/symfony/yaml/Inline.php

    if (2 /* MB_OVERLOAD_STRING */ & (int) ini_get('mbstring.func_overload')) {
       $mbEncoding = mb_internal_encoding();
       mb_internal_encoding('UTF-8');
    }

    Might be expected to be working…and they wont be. So..i don;t know, but probably important for developers to comment on here.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.