Profiles and themes should be excluded [#1325654]

A profile can only do harm, I think, so they should be excluded.

However, wrongly built profiles like http://drupal.org/project/b2b_store_solution do all sorts of damage. by actually including modules in themselves.

Comment	File	Size	Author
#4	project_dependency.skip_install_profiles_and_themes_1325654_03.patch	1.58 KB	rfay

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 4 November 2011 at 16:42

I don't know how we can figure this out easily. Look for the .module or .theme or .profile? Maybe that would do it.

See #1332104: Modules, Themes, Profiles should declare their type in their .info file

Comment #2

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 4 November 2011 at 18:51

Can one simply look to see if there is [filename_same_as_info].module and therefore class as module, same for theme and profile?

Comment #3

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 23 December 2011 at 02:14

Title:	Profiles need to be excluded (and why not themes?)	» Profiles and themes should be excluded
Priority:	Normal	» Critical

Comment #4

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 24 December 2011 at 14:50

Status:

Active

» Needs review

File	Size
project_dependency.skip_install_profiles_and_themes_1325654_03.patch	1.58 KB

I believe this will do the trick. I was trying to figure out how to get it from the database, but that information is buried deeply somewhere in taxonomy. Probably not reliable to get it from there.