Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It appears in:
commands/core/drupal/site_install.inc that:
'update_status_module' => array(
1 => TRUE,
2 => TRUE,
),
Why not have it default to TRUE, but allow a option to turn these off. Suggestions include:
--update_status_module=1,2
or:
--update_status_module_enable=FALSE
--update_status_module_email=FALSE
Open to suggestions. Can create a patch if needed.
Comments
Comment #1
greg.1.anderson CreditAttribution: greg.1.anderson commentedWouldn't it meet your requirements to just run
drush dis update
after the site install completes?Comment #2
Paul Kim Consulting CreditAttribution: Paul Kim Consulting commentedThat could work. However, there are sometimes very strict requirements around a new install talking to anything on the internet. Drush seems to segment fault when the update module can't talk to updates.drupal.org during installation of the update module. This is what I'm seeing when talking to updates.drupal.org is disabled (by firewall?):
This is what i'm seeing when there is no restriction in place:
Comment #3
greg.1.anderson CreditAttribution: greg.1.anderson commentedThis issue was marked
closed (won't fix)
because Drush has moved to Github.If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to
closed (duplicate)
.Please ask support questions on Drupal Answers.
Comment #3.0
greg.1.anderson CreditAttribution: greg.1.anderson commentedFix typo.
Comment #4
kenorb CreditAttribution: kenorb commentedPossible workaround:
drush site-install foo_profile install_configure_form.update_status_module='array(FALSE,FALSE)'
This also can be overridden in hook_form_FORM_ID_alter, like: