Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I'm not sure if this is a drush issue or omega theme, but since drush detects the other contributed themes in my installation, my first guess is it's an issue with Omega. I get this error:
[../TheInstitute/tuci.d7]> drush up omega
Refreshing update status information ...
Done.
Error while trying to find the common path for enabled extensions of project omega. Extensions are: omega, omega_starterkit, omega_starterkit_xhtml, tuci. [error]
Update information last refreshed: 03/04/2011 - 08:58
Update status information on all installed and enabled Drupal projects:
Name Installed version Proposed version Status
Administration menu 7.x-3.0-rc1 7.x-3.0-rc1 Up to date
Advanced help 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Drupal core 7.0 7.0 Up to date
Content Construction Kit (CCK) 7.x-2.x-dev 7.x-2.x-dev Up to date
Chaos tool suite 7.x-1.0-alpha2 7.x-1.0-alpha2 Up to date
Link 7.x-1.0-alpha3 7.x-1.0-alpha3 Up to date
Masquerade 7.x-1.0-rc2 7.x-1.0-rc2 Up to date
Omega Tools 7.x-2.0 7.x-2.0 Up to date
Pathauto 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Taxonomy Manager 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Token 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Views 7.x-3.0-alpha1 7.x-3.0-alpha1 Up to date
Views Slideshow 7.x-3.x-dev 7.x-3.x-dev Up to date
Webform 7.x-3.8 7.x-3.8 Up to date
Wysiwyg 7.x-2.0 7.x-2.0 Up to date
omega Unknown Unknown Specified project not found
No code updates available. [ok]
Comment | File | Size | Author |
---|---|---|---|
#11 | omega_tools-n1081378-11.patch | 665 bytes | DamienMcKenna |
Comments
Comment #1
BrightLoudNoise CreditAttribution: BrightLoudNoise commentedI'm receiving the same error, I had been using an RC of Omega prior.
Comment #2
himerus CreditAttribution: himerus commentedYou need to make sure that you have not encountered this bug: (#986616: Update Manager fails when the primary module/theme for a project lives in a subdirectory)
Drupal core (and drush) have issues if you do an upgrade of any theme/module where a .info file doesn't live in the root directory.
So you may have ended up with the omega folder in sites/***/themes/omega/omega/omega/omega/etc.
Please just remove the omega folder and
drush dl omega
drush cc all
and let me know.
Comment #3
himerus CreditAttribution: himerus commentedalso note this issue as well: #1081182: drush upc doesn't list themes
Comment #4
spuky CreditAttribution: spuky commentedI was getting the same error
Refreshing update status information ...
Done.
Error while trying to find the common path for enabled extensions of project omega. Extensions are: [error]
kneershop, omega.
Update information last refreshed: Mo, 04/04/2011 - 15:13
the tipps didn't help ...
but deleting packaging information from my subtheme... .info file...
that part... resolved the Issue...
Comment #5
safetypinThe omega.info file is in site/all/themes/omega/omega/omega.info - which is probably why drush is throwing an error. Should I be updating to a dev version or something?
Comment #6
safetypinYeah, the error was resolved and discussed here: #1043038: Error while trying to find the common path for enabled extensions of [error] project fusion. Base Theme and Sub Theme separate.
I think that although this is a pretty easy thing to do manually, it took me a while to find the problem, and it's a problem that really should have come up in the first place. I was convinced it was an issue with the omega theme, when it was actually a problem with the subtheme. I wonder if it's something drush should fix instead of the (sub)themes, but it's not my call either way.
Comment #7
marcoka CreditAttribution: marcoka commentedis that still in 3.0?
Comment #8
himerus CreditAttribution: himerus commentedMoving to the appropriate issue queue. We do need to verify if this is still an issue with 3.x Omega/Omega Tools
Comment #9
GeminiAgaloos CreditAttribution: GeminiAgaloos commentedVerified that this is still an issue in Omega 7.x-3.1 even without using Omega Tools.
Simply creating a subtheme based on an Omega-html5 starterkit produces a .info file containing the following drupal.org packaging info that needs to be removed.
These lines are found towards the end of the .info file and is the same in the themes/omega/omega/omega.info and themes/omega/starterkits/omega-html5/starterkit_omega_html5.info files.
Removing or commenting out those lines in the subtheme resolves the drush error messge "Error while trying to find the common path for enabled extensions of project omega"
Comment #10
js CreditAttribution: js commentedHi,
I appreciate Omega very much, but hunting down this issue to see that it has been hanging around for such a long time feels like a bit of waste of time.
I deleted the project line from sub-theme .info. Is this correct?
If this can't be removed for some Drupal packaging reason, perhaps a note at the top of the .info file would help. We already have to make edits regardless. One more is minor, just knowing to do it is helpful.
Thanks again for this useful theme.
Comment #11
DamienMcKennaHow about this? During the subtheme creation process it removes the 'package' info line if the base theme is a starterkit.