Why not check for PHP 5.6?

  • Resolved tnrogers

    (@tnrogers)


    8 years, 4 months ago

    I am setting up a WooCommerce store which says I should be running PHP 5.6. But that’s not included in the list to check. It includes PHP 5.3, PHP 5.4, PHP 5.5, and then skips to PHP 7.0.

    I ran it, checking for 7.0, and found that many plugins I have installed would be incompatible, and it could not figure out a few including WooCommerce, and the Avada theme which is one of the top selling WordPress themes, and Fusion Core which runs the Avada theme (the report says “The plugin/theme was skipped as it was too large to scan before the server killed the process.”).

    It also found that UpdraftPlus would not work which is a very popular backup/restore plugin.

    So that’s a no go on PHP 7, but what I really need to know is if they will work with 5.6?

    I ended up checking for 5.5 compatibility, and that showed better results, but still was not able to check on the larger files.

    https://www.ads-software.com/plugins/php-compatibility-checker/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Taylor McCaslin

    (@taylor4484)

    Howdy Tnrogers,

    We leverage an third party open source library to back the PHP version checking in this plugin which you can see here, which unfortuantely does not have PHP 5.6 support.
    https://github.com/wimg/PHPCompatibility

    While 5.6 is currently the recommended minimum version for WordPress, the development community has largely forgone updating projects for PHP 5.6 support because it is an incremental release with incremental performance gains and will only be officially supported through 2016. PHP 7 is a major project release with substantial performance improvements, new features, and has a lengthy official support life through 2017. WP Engine is putting our focus on the future and encouraging our customers to move directly to PHP 7.

    While some plugins may state PHP 5.6 as a minimum version, we have not yet seen any issues with customers running those plugins on PHP 5.5. In many cases, if plugins are correctly hooking into WordPress, many will get backwards compatibility thanks to the backwards compatibility of WordPress.

    Hi Taylor,

    PHPCompatibility in fact does support PHP 5.6 – I’m not really sure why it wouldn’t. There’s even a 5.6 tag (https://github.com/wimg/PHPCompatibility/tree/5.6) and a 5.6 release (https://github.com/wimg/PHPCompatibility/releases)

    Wim

    Plugin Contributor Taylor McCaslin

    (@taylor4484)

    Hey Wim,

    Not sure how we missed that. I’ll chat with my engineers, we’re currently working on an update with your recent patches which should help with some of the false positives we’ve been seeing. We’ll check on adding support for 5.6 as it has been something we’ve been asked about for the plugin.

    Hi Taylor,
    Thanks to a lot of recent additions by one of WordPress’s key community members (Juliette Reinders Folmer), we have tons of new checks as well as fewer false positives and a close to 100% unit test coverage on the sniffs.
    Wim

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Why not check for PHP 5.6?’ is closed to new replies.

Tags