Skip to main content
17 votes

"Unknown package has no name defined" composer error on upgrade

Very similar to Devin's answer. I came up against this on Friday and I had to follow these steps to resolve this issue. Nuke the vendor folder within the project. rm -rf vendor/ Nuke the composer....
Terry Upton's user avatar
  • 1,894
10 votes

"Unknown package has no name defined" composer error on upgrade

The problem seems to be with parsing vendor/composer/installed.json Once I deleted it - install went well. Even without deleting other files. This one is generated one. You can also simply remove ...
Zebooka's user avatar
  • 201
8 votes
Accepted

Craft install via composer: install to public_html?

You can just rename web/ to public_html/, or move all the files inside web/ into public_html/. (Don’t forget to move the .htaccess and .env files, if the latter.) As long as the location of the ...
Brandon Kelly's user avatar
7 votes
Accepted

"Craft isn't installed yet" error after updating to Craft 3.1

Have you tried running ./craft setup to double check if your setup is correct? If ./craft setup completes successfully ./craft should find the existing installation and complete any required setup. ...
Panos Spiliotis's user avatar
7 votes
Accepted

Your project config YAML files are expecting different versions to be installed

That error occurs when there is a discrepancy between the schema versions listed in your incoming project config YAML, and what’s actually installed. If you have the site installed locally, try ...
Brandon Kelly's user avatar
6 votes
Accepted

How can I install modules with Composer?

Craft Plugins require that a "type":"craft-plugin" property is defined in each composer.json file. Composer refers to this to help manage and install the plugin. Craft Modules do not currently have ...
Mark Notton's user avatar
  • 2,337
6 votes
Accepted

Composer was unable to install the updates

You'll need to remove every required packages besides the plugins you installed and craftcms/cms as well as vlucas/phpdotenv, clear your vendor folder and run composer update again. For whatever ...
Robin Schambach's user avatar
6 votes

Carbon 1 is deprecated - migrate to Carbon 2

To find the culprit, you could run a composer show --tree to see which plugin is using the dependency. So far, I found two plugins using it : rias/craft-contact-form-extensions (1.1.6) solspace/...
Alban Jubert's user avatar
5 votes

Craft 3 Command setup failing

I was just confronted with this too. You most likely need to specify the unixSocket attribute for the MAMP Pro database. Take a look at my problem and solution at Craft CLI RC1 Connectivity Issues ...
Tim Knight's user avatar
  • 1,022
5 votes
Accepted

Craft 3 forgets plugins

Craft 3 knows about available plugins via the vendor/craftcms/plugins.php file, which stores info about all Composer packages that were installed with type: craft-plugin in composer.json. If that ...
Brandon Kelly's user avatar
5 votes

Migrate path from 2 to 3?

The documentation posts this link: Upgrading from Craft 2 Mijingo has a tutorial: Upgrading Craft 2 to Craft 3 There is a hangout on the topic on Straight Up Craft: Migrating a website with plugins ...
Ben Parizek's user avatar
  • 13.5k
5 votes
Accepted

Does composer update make changes to the SQL database

No, running composer update will not – by itself – result in any changes to your database. When you run composer update, all that happens is that Composer downloads updated versions for all your ...
Mats Mikkel Rummelhoff's user avatar
5 votes
Accepted

Can't Install Plugin Via Composer

From looking at your plugin's composer.json file, I think you've got the package name wrong – instead of composer require kgrote/siteutilities you'll probably want composer require kgrote/site-...
Mats Mikkel Rummelhoff's user avatar
5 votes

"Craft isn't installed yet" error after updating to Craft 3.1

You can get this error message even if Craft installation is OK. If you work in MAMP environment and have this error message, check if your PHP and MySQL are available from command line (Terminal). ...
Duško Šobić's user avatar
5 votes

Carbon 1 is deprecated - migrate to Carbon 2

