The testing profile does not enable required modules like node but uses its permission 'access content'. This leads to a fatal error during testing_install() using drush. Attached patch adds one dependencies[] line to testing.info which is enough to kick in the dependency check and thus all required modules are enabled. Patch also adds a customary files[] = testing.profile like other profiles.

CommentFileSizeAuthor
#2 testing.patch456 bytesmoshe weitzman
testing_profile.patch699 bytesmoshe weitzman

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Needs review » Needs work

I don't see that second hunk as mentioned in this patch.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs work » Needs review
StatusFileSize
new testing.patch456 bytes

woops. posted wrong patch. this one adds the single required line. the files[] entry is kinda pointless as long as testing.profile is empty.

David_Rothstein’s picture

David_Rothstein commented

I guess this profile is a bit of an edge case, but seems like a bug in the installer itself if it ever allows Drupal to be installed without the required modules being turned on... should this be fixed there instead?

moshe weitzman’s picture

moshe weitzman commented

Exactly. This is the one profile in the drupal universe that doesn't add another module. With such an easy workaround, I really don't see the value in hunting for a deeper change.

alanburke’s picture

alanburke commented

Thanks Moshe!
This fixes the problem I was speaking to you about at the Drupalcon CPH sprint, before I had to rush off.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Mmm. This smells an awful lot like #898654: Required modules not installed before optional modules to me. I'd prefer to fix this at the source.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Closed (duplicate)

Yup. That patch fixes this issue. Just confirmed it.