johnpbloch
commented
7 years ago The issue here is that composer require johnpbloch/wordpress:~4.7.0 doesn't do what it looks like you think it should. It sounds like you'd like it to do this:
- Update composer.json to reflect new requirements
- Run composer update
Unfortunately, that's not what it does. What it does is it updates the composer.json file and then tries to resolve dependencies without changing anything else in the dependency tree, including dependencies of the package you're updating. So the problem stems from the fact that this package is a meta package that requires an identical version of johnpbloch/wordpress-core and the core installer. When you try to update from 4.6.6 to 4.7.0, it still wants to keep 4.6.6 of the wordpress-core package, but the new version of this package says it needs 4.7.0.
You have a few options here:
First, you could edit composer.json manually, changing "johnpbloch/wordpress": "~4.6.0" to "johnpbloch/wordpress": "~4.7.0", then run composer update.
Secondly, you could make a slight change to the commands you run:
composer require --no-update johnpbloch/wordpress:~4.7.0
composer updateThis option is the same as the option above, but doesn't involve manually editing the composer.json file.
Your last option is to migrate away from this package and replace this:
"johnpbloch/wordpress": "~4.7.0"with this:
"johnpbloch/wordpress-core": "~4.7.0",
"johnpbloch/wordpress-core-installer": "^1.0"It sounds like this might not be feasibly right away, since it sounds like some of your other dependencies list johnpbloch/wordpress. Those would need to list johnpbloch/wordpress-core instead before you could migrate away from this package.
dnaber-de
TL;DR You probably want to run
Original issue text:
Since the restructuring of the package I frequently run into issues with composer require or update commands.
If I have for example WordPress installed at 4.6-branch and want to upgrade to 4.7-branch I'd normally do it by the require command:
What I would expect here is, that composer removes the 4.6-package and installs 4.7 instead. Like it does for example with
symfony/console:Tested composer version is 1.4.2, PHP version is 7.0.21 on Ubunut 14.04
It would not that big issue if I'd only had WP as single package because I could remove and require it manually. But as there are several other packages that requires WordPress, I have to remove all of them in the correct order by hand.