Hey Jeroen I got it all sorted out. I think I figured out what I did. I was using the instructions on https://github.com/JeroenDeDauw/ExtensionInstaller/blob/master/README.md. The default contents of the json file specifies nothing should be installed, and looks as follows: { "require": { "php": ">=5.3.2" } } When actually the example json file contains: { "require": { "php": ">=5.3.2" }, "config": { "vendor-dir": "../../vendor" }, "extra": { "installer-paths": { "../../extensions/{$name}": ["type:mediawiki-extension"] } } } Then dumb me skipped the step, "Copy the example.json file" which contained the paths for the installation of /vender and /extensions because I focused on the statement, "The default contents of the json file specifies nothing should be installed, and looks as follows:" and nothing else. :) So a quick question, on our production server, we don't use w/. Which would mean, "vendor-dir": "../../vendor" should become "vendor-dir": "../vendor" and the same for ../../extensions, loose the proceeding ../ And will this: if ( is_readable( __DIR__ . '/../../vendor/autoload.php' ) ) { include_once( __DIR__ . '/../../vendor/autoload.php' ); } will have to be changed to if ( is_readable( __DIR__ . '/../vendor/autoload.php' ) ) { include_once( __DIR__ . '/../vendor/autoload.php' ); } for ExtensionInstaller to work because we are only going up one directory since w/ doesn't exist? Maybe serendipity was telling me to throw everything into the /ExtensionInstaller directory because I'll have to edit .htaccess to allow direct calls to /vender through.... Ugh! Take care Tom