Timeline for Composer was unable to install the updates. Error: Unknown package has no name defined
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2022 at 21:24 | comment | added | cannon303 | Update: I followed these instructions and it generated a different error. However when I tried to log back in it gave me the option to upgrade the database and once that happened everything was up to date: craftcms.stackexchange.com/questions/36551/… | |
| Aug 8, 2022 at 20:47 | comment | added | cannon303 | After installing the website locally and getting it to work (which was fun). I followed the instructions, I deleted the vendor folder and composer.lock, ran composer install (no errors), ran php craft update all, it said performing 1 update : - craft 3.1.18 => 3.7.50 (CRITICAL), all good then ran it and same error: error: Unknown package has no name defined ([{"name":"adigital\/cookie-consent-banner".... so still not working! | |
| Aug 4, 2022 at 14:54 | comment | added | MoritzLost |
@CraftQuest With a standard install based on the starter project, composer update will not update Craft or any plugins though, since the version constraints are pinned to exact versions. Same goes if you've previously used php craft update all, since that command pins specific versions as well. I like having fixed versions for Craft and plugins and using php craft update all, because it performs migrations in the same step. This way, I can use composer update to update all packages except Craft and plugins and I can be sure I'm not missing any migrations.
|
|
| Aug 4, 2022 at 14:43 | comment | added | CraftQuest |
One note: you shouldn't mix using composer update and craft update/all because of how Craft pins your versions in composer.json. Pick one way and always use it. I like composer update, followed by craft migrate/all.
|
|
| Aug 4, 2022 at 13:00 | history | answered | MoritzLost | CC BY-SA 4.0 |