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.
When running master-execute against a Pantheon site, I receive the following error:
"Error: Call to undefined function drush_get_named_extensions_list()"
Pantheon uses Drush 5.10.1. On another environment running Drush 6.4.0 the command runs without error. Also, using the last master release (7.x-2.0-beta3) there are no errors on either environment. Is the most recent release incompatible with older versions of Drush?
Comments
Comment #1
derhasi CreditAttribution: derhasi commenteddrush_get_named_extensions_list() was introduced in Drush 6. Could you work around the issue?
Comment #2
chasingmaxwell CreditAttribution: chasingmaxwell commentedI'm not sure how I would. Right now we'll have to stick to beta3 until Pantheon updates to a newer version of drush.
Comment #3
milos.kroulik CreditAttribution: milos.kroulik commentedComment #4
a.milkovskyI have the same issue. Drush Version : 6.5.0
Comment #5
johnennew CreditAttribution: johnennew commentedOddly I found this happened when I had not downloaded a dependant module to one which was referenced in my master config for the environment.
So master config required views to be enabled in an environment, views requires ctools but I had not downloaded ctools module and ctools module was not listed in the mater config as required in the environment.
After downloading ctools this error went away.
I was also using Drush 6.5.0
Comment #6
samueljmurray CreditAttribution: samueljmurray commentedI'm having the same problem with Drush 6.5.0.
There doesn't seem to be any dependencies that aren't downloaded, so the fix that worked for @ceng hasn't worked for me.
Downgrading to 2.0-beta3 for now.
Comment #7
mike.davis CreditAttribution: mike.davis at Deeson commentedI've had the same problem and I am using Drush version: 7.0, but it seems to only be a problem when I am building a new site and so have downloaded my default set of modules and then run master-exec to enable them all.
Seeing @ceng's comment I did some testing between the beta3 version and the beta4 version.
Building a site using the beta4 version failed with the error, whereas building a site using the 7.x-2.0-beta3 version this all worked fine. I had a look through the list of modules that were being enabled (when using the beta3 version) and noticed that there were 2 modules that were being downloaded and enabled as they were dependancies but I hadn't downloaded them.
I added these 2 modules to by default list of modules and built a new site using the beta4 version of the master module and this all worked fine, so it does seem to be due to certain dependancy modules having not been downloaded.