This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 645
Drupal instance is reinstalled on provision when default language is not english #1399
Comments
Yikes! if no one gets to it before I can have a look during the weekend. Thanks for the great report! |
Eek, never thought of it, and I'm mildly surprised you're the first person to run into this! |
Looking at https://github.com/drush-ops/drush/blob/8.1.11/commands/core/core.drush.inc#L592, to update the |
Yes, that's apparently the case. I tested your fix locally and opened up a PR upstream. |
Fixed by pulling in the latest Drupal role. Thanks for reporting, and thanks SO much to @oxyc for knocking out the past five or so bugs :) |
kentr
pushed a commit
to kentr/drupal-vm
that referenced
this issue
Jun 9, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type
Your Environment
Your OS
Summary
When doing
vagrant provision
on a drupal-vm where Drupal instance is already installed and using another default language than english, the Drupal instance is re-installed.We can find the source of the error in
provisioning/roles/geerlingguy.drupal/tasks/install-site.yml
:This is because the test
when: "'Successful' not in drupal_site_installed.stdout"
is wrong as the commanddrush status bootstrap
does not return "Successful" but the translated corresponding string when english is not the default language of the drupal instance.The text was updated successfully, but these errors were encountered: