While running a pm-update on the site I receive the following message.

$ drush -l http://www.mysite.local pm-update

Error while trying to find the common path for enabled extensions of project fusion. Extensions are: fusion_core, casablog. [error]

The site is part of a multisite build where the base theme lives in /sites/all/themes/drupal-contrib/fusion and the subtheme is a fusion-starter theme living in /sites/mysite.local/themes/custom/casablog

Don't know if this is a fusion issue, but I don't recall having this issue at all using All-versions-3.1.

The rest of the pm-update seems to run fine, so I'm putting this as a support request. Wondering if this is a bug or if this means if I'm going to need three copies of the base theme on my multisite since the base theme and subtheme must live in a common path. Thanks.

Comments

jonhattan’s picture

Status: Active » Postponed (maintainer needs more info)

It seems to me the same issue as in #745082: Drush pm-updatecode gets really confused by corrupt module / themes

if your fusion subtheme include project=fusion in the .info file you need to remove it.

casaswing’s picture

Thank you. That worked nicely!

greg.1.anderson’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

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

ryan258’s picture

I think this was also a case w/ Omega, but I'm not sure.

Had the same issue, subthemes kicked off an error. Cleared out a bunch of them, checked the remaining one for project= (didn't find it).

Went back to drush and pm-update worked the way it should w/o the error that originally led me to do a search and find this page.

betoaveiga’s picture

Search also for custom modules that have inside the info file the line project, and remove this line. See https://www.drupal.org/docs/7/creating-custom-modules/writing-module-inf...