can't apply existing project config: No plugin exists with the handle "<...>" #7997

D3strukt0r · 2021-05-31T21:33:52Z

D3strukt0r
May 31, 2021

I hope this is a way to get some help here, otherwise, I'll gladly open an issue instead.

Right now I'm trying to create a blueprint, which can be found here: https://github.com/D3strukt0r/craftcms-blueprint/tree/main/cms

I somehow got my dev environment setup (by running docker-compose -f cms/.docker/docker-compose.dev.postgres.yml up (to file)). But if I try my production compose file (docker-compose -f cms/.docker/docker-compose.prod.postgres.yml up (to file)), I get the error in the title.

I used to have the same issue in my dev environment, but it somehow disappeared after reinstalling the plugins, something I can't do in the production environment, so I'm trying to figure out what is causing this.

If you want to build the image in yourself create a copy of the .env.dist (https://github.com/D3strukt0r/craftcms-blueprint/blob/main/cms/.docker/.env.dist) to .env and enter your user's user id and group id in the corresponding env variables as well as add some license keys to the env variables.

If you're wondering, I'm doing this on Windows 10, using WSL 2 with Ubuntu 20.04, and the whole project is in WSL.

Checking the folder in the container ...

� root@7674eb998769:/var/www# ls -Al
total 2588
-rw-r--r-- 1 www-data www-data    2506 May 31 19:40 composer.json
-rw-r--r-- 1 www-data www-data  363183 May 31 19:40 composer.lock
drwxr-xr-x 1 www-data www-data    4096 May 31 17:27 config
-rwxr-xr-x 1 www-data www-data     773 May 24 14:29 craft
drwxr-xr-x 1 www-data www-data    4096 May 31 17:27 modules
drwxr-xr-x 1 www-data www-data    4096 May 31 17:27 src
drwxr-xr-x 1 www-data www-data    4096 May 31 20:55 storage
drwxr-xr-x 1 www-data www-data    4096 May 31 17:27 templates
drwxr-xr-x 1 www-data www-data    4096 May 31 20:56 vendor
drwxr-xr-x 1 www-data www-data    4096 May 31 17:27 web

... all the necessary files should be there as well as the proper permissions are set.

The install command I used is:

./craft install --language de-CH --site-name 'Blueprint' --site-url \$SITE_URL --username admin --email [email protected] --password 'password'

The full error log is (I momentarily switched to dev settings in the prod environment here, that's why there is more info):

    > <creating the tables, indexes and foreign keys until here were successful>
    > populating the info table ... done
    > can't apply existing project config: No plugin exists with the handle "async-queue".
    > moving config/project/ to storage/config-backups/project-2021-05-31-210138 ... Exception: rename(): The first argument to copy() function cannot be a directory (/var/www/vendor/craftcms/cms/src/migrations/Install.php:1091)
#0 [internal function]: yii\base\ErrorHandler->handleError(2, 'rename(): The f...', '/var/www/vendor...', 1091)
#1 /var/www/vendor/craftcms/cms/src/migrations/Install.php(1091): rename('/var/www/config...', '/var/www/storag...')
#2 /var/www/vendor/craftcms/cms/src/migrations/Install.php(74): craft\migrations\Install->insertDefaultData()
#3 /var/www/vendor/craftcms/cms/src/db/Migration.php(52): craft\migrations\Install->safeUp()
#4 /var/www/vendor/craftcms/cms/src/db/MigrationManager.php(232): craft\db\Migration->up(true)
#5 /var/www/vendor/craftcms/cms/src/console/controllers/InstallController.php(179): craft\db\MigrationManager->migrateUp(Object(craft\migrations\Install))
#6 [internal function]: craft\console\controllers\InstallController->actionCraft()
#7 /var/www/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array)
#8 /var/www/vendor/yiisoft/yii2/base/Controller.php(181): yii\base\InlineAction->runWithParams(Array)
#9 /var/www/vendor/yiisoft/yii2/console/Controller.php(184): yii\base\Controller->runAction('', Array)
#10 /var/www/vendor/craftcms/cms/src/console/Controller.php(192): yii\console\Controller->runAction('', Array)
#11 /var/www/vendor/yiisoft/yii2/base/Module.php(534): craft\console\Controller->runAction('', Array)
#12 /var/www/vendor/yiisoft/yii2/console/Application.php(181): yii\base\Module->runAction('install', Array)
#13 /var/www/vendor/craftcms/cms/src/console/Application.php(89): yii\console\Application->runAction('install', Array)
#14 /var/www/vendor/yiisoft/yii2/console/Application.php(148): craft\console\Application->runAction('install', Array)
#15 /var/www/vendor/yiisoft/yii2/base/Application.php(392): yii\console\Application->handleRequest(Object(craft\console\Request))
#16 /var/www/craft(26): yii\base\Application->run()
#17 {main}
Exception 'craft\errors\MigrationException' with message 'An error occurred while executing the "craft\migrations\Install migration: rename(): The first argument to copy() function cannot be a directory'

in /var/www/vendor/craftcms/cms/src/db/MigrationManager.php:252

Caused by: PHP Warning 'yii\base\ErrorException' with message 'rename(): The first argument to copy() function cannot be a directory'

in /var/www/vendor/craftcms/cms/src/migrations/Install.php:1091

Stack trace:
#0 [internal function]: yii\base\ErrorHandler->handleError(2, 'rename(): The f...', '/var/www/vendor...', 1091)
#1 /var/www/vendor/craftcms/cms/src/migrations/Install.php(1091): rename('/var/www/config...', '/var/www/storag...')
#2 /var/www/vendor/craftcms/cms/src/migrations/Install.php(74): craft\migrations\Install->insertDefaultData()
#3 /var/www/vendor/craftcms/cms/src/db/Migration.php(52): craft\migrations\Install->safeUp()
#4 /var/www/vendor/craftcms/cms/src/db/MigrationManager.php(232): craft\db\Migration->up(true)
#5 /var/www/vendor/craftcms/cms/src/console/controllers/InstallController.php(179): craft\db\MigrationManager->migrateUp(Object(craft\migrations\Install))
#6 [internal function]: craft\console\controllers\InstallController->actionCraft()
#7 /var/www/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array)
#8 /var/www/vendor/yiisoft/yii2/base/Controller.php(181): yii\base\InlineAction->runWithParams(Array)
#9 /var/www/vendor/yiisoft/yii2/console/Controller.php(184): yii\base\Controller->runAction('', Array)
#10 /var/www/vendor/craftcms/cms/src/console/Controller.php(192): yii\console\Controller->runAction('', Array)
#11 /var/www/vendor/yiisoft/yii2/base/Module.php(534): craft\console\Controller->runAction('', Array)
#12 /var/www/vendor/yiisoft/yii2/console/Application.php(181): yii\base\Module->runAction('install', Array)
#13 /var/www/vendor/craftcms/cms/src/console/Application.php(89): yii\console\Application->runAction('install', Array)
#14 /var/www/vendor/yiisoft/yii2/console/Application.php(148): craft\console\Application->runAction('install', Array)
#15 /var/www/vendor/yiisoft/yii2/base/Application.php(392): yii\console\Application->handleRequest(Object(craft\console\Request))
#16 /var/www/craft(26): yii\base\Application->run()
#17 {main}

After having thought the missing composer binary might be the issue, I added the composer binary to the container, but the error persisted.

    > populating the info table ... done
    > can't apply existing project config: No plugin exists with the handle "async-queue".
    > moving config/project/ to storage/config-backups/project-2021-05-31-211848 ... Exception: rename(): The first argument to copy() function cannot be a directory (/var/www/vendor/craftcms/cms/src/migrations/
Install.php:1091)
#0 [internal function]: yii\base\ErrorHandler->handleError()
#1 /var/www/vendor/craftcms/cms/src/migrations/Install.php(1091): rename()
#2 /var/www/vendor/craftcms/cms/src/migrations/Install.php(74): craft\migrations\Install->insertDefaultData()
#3 /var/www/vendor/craftcms/cms/src/db/Migration.php(52): craft\migrations\Install->safeUp()
#4 /var/www/vendor/craftcms/cms/src/db/MigrationManager.php(232): craft\db\Migration->up()
#5 /var/www/vendor/craftcms/cms/src/console/controllers/InstallController.php(179): craft\db\MigrationManager->migrateUp()
#6 [internal function]: craft\console\controllers\InstallController->actionCraft()
#7 /var/www/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array()
#8 /var/www/vendor/yiisoft/yii2/base/Controller.php(181): yii\base\InlineAction->runWithParams()
#9 /var/www/vendor/yiisoft/yii2/console/Controller.php(184): yii\base\Controller->runAction()
#10 /var/www/vendor/craftcms/cms/src/console/Controller.php(192): yii\console\Controller->runAction()
#11 /var/www/vendor/yiisoft/yii2/base/Module.php(534): craft\console\Controller->runAction()
#12 /var/www/vendor/yiisoft/yii2/console/Application.php(181): yii\base\Module->runAction()
#13 /var/www/vendor/craftcms/cms/src/console/Application.php(89): yii\console\Application->runAction()
#14 /var/www/vendor/yiisoft/yii2/console/Application.php(148): craft\console\Application->runAction()
#15 /var/www/vendor/yiisoft/yii2/base/Application.php(392): yii\console\Application->handleRequest()
#16 /var/www/craft(26): yii\base\Application->run()
#17 {main}
Exception 'craft\errors\MigrationException' with message 'An error occurred while executing the "craft\migrations\Install migration: rename(): The first argument to copy() function cannot be a directory'

in /var/www/vendor/craftcms/cms/src/db/MigrationManager.php:252

Caused by: PHP Warning 'yii\base\ErrorException' with message 'rename(): The first argument to copy() function cannot be a directory'

in /var/www/vendor/craftcms/cms/src/migrations/Install.php:1091

Stack trace:
#0 [internal function]: yii\base\ErrorHandler->handleError()
#1 /var/www/vendor/craftcms/cms/src/migrations/Install.php(1091): rename()
#2 /var/www/vendor/craftcms/cms/src/migrations/Install.php(74): craft\migrations\Install->insertDefaultData()
#3 /var/www/vendor/craftcms/cms/src/db/Migration.php(52): craft\migrations\Install->safeUp()
#4 /var/www/vendor/craftcms/cms/src/db/MigrationManager.php(232): craft\db\Migration->up()
#5 /var/www/vendor/craftcms/cms/src/console/controllers/InstallController.php(179): craft\db\MigrationManager->migrateUp()
#6 [internal function]: craft\console\controllers\InstallController->actionCraft()
#7 /var/www/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array()
#8 /var/www/vendor/yiisoft/yii2/base/Controller.php(181): yii\base\InlineAction->runWithParams()
#9 /var/www/vendor/yiisoft/yii2/console/Controller.php(184): yii\base\Controller->runAction()
#10 /var/www/vendor/craftcms/cms/src/console/Controller.php(192): yii\console\Controller->runAction()
#11 /var/www/vendor/yiisoft/yii2/base/Module.php(534): craft\console\Controller->runAction()
#12 /var/www/vendor/yiisoft/yii2/console/Application.php(181): yii\base\Module->runAction()
#13 /var/www/vendor/craftcms/cms/src/console/Application.php(89): yii\console\Application->runAction()
#14 /var/www/vendor/yiisoft/yii2/console/Application.php(148): craft\console\Application->runAction()
#15 /var/www/vendor/yiisoft/yii2/base/Application.php(392): yii\console\Application->handleRequest()
#16 /var/www/craft(26): yii\base\Application->run()
#17 {main}

Maybe someone who has a better understanding of this process could help me understand what is going on here because I'm lost as to what I'm doing wrong. Thanks in advance.

Answered by brandonkelly

Jun 1, 2021

For Craft to be able to use the existing project config files during installation, the installed version of Craft and plugins must be identical to what they were on the environment where the project config files came from, at the time they were exported.

Try doing this:

Go back to the original environment and run php craft project-config/rebuild
Now copy its project config files, composer.json and composer.lock over to a new project.
Run composer install on the new project
Run php craft install on the new project

If it still doesn’t pull in the project config files, please send a database backup from your original install, and your Composer files over to [email protected], and we can…

View full answer

brandonkelly · 2021-06-01T17:03:30Z

brandonkelly
Jun 1, 2021
Maintainer

For Craft to be able to use the existing project config files during installation, the installed version of Craft and plugins must be identical to what they were on the environment where the project config files came from, at the time they were exported.

Try doing this:

Go back to the original environment and run php craft project-config/rebuild
Now copy its project config files, composer.json and composer.lock over to a new project.
Run composer install on the new project
Run php craft install on the new project

If it still doesn’t pull in the project config files, please send a database backup from your original install, and your Composer files over to [email protected], and we can try to reproduce it on our end.

3 replies

D3strukt0r Jun 2, 2021
Author

Thanks for the help, but that ./craft project-config/rebuild didn't do much. It's also something many others on Stackoverflow suggested, so I kind of knew of that,

HOWEVER, I found the culprit anyways. It's also something that's documented NOWHERE (so please maybe add it to the website docs, like under a section "How to use composer install for production and development environments")

I used to have the following composer installs
Prod: composer install --prefer-dist --no-dev --no-scripts --no-progress --optimize-autoloader --no-interaction --no-plugins
Dev: composer install --prefer-dist --no-scripts --no-progress --optimize-autoloader --no-interaction --no-plugins

The issue was the --no-plugins. Once I removed it, I could finally run the install. I still don't understand what Composer Plugins are needed for, because that shouldn't have anything to do with Craft Plugins, but in the end, I don't really know. What I know is not to use it. I still find it weird that it worked on my Dev environment though.

So my commands are now:
Prod: composer install --no-dev --no-scripts --no-progress --optimize-autoloader --no-interaction
Dev: composer install --no-scripts --no-progress --no-interaction

brandonkelly Jun 4, 2021
Maintainer

@D3strukt0r Glad you got it sorted!

Craft has its own Composer plugin that is responsible for identifying which Composer dependencies are Craft plugins, and populating the vendor/craftcms/plugins.php file. So you should never be passing --no-plugins when working with Craft. We’ll discuss internally whether that’s worth documenting.

mattstein Jun 24, 2021

@D3strukt0r We added a warning about --no-plugins to the Deployment Best Practices Knowledge Base article. Thanks for bringing this up!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

can't apply existing project config: No plugin exists with the handle "<...>" #7997

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

can't apply existing project config: No plugin exists with the handle "<...>" #7997

D3strukt0r May 31, 2021

Replies: 1 comment · 3 replies

brandonkelly Jun 1, 2021 Maintainer

D3strukt0r Jun 2, 2021 Author

brandonkelly Jun 4, 2021 Maintainer

mattstein Jun 24, 2021

D3strukt0r
May 31, 2021

Replies: 1 comment 3 replies

brandonkelly
Jun 1, 2021
Maintainer

D3strukt0r Jun 2, 2021
Author

brandonkelly Jun 4, 2021
Maintainer