Skip to main content
7 events
when toggle format what by license comment
Oct 12, 2015 at 14:06 comment added greg_1_anderson Okay, next run your Drush make command with the --show-invoke flag. This will cause Drush to print out all of the commandfile hooks for the make command. You must have this right if your hook is being called sometimes, I would imagine, so this is a difficult question. If your commandfile is listed in the commandfile list, then it should be called for all of the valid hooks that Drush invokes.
Oct 12, 2015 at 12:28 comment added Pan Chrono That was useful. From both ends I get the same array containing my extension from /home/<user>/.drush/<extension>, drushify, and also the core extensions from /usr/share/drush/commands. Weird stuff - I can also verify that if I execute my drush-make from a bash alias, it will work (!) but still not working from the script :(
Oct 9, 2015 at 16:31 comment added greg_1_anderson Run drush ev 'return drush_commandfile_list();' and see if it includes your commandfile. Also, you should do these operations both from the command line and from your script, and look for any variations in behavior.
Oct 9, 2015 at 12:17 comment added Pan Chrono Project drushify (7.x-1.0) downloaded to /home/<user>/.drush/drushify.Same location as my extension, I can see drushify help from that location..
Oct 5, 2015 at 14:34 comment added greg_1_anderson Does your Drush extension, or any Drush extension in the same directory, define any Drush commands? Put drush help commandname in your script, and see if Drush is finding the commandfile. If you don't have any commands, just download one, e.g. drush dl drushify
Oct 5, 2015 at 7:56 comment added Pan Chrono Thanks, $HOME var points to the correct location, also if I echo it from the script I get the correct location...what else to look for?
Oct 2, 2015 at 15:06 history answered greg_1_anderson CC BY-SA 3.0