All Solspace plugins use some bit of the Carbon dependency so it's highly likely it might be something like Calendar and/or Freeform triggering this. As of last week, we've updated Freeform 2, ...
Solspace's user avatar
  • 1,410
5 votes

"Unknown package has no name defined" composer error on upgrade

I managed to solve this by running: rm -rf vendor/ rm composer.lock At this point, the error still persisted when running composer update or composer dumpauto but then after running: composer ...
Devin Norgarb's user avatar
5 votes

"Unknown package has no name defined" composer error on upgrade

rm vendor/composer/installed.json composer install Maybe installed.json was generated with composer 2.x and you are trying run it now with composer 1.6 or 1.8. Also maybe update composer it also ...
Sérgio's user avatar
  • 151
5 votes

Monolog Logger error

Anyone still looking for how to fix this, the answer is givin in the link above specifically the comment here: https://github.com/craftcms/cms/issues/13963#issuecomment-1830116976 If you can't run ...
jpwdesigns's user avatar
4 votes

Craft 3 Command setup failing

Nothing worked mentioned here. But after these steps Enable "Allow network access to MySQL" -> "only from this Mac" Save Restart It worked!
Trajektorijus's user avatar
4 votes
Accepted

Copy a Craft 3 site to my local machine (MAMP)

From what I see in your screenshot, it looks like you stumbled upon a Craft 3 installation, in which case neither a Craft nor Public folder exist. Craft 3 specific The public folder is now called ...
Paul's user avatar
  • 6,338
4 votes

Composer require looking to craft/plugins/[plugin] directory but throws runtime error?

I found the real root cause. A internal business plugin which I migrated from Craft 2 to Craft 3 had a composer.json file which required composer/installers and that little bugger was mucking up the ...
Greg Bowne's user avatar
4 votes
Accepted

composer update missing zip extension (ext-zip) on MacOS

The reason seems to be that either the PHP version of the MacOS Catalina update or a version installed via brew do not come bundled with the ext-zip extension. You can verify that by calling php -m ...
Matthias Redl-Mann's user avatar
4 votes
Accepted

PHP version problem when upgrading to Craft CMS 4

The package embed/embed isn't the problem – the newest version supports both PHP 7.4 and 8+. The problem is that you have two plugins that require different versions of that package: newism/craft3-...
MoritzLost's user avatar
  • 11.5k
3 votes
Accepted

Can't update or install plugins locally, macOS

error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version Your local OpenSSL setup is trying to connect with an older, insecure TLS 1.0 protocol, which Github (and a lot of ...
Brad Bell's user avatar
  • 67.5k
3 votes
Accepted

Problem installing plugin via path repository

The article I wrote So You Wanna Make a Craft 3 Plugin? may help you in terms of figuring out how to properly set up a "host" website to run your plugin development from. TL;DR your repo shouldn't ...
andrew.welch's user avatar
  • 11.6k
3 votes

PHP version issue when installing Craft 3 using Composer

You are running PHP 5.6.30 on the command line (read the error message), which you can also verify with php -v. To swap the PHP, you should add the path to your preferred PHP executable to your shell’...
carlcs's user avatar
  • 36.3k
3 votes

What would it take to make Craft composer based?

Better late than never... Craft 3 (released April 2018) is fully Composer compliant!
Lindsey D's user avatar
  • 24k
3 votes
Accepted

Craft 3 composer installation

Have you tried to enter the database information in your .env file? Your password is usually "root" in a MAMP environment.
Marten Brosch's user avatar
3 votes
Accepted

FTP Plugin Not Showing Up

If you FTP up the entire vendor folder, all of the same libraries should be available. Make sure it is properly installed locally, first.
Lindsey D's user avatar
  • 24k
3 votes
Accepted

No index.php file created during install using composer

Your index.php file should be found under the web directory. All of the other files and folders installed by composer are considered to be above the root which is recommended for security reasons. ...
Matt Shearing's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible