I tried to upgrade from Libraries 1.0 to 2.2 because a module needed that version. The only related issue I found was https://drupal.org/node/1844632 so I tried the suggestions in that post. Did not help.

Finally I disabled, uninstalled and physically removed all modules, including Libraries 1.0 (all using drush). Then downloaded and enabled libraries again.

Running drush up gave me immediately the message Error while trying to find the common path for enabled extensions of project libraries. Extensions are: libraries, libraries_test_module.

Which is kind of weird as I just installed the latest Libraries...
Also weird is that I don see Libraries listed as module (it showed up when version 1.0 was still there) after running drush up.

I checked all permissions, but now I'm running out of ideas. Any suggestions?

Comments

marcelgalema’s picture

Status: Active » Closed (works as designed)

As it turned out, there were two libraries.info files: one in sites/all/modules/libraries and one in sites/all/modules/contrib/libraries. Don know it got mixed up, but after cleaning up all is fine again :-)

pkosenko’s picture

I had this same issue with the admin_menu module when I tried to reconfigure a site. It seems that in the old site the admin_menu module had all of its files and folders installed in the top level of the modules folder (go figure). Then they all got installed inside the "admin_menu" folder. But I did not notice that there were duplicate "admin_devel" and "admin_menu_toolbar" folder both INSIDE and OUTSIDE the "admin_menu" folder. And I had forgot to remove the ones in the top level module folder.

So when I got a Drush error "Error while trying to find the common path for enabled extensions of project admin_menu. Extensions are: admin_devel, admin_menu, admin_menu_toolbar", Drush was TRYING to tell me that there was more than one copy of a module (and module info file).

So look for duplicate module folders when you get this error.

The other strange thing is that this did not effect the operation of the site, which apparently uses the ONE module path in the system table of the database, I guess.