• Resolved Steve Borsch

    (@sborsch)


    Wordpress has made it clear that PHP 7 will be the norm in 2017. We manage several dozen sites and are slowly migrating them to PHP 7.1.2 when possible. The PHP Compatibility plugin (by WPEngine) shows that your WP-CRM plugin has the following *serious* warnings.

    Please let me know when you will be updating this plugin for PHP 7+ compatibility.

    FILE: ../wp-content/plugins/wp-crm/lib/class_core.php
    ————————————————————————————————————
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ————————————————————————————————————
    29 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
    ————————————————————————————————————

    FILE: ../wp-content/plugins/wp-crm/lib/class_user_list_table.php
    ———————————————————————————————————————–
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ———————————————————————————————————————–
    65 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
    ———————————————————————————————————————–

    FILE: ../wp-content/plugins/wp-crm/lib/class_contact_messages.php
    ————————————————————————————————————————
    FOUND 2 ERRORS AFFECTING 2 LINES
    ————————————————————————————————————————
    314 | ERROR | Function split() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_split instead
    321 | ERROR | Function split() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_split instead
    ————————————————————————————————————————

    FILE: ../wp-content/plugins/wp-crm/lib/class_ud.php
    ————————————————————————————————————————
    FOUND 10 ERRORS AFFECTING 5 LINES
    ————————————————————————————————————————
    56 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
    56 | ERROR | Function ereg_replace() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_replace instead
    1254 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
    1254 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
    1264 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
    1264 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
    1271 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
    1271 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
    1278 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
    1278 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
    ————————————————————————————————————————

    FILE: ../wp-content/plugins/wp-crm/lib/class_list_table.php
    ——————————————————————————————————————
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ——————————————————————————————————————
    33 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
    ——————————————————————————————————————

    FILE: ../wp-content/plugins/wp-crm/static/scripts/src/l10n.php
    ———————————————————————————————————————–
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ———————————————————————————————————————–
    1 | WARNING | No PHP code was found in this file and short open tags are not allowed by this install of PHP. This file may be using short open tags but PHP does not allow them.
    ———————————————————————————————————————–

    FILE: ../wp-content/plugins/wp-crm/vendor/usabilitydynamics/lib-utility/lib/class-utility.php
    ————————————————————————————————————————
    FOUND 1 ERROR AFFECTING 1 LINE
    ————————————————————————————————————————
    508 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5 and removed since PHP 7.0
    ————————————————————————————————————————

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Hello.

    Thank you for pointing. We will think to fix those warnings, but they are not preventing wp-crm to work. If you will disable debug mode you won’t see them.

    And nothing serious.

    Regards.

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Have not heard from you in some time so just wanted to touch base and see if you had any questions or comments 🙂

    I will mark this ticket as resolved for now.

    Regards.

    Thread Starter Steve Borsch

    (@sborsch)

    Hello Maria,

    After extensive testing with a cloned version of our most important website that uses WP-CRM, we enabled PHP 7.x.

    Turns out we may have been premature since a strange anomaly has appeared: when clicking on any given person we find that most load, but about a dozen do not. When clicking on one of these few users a blank screen appears.

    I’ve cleared all caches. Do you have any other suggestions?

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Hello,Steve.

    Please let me know exact version which you have. I have tested on 7.0.18-1 and didn’t face mentioned issues.

    Also try to disable third party plugins to be sure the issue do not relate to them.

    Regards.

    Thread Starter Steve Borsch

    (@sborsch)

    Maria,

    Am using 1.0.6 current version. Usually a plugin conflict means that there is a consistent, across-the-board rendering issue of some kind but this one is intermittent.

    So far we have discovered roughly 50 records out of hundreds that don’t render. All others do just fine. The ONLY change since this occurred was changing to PHP 7 from 5.6.

    Any other ideas?

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Sorry wasn’t clear. Can you tell me exact version of php which you have?

    Regards.

    Thread Starter Steve Borsch

    (@sborsch)

    Sorry Maria. Using PHP 7.1.4 as FastCGI used by Apache.

    Let me know if you need anything else and thanks for digging in to the issue.

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Ok, we need more details from your site, like errors in console and so on. Can you contact us directly we will check that on your site.
    https://usabilitydynamics.com/contact-us/

    Regards.

    Thread Starter Steve Borsch

    (@sborsch)

    Wanted to publicly thank you, Maria, for all of your assistance and to the developer who fixed this error. Glad to see it will make it in to the next update too!

    I am so appreciative that I am now going to make a donation. Again, thank you!

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

The topic ‘Not compatible with PHP 7.x.x’ is closed to new replies.