So, I'm running a D7 site with composer manager. I have successfully run the composer install command from inside the /sites/default/files/composer directory. The libraries appear to be successfully installed, but my watchdog is loaded with RuntimeException: Autoloader not found: /var/www/html/psrlivetoupdate/sites/all/vendor/autoload.php in composer_manager_register_autoloader() (line 173 of /var/www/html/psrlivetoupdate/sites/all/modules/composer_manager/composer_manager.module). and there's also a notice in the site's status report that composer's dependencies haven't been installed. Any idea what's going on and or how to address it?

1 Answer 1


So, this is something that is a little bit wonky in the user interface for composer manager. The file path to where the autoloader should be gets generated automatically in reference to the drupal root of where you configure composer. If your live and development environments have different doc roots, as is likely with a shared host (e.g. /var/www/html/mysite vs /yourhost/public_html/blahblah, your path will be different and drupal won't know where to look. To solve this problem you have to modify the composer manager file directory variable to reflect where the file actually is. You can't change this through composer manager's settings tab, because it will generate a site error that prevents navigating to the tab and editing it there. You can most easily edit this variable with the devel module's variable editor function.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.