Open jawys opened 2 years ago
@jawys Something is awry, your outlined workflow should work fine (Developer B should be able to craft intall
with a project config and no database).
I'm also unable to reproduce…can supply a set of project config files and composer.json/lock files to reproduce this?
The Calling unknown method: craft\console\Request::getParam()
error is from the SitePickerField
, which is making the installation fail.
Yes I will provide some minimal example. Just have to find the time to prepare something
I’ve noticed a this or a similar / related issue. Plugins that were previously uninstalled (Using Craft uninstall and then Composer remove) will make Craft very angry when trying to install itself on an empty database. (Not all of them, but some early plugins that I had managed with project config I’ve seen this happen.)
It seems like at some point entries for removed plugins didn’t get full excised from project.yaml
and it attempts to install and then just deactivate the plugin (which it cannot do because the plugin code no longer exists in the project) and then process crashes. If I go in and manually delete the entries for the removed plugins in project.yaml
Everything appears to be happy, but just doing a rebuild on project config doesn’t excise the ghost plugins.
Description
At our company we try to achieve the following cross developer experience:
config/project/
changes into gitcraft install
either from console or browserconfig/project/
folderconfig/project/
folderconfig/project/
folderThis happened already quite often in our approach sharing development progress between different team members. Most of the time we see
Exception 'craft\errors\MigrationException' with message 'An error occurred while executing the "craft\migrations\Install migration: Calling unknown method: craft\console\Request::getParam()'
right beforecraft install
is able to finish. See this for the whole console output: https://gist.github.com/jawys/51dc1fc7d773af93a94de9523d0d8b18#file-php_craft_install-log-L445While searching for the origin of the errors trying to make a quickstart for new developers as easy as possible, we started removing plugins to mitigate issues with these. But still, we cannot achieve a frictionless install while sharing only code between devs on different machines. Do we need to share db dumps across us all as well?
Steps to reproduce
plugins:
section fromproject.yaml
craft install
See this:
/admin/install
screenAdditional info