Dependencies of dependencies are ignored by installation profiles (and by test setUp methods)

Created on 19 August 2011, over 13 years ago

Updated 8 June 2023, over 1 year ago

An oddity I just ran into with D7:

New installation of Drupal 7.7 core + many contrib modules
Rules (7.x-2.0-rc1) was downloaded.
Entities API was not downloaded.
Rules was listed as a dependency on the install profile, Entities API was not. Note: Entities API is a dependency for Rules.
The install ran fine, it installed all of the other modules & no errors showed up, except that once it tried to bring up install.php?op=finished the Rules module gave an error that one of the Entities API classes could not be loaded, i.e. it wanted the Entities API module but it had not checked for its existence.

Some related issues:

Related search terms:

The patch proposed in #9, although it is sort of hacky.

Reroll the proposed patch.

🐛 Bug report

Status

Needs work

Version

9.5

Component

Install →

Last updated 3 days ago

No maintainer

Created by

🇺🇸United States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.

DrupalWTF
Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

Needs manual testing
The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇳🇿New Zealand luke.stewart
Looking at this:

This issue dates back to D7 and is flagged with needs backport - but in this stage of D7 lifecycle I think this can be removed as this bug relates to new installs - and one would hope new installs of D7 are extremely rare at this point!

1093420 is an attempt to address the impacts of this bug when testing based on install profiles this seems to indicate this is still a problem - but only in D7 - there is no evidence for D8+

Reading back over the issue

I'm flagging this as needs manual testing. As I don't see any evidence suggesting that this is an issue in D9/10/11. If it is we definitely should address. But the implementation has changed somewhat and based on the comments of the method in D11 branch I'm not convinced this is still a problem.
Issue was unassigned.
Comment over 1 year ago →
🇳🇱Netherlands kingdutch
I did not get to it in the fatal week of 2018, nor in any week since: unassigning.

Production build 0.71.5 2024