About 'dependencies[] = standard'... [#1373146]

In the '.info' File Content field, dependencies[] = standard is listed. Took me a while to figure out that it was one of the available profiles. The problem is that this will generate an error message during installation (Requirements problem).

The following modules are required but were not found. Move them into the appropriate modules subdirectory, such as sites/all/modules. Missing modules: Standard.

Removing dependencies[] = standard is required for the installation to be successful.

Comments

Comment #1

markwk CreditAttribution: markwk commented 16 December 2011 at 16:51

Status:

Active

» Closed (works as designed)

Yeah, "standard" is the original standard installation profile. Drupal 7 does some interesting things I still haven't quite figure out yet.

Unfortunately, this module is not a magic "mothership" that can take a current site and convert it into an installation profile. It's just a helper... ;-)

Comment #2

bisonbleu CreditAttribution: bisonbleu commented 16 December 2011 at 19:46

I wasn't complainin'... Just reporting. :-)

Comment #3

markwk CreditAttribution: markwk commented 16 December 2011 at 19:51

Yeah, I had the same issue my first installation building with this module too. I do dream of that "mothership" module, though.

But it's a testament to how wonky the Drupal plumbing is that a profiler_builder runs a query for modules and pulls the installation profile as a module

Comment #4

bisonbleu CreditAttribution: bisonbleu commented 16 December 2011 at 22:39

Isn't there a tune by the Stones called Wonkytonk something...
Hey Drupal needs an anthem, right? ;-)

Comment #5

btopro CreditAttribution: btopro commented 24 October 2012 at 02:13

Version:	7.x-1.0-alpha2	» 7.x-1.x-dev
Status:	Closed (works as designed)	» Fixed

This has been fixed in dev. It checks against the listed installed profile and disables it. This makes sense because you are building an install profile off of something made with a different install profile (theoretically). Also while a profile can technically house module files it's not best practice to do so. Other hooks would allow someone to inject it back in if they really want to but this is an edge case. The norm is to remove the profile "module" in dependencies.