I followed the instructions for installing Drupal Module Upgrader and ran the Drush command 'drush dmu-analyze si_publications'. I get the response 'Command dmu-analyze needs the following extension(s) enabled to run: . [error]'. I am not sure why dmu-analyze wouldn't actually specify the extensions it needs enabled instead of an empty string or dot.

I am developing locally on a Windows 10 Enterprise 2016 LTSB Dell laptop using Acquia Dev Desktop. Other drush commands run fine such as drush cc drush, drush cr, and drush status. Any feedback would be appreciated. (i already know that I would rather be developing on a Mac, so you can skip over that piece of advice.)

C:\Users\kochertj.NMNHL-KOCHERT\Sites\devdesktop\module-development-D8>drush status
Drupal version : 8.5.2
Site URI : http://default
Database driver : mysql
Database hostname : 127.0.0.1
Database port : 33067
Database username : drupaluser
Database name : module_development_D8
Database : Connected
Drupal bootstrap : Successful
Drupal user :
Default theme : bartik
Administration theme : seven
PHP executable : php.exe
PHP configuration : "C:\Program Files (x86)\DevDesktop\php7_0\php.ini"
PHP OS : WINNT
Drush script : C:/Program Files (x86)/DevDesktop/tools/vendor/drush/drush/drush.php
Drush version : 8.1.16-dev
Drush temp directory : C:\Users\KOCHER~1.NMN\AppData\Local\Temp
Drush configuration :
Drush alias files :
Install profile : standard
Drupal root : C:\Users\kochertj.NMNHL-KOCHERT\Sites\devdesktop\module-development-D8
Drupal Settings File : sites/default/settings.php
Site path : sites/default
File directory path : sites/default/files
Temporary file directory path : c:\windows\temp

Comments

kochertj created an issue. See original summary.

hongpong’s picture

I don't know too much about php/windows extensions but perhaps you can post a github gist with the list of extensions that are available, or the output of php_info(). I'm assuming it's a php extension that is missing or it can't find. see also #2611204: Install in DevDesktop for Windows? may help

hongpong’s picture

Cpt-Spot’s picture

I had this exact same problem. Running the following commands solved it.
composer update (executed in the drupalmoduleupgrader module folder)
drush cr
drush -y pm-uninstall drupalmoduleupgrader
drush -y pm-enable drupalmoduleupgrader

  • HongPong committed 296a095 on 8.x-1.x
    Updating README.txt. Covers Windows issue #2964747, Drush 9 note #...
hongpong’s picture

Status: Active » Fixed

Thanks Cpt-Spot, you have been credited in the readme :) ... this may have been caused by the out-of-date composer.lock file present in 1.2 which caused a bunch of problems on Windows and was removed for 1.3.

amritendu1980’s picture

when I am running drush dmu-analyze MODULENAME or drush dmu-analyze MODULENAME --path=modules/MODULENAME both command show error " Command "dmu-analyze" is not defined.".

I am using "Drush Commandline Tool 9.3.0" and Drupal 8.5.5 and xampp in my windows machine.

Please can you help to overcome that.

hongpong’s picture

Hi amritendu1980, I believe this is a problem with Drush 9. See #2949601: Drush 9 compatibility . You may be able to get it to work with Drush 8 however (this does actually work on OSX these days I know, not sure about Windows)

amritendu1980’s picture

Issue tags: +_block_view and _block_info hook did not work

Hi HongPong,

Thanks for your valuable feedback. I install Druapl 8.3 and drush 8, it is working fine. But I am facing issue when I am trying to convert D7 module with custom block.

_block_info and _block_view hook. I think this is not work.

Please let me know any solution for that.

hongpong’s picture

hi amritendu1980, please run in verbose mode and post something like a github gist note with the output if you can share.

The module's main author has told me recently really, it is best to interpret the notes of what the converter wants to do, rather than count upon the correct version being output here. (so use it as a guide to change notes from 7, instead of depending on the conversions.

you can also skip block_info and block_view hook and just use the other hooks. that may still give you useful results. best regards!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.