First, 8.x is a very different beast and will need an entirely different patch -- it's not solved there, it's a regression in D8 that I will file. In D7, however, this is an easy documentation fix that I deem major cos if someone accidentally pretties the code here by adding $module_list = array() here then git deploy is screwed.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | drupal-update-loophole-2062763-3.patch | 1.19 KB | darren oh |
Comments
Comment #1
chx commentedComment #2
chx commentedComment #3
darren ohIt is also necessary to load the modules in
$module_list. Otherwise, hacks are required such as adding an empty bootstrap hook to the module or loading the module in settings.php.Comment #4
drzraf commentedsettings$GLOBALS['module_list']in settings.php does not seem to work (anymore ?), tested with Drupal 7.35the workaround still does work
(drush just didn't modified the info file because it aborted with an error because it failed to add the module as a git submodule)
sorry for the noise
Comment #5
darren ohI've created a pull request to get the same workaround supported by drush.
Comment #6
darren ohComment #7
darren ohFound a fix that does not require a core patch.
Comment #8
darren ohComment #10
darren ohNew pull request for Drush: https://github.com/drush-ops/drush/pull/4397