WP-CLI PHP Requirements Strategy

Up until now, WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. was keeping a very low PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. minimum requirement, to support as many legacy server platforms as possible. As a result, WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ tried to stay as low as possible with its own PHP minimum requirement, within reason. It made sense to not randomly break support for people stuck on lower PHP versions if we could easily avoid it.

WordPress Core is now planning to switch to a different approach for dealing with minimum PHP requirements, as recently announced on the Make/core blog: “Updating the Minimum PHP Version”.

As soon as WordPress Core has moved past WP-CLI in terms of minimum PHP version, we will try to adapt WP-CLI, but with a 1-year delay at the least. This delay is meant to allow site owners to still use WP-CLI to migrate their old sites over to newer servers. One year of additional support should be ample time to work on migrating your server over from an unsupported PHP platform.

After this year, we might raise the minimum as well, or wait for a more strategic moment to do so.

So this will be the guarantee that WP-CLI provides moving forward: Whenever WordPress Core raises the PHP minimum version requirement past WP-CLI, WP-CLI will stay at the old minimum requirement for at least 1 full year.

Given the current plans put forth in the above announcement, and considering the fact that there’s no real benefit to be had for WP-CLI to bump the requirement twice, the preliminary plan is to schedule WP-CLI v3 with PHP 7+ as a minimum requirement for December 2020.

The final announcement for a WP-CLI v3 release date will be done at a later date, probably closer to the end of this year.

#v3-0-0

Installing packages

Here is the debug or part of it:

Updating dependencies

Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165

Debug (packages): composer.json content:

{

    "name": "wp-cli/wp-cli",

    "description": "Installed community packages used by WP-CLI",

    "version": "2.1.0",

    "authors": [

        {

            "name": "WP-CLI",

            "email": "noreply@wpcli.org"

        }

    ],

    "homepage": "https://wp-cli.org/package-index/",

    "require": {

        "wp-cli/admin-command": "dev-master",

        "wp-cli/find-command": "dev-master",

        "aaemnnosttv/wp-cli-login-command": "dev-master"

    },

    "require-dev": {},

    "minimum-stability": "dev",

    "prefer-stable": true,

    "license": "MIT",

    "repositories": {

        "wp-cli": {

            "type": "composer",

            "url": "https://wp-cli.org/package-index/"

        }

    },

    "config": {

        "secure-http": true

    }

}

 (138.509s)

Error: Package installation failed.

Reverted composer.json.

As you see the composer now requires the package it failed to install.

"require": {

        "wp-cli/admin-command": "dev-master",

        "wp-cli/find-command": "dev-master",

        "aaemnnosttv/wp-cli-login-command": "dev-master"

    }

but the install failed.
error: Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165

I tried adding the following code to the “.composer/config.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.” to correct the issue, no luck.

{

  "config": {

    "github-protocols": [

      "https"

    ]

  },

  "repositories": {

    "packagist.org": {

      "type": "composer",

      "url": "https://packagist.org"

    }

  }

}

into the .composer/config.json

Sorry, for bothering you with this but I had no place to turn and I found your profile when searching issues/questions with CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress..

Thanks

Jeremy Ward 6:32 pm on January 15, 2019

Hmm, I feel like the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ and PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. teams have been ahead of the curve of late, but this feels like a regression. Since PHP release have come at an annual basis, this update schedule suggests that a supported version of PHP will never be a minimum requirement for PHP. 7.1 is set to stop receiving updates at the end of 2019, and 7.2 will do so at the end of 2020. I understand that the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team hasn’t made a distinction as to what “7+” means exactly just yet, but this will ensure that WP-CLI’s minimum supported version is always at least 2 years behind PHP EOL.

Since WP-CLI is primarily a developer-facing tool, this seems backward to me. A new release of WordPress that no longer runs on a certain version of PHP would not get upgraded until the environment itself is upgraded. Wouldn’t that suggest that WP-CLI should abide by those same minimums?

Please let me know if I’m overlooking something.
- Alain Schlesser 7:35 pm on January 15, 2019
  
  Hey Jeremy,
  
  WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ is not really a developer-facing tool in the same sense as a framework like Symfony is. The most important task that WP-CLI does is to streamline site management, and I’d position it closer to a DevOps role in that regard. As such, it’s most important asset is that it can run on the server it is meant to manage.
  
  Consider the following scenario: WP raises the minimum PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. version to 7.0. Many people still run sites that use old code and cannot work on 7.0 without major modifications. Often times, they are even looking at a rebuild of the site, as it comes roughly at the same cost as modifying the old one to just work again.
  
  In such a case, they need a tool for migrating the data over once their fresh site is ready to go live. If that tool would only run on the new site, but not on the old anymore, they’d have trouble making that migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies..
  
  I’m still hopeful that, with time, WordPress will be able to just keep rolling with the PHP updates, and then we’ll rediscuss how to handle this with WP-CLI. But for now, bumping the minimum PHP version is a huge and scary deal for your average run-of-the-mill WordPress site, and I want to make sure they can count on WP-CLI to help them get moved over to newer versions of PHP as quickly and as painlessly as possible.
  - Alain Schlesser 7:37 pm on January 15, 2019
    
    I want to add that “a supported version of PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. will never be a minimum requirement ” is a non-issue, really. We’re talking about the minimum supported version here, not the maximum. We’re not forcing anyone to run on an unsupported version. People are always free to run WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ on bleeding-edge PHP versions, and we’ll make sure it works with the newest stable at all times.
    - robguay 8:03 pm on February 17, 2019
      
      Hello:
      First let me say “Awesome Sauce!” I just ran into this yesterday. Wow what a useful tool.
      
      Second, I need guidance, where do I address this issue:
      
      Installing packages
      
      Here is the debug or part of it:
      
      Updating dependencies
      Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165
      Debug (packages): composer.json content: { "name": "wp-cli/wp-cli", "description": "Installed community packages used by WP-CLI", "version": "2.1.0", "authors": [ { "name": "WP-CLI", "email": "noreply@wpcli.org" } ], "homepage": "https://wp-cli.org/package-index/", "require": { "wp-cli/admin-command": "dev-master", "wp-cli/find-command": "dev-master", "aaemnnosttv/wp-cli-login-command": "dev-master" }, "require-dev": {}, "minimum-stability": "dev", "prefer-stable": true, "license": "MIT", "repositories": { "wp-cli": { "type": "composer", "url": "https://wp-cli.org/package-index/" } }, "config": { "secure-http": true } } (138.509s) Error: Package installation failed. Reverted composer.json.
      
      As you see the composer now requires the package it failed to install.
      
      "require": { "wp-cli/admin-command": "dev-master", "wp-cli/find-command": "dev-master", "aaemnnosttv/wp-cli-login-command": "dev-master" }
      but the install failed.
      error: Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165
      
      I tried adding the following code to the “.composer/config.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.” to correct the issue, no luck.
      { "config": { "github-protocols": [ "https" ] }, "repositories": { "packagist.org": { "type": "composer", "url": "https://packagist.org" } } }
      
      into the .composer/config.json
      
      Sorry, for bothering you with this but I had no place to turn and I found your profile when searching issues/questions with CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress..
      
      Thanks
      - Alain Schlesser 3:16 pm on April 20, 2019
        
        For support options, please review http://wp-cli.org/#support
        
        The easiest way to get support is to join us in the #cli channel on the Make WordPress Slack Team.

Welcome to WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/!

Contact

WP-CLI PHP Requirements Strategy

Installing packages

Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165

Welcome to WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/!

Contact

Share this:

Installing packages

Warning: Content-Length mismatch, received 163577 bytes out of the expected 675165