- First commit to issue fork.
i am getting the same error as Bhanu951 above. I have a clean drupal/recommended installation.
by the way, is this the right place to report drush problems?
- Status changed to Postponed: needs info
over 1 year ago 7:45pm 28 March 2023 - πΊπΈUnited States cilefen
No! Drush-specific issues are here: https://github.com/drush-ops/drush/issues
If a commit to Drupal core could fix this then it is ok for this issue to exist here. If not, then I guess it is a Drush bug(?). I am postponing this on that question.
@cilfen - according to drush's issue, the problem is Drupal core...
- π©π°Denmark ressa Copenhagen
As an alternative to doing a full import of all config files, it is also possible to cherry pick the relevant config files, place them in another folder, and do a partial configuration import with this, where config folder in this case is in the root of a Lando installation:
drush config:import --partial --source=/app/config
For more, see Drush issue Config import single command #5146.
- πΊπΈUnited States cilefen
Is this issue more of a support request, or, a duplicate of π Allow an install hook in profiles installing from configuration Needs work ?
- Status changed to Closed: duplicate
over 1 year ago 8:03pm 10 May 2023 - π©π°Denmark ressa Copenhagen
I agree @cilefen, it's the same problem, and the solution is being worked on in the other issue, so closing this issue.
Note: It's not mentioned in the Drupal 8: Install Site From Existing Configuration or anywhere, as far as I have seen, but you need to do these steps for it to work:
- First install a fresh site with plain
drush site:install
- Add
$settings['config_sync_directory'] = '../config/sync';
line in settings.php - THEN you can run
drush site:install --existing-config
If someone has figured out to do it in less steps, that would of course be nice :)
- First install a fresh site with plain