Show only involved extensions if failed to obtain the common path for a project's extensions [#1532166]

I've been using drush without incident to manage module updates on a multi-site install with several active subthemes, but after upgrading drush, I now get errors regarding a couple of themes - one of which isn't even sub-themed:

Error while trying to find the common path for enabled extensions of project genesis. Extensions are: aaa_update_test, [error]
actions_loop_test, advanced_help, aggregator, aggregator_test, ajax_forms_test, ajax_test, batch_test, bbb_update_test,
biblio, biblio_bibtex, biblio_citeproc, biblio_crossref, biblio_marc, biblio_pm, biblio_ris, biblio_rtf, biblio_tagged.....

And the module updates don't seem to be taking place. I did search the error, but since genesis isn't subthemes or even used, none of the solutions seem to apply. Any advice would be appreciated!

Comments

Comment #1

agerard CreditAttribution: agerard commented 13 April 2012 at 16:35

more info: after rolling back to 4.5, I do notice the same types of theme errors for some of the sub-sites (oddly, not the same ones that caused them with 5.1) but they don't stop the module update process.

Comment #2

stephenplatz CreditAttribution: stephenplatz commented 24 April 2012 at 18:27

I'm having the same issue with Sasson, subscribing.

Comment #3

MXT

Italian

Milan

CreditAttribution: MXT commented 4 May 2012 at 14:48

Priority:

Normal

» Major

Same problem using Adaptivetheme:

Error while trying to find the common path for enabled extensions of project adaptivetheme. Extensions are: aaa_update_test, actions_loop_test, actions_permissions, ... [ALL INSTALLED MODULE APPEAR IN THIS LIST]

UPDATE:

Removing the following lines from my subtheme .info file the error disappear:

; Information added by drupal.org packaging script on 2012-04-25
version = "7.x-3.0-beta1+9-dev"
core = "7.x"
project = "adaptivetheme"
datestamp = "1335312122"

Comment #4

jonhattan

Spanish

Plasencia

CreditAttribution: jonhattan commented 4 May 2012 at 14:55

The culprit is having a line like project = "adaptivetheme" in a subtheme, that is not part of the adaptivetheme project in drupal.org.

What surprises me is that it shows all extensions. It should show only the ones with project = "adaptivetheme" in its .info.

@MXT can you post a complete debug output in order to inspect it? Also where is placed adaptivetheme and where your subtheme?

Comment #5

jonhattan

Spanish

Plasencia

CreditAttribution: jonhattan commented 4 May 2012 at 15:04

Title:	theme errors on pm-update after updating drush from 4.5 to 5.1	» Show only involved extensions if failed to obtain the common path for a project's extensions
Status:	Active	» Fixed

Just found that is was printing all extensions and not only the involved ones.

Fixed:

http://drupalcode.org/project/drush.git/commitdiff/024066a?hp=a69fcace92...

Comment #6

mollyavalon CreditAttribution: mollyavalon commented 12 May 2012 at 19:21

Status:

Fixed

» Active

I am having the same problem with an Omega subtheme and so I'm reopening this.

This is happening only on my local computer (Mac). Drush is working fine on the server.

I run drush pm-update and get the error and giant list of extensions. My subtheme's .info file was created with Omega Tools and so does not contain the line project="Omega".

I had just upgraded my version of drush to 5.1 (same as on the server). Finally I removed drush and then reinstalled it. Same problem, not fixed.

Oddly enough, I had the same problem with a Fusion subthemed site today too, but it DID have the project="Fusion" line. I removed it and all was well. But the stranger part is that before I removed it, drush did not produce the error on the server. Why would it be different on the server from the local when the version of drush is the same and the version of the subtheme is the same?

Comment #7

Andy_Read CreditAttribution: Andy_Read commented 15 May 2012 at 11:42

I've been getting this sort of error ever since I upgraded drush on 2012-04-20.

But in my case it's the smsframework module that causes the problem.

As per #3, I removed all of the packing script info from the 5 submodules, including the line: project = "smsframework" - this made no difference whatsoever.

I've now applied the patch in #5 and now get simply this:
Error while trying to find the common path for enabled extensions of project smsframework. Extensions are: , , . [error]
(NB Extension are "comma comma stop")

### Update ###
I also had two custom modules outside of the smsframework dir with 'project = "smsframework"' in their .info files. Removing these lines have clear the error report.

Comment #8

jonhattan

Spanish

Plasencia

CreditAttribution: jonhattan commented 15 May 2012 at 16:10

Status:

Active

» Fixed

Fixed the Extensions are: , , . bug.

Comment #9

mducharme CreditAttribution: mducharme commented 22 May 2012 at 20:24

Status:

Fixed

» Active

This is still an issue and I'm wondering, is this a problem with the Drupal packing script? Shouldn't it be setting the name of the project AS the sub-project's name instead of the parents? I'm having this error popping up for several modules that have sub-projects in which Drupal packing script is adding this incorrect(?) information.

If someone could clarify this for me we could move this over to a drupal issue instead of a drush issue.

Comment #10

jonhattan

Spanish

Plasencia

CreditAttribution: jonhattan commented 23 May 2012 at 07:36

Status:

Active

» Fixed

@mducharme I'm not sure if I understand you. For the sake of understanding, a project is http://drupal.org/project/{projectname} and projects contain extensions(modules or themes). For example project views contains extensions views and views_ui. The project for views_ui is views.

If you still have an issue, post a debug output.

Comment #11

mducharme CreditAttribution: mducharme commented 23 May 2012 at 15:06

So are the following modules not written properly for Drush to find it's extensions or is this a Drush issue? If this too irrelevant for the topic let me know and I'll move this into a new issue.
Drush 5.2
Drupal 7.14

Error while trying to find the common path for enabled extensions of project metatag. Extensions are: metatag, metatag_opengraph,    [error]
metatag_test, metatag_ui.

metatag/metatag_ui/metatag_ui.info

name = Meta tag UI
description = User interface for the Meta tag API.
package = Meta tags
core = 7.x
dependencies[] = metatag
dependencies[] = ctools
hidden = TRUE

; Information added by drupal.org packaging script on 2012-03-28
version = "7.x-1.0-alpha5"
core = "7.x"
project = "metatag"
datestamp = "1332895560"

Same error for the relation module...

Error while trying to find the common path for enabled extensions of project relation. Extensions are: relation, relation_add,       [error]
relation_dummy_field, relation_endpoint, relation_entity_collector, relation_rules_test.

Comment #12

mducharme CreditAttribution: mducharme commented 1 June 2012 at 16:18

Does anyone have insight into what would cause Drush to fail to obtain the common path for a project's extensions? I'm having difficulty finding any resources on this topic.