A site's install profile is registered as a module in core.extension config, with a weight of 1000.

This is hardcoded in install_finished(), though patches at #3266057: Allow profiles to define a base/parent profile [continue of #1356276] add a hardcoded value of 1000 in to the Extension component too.

Until this quirk of the profile system is cleaned up, we could add a constant for the value to the relevant class, so it's easier to spot and has documentation.

This should probably be postponed on #3266057: Allow profiles to define a base/parent profile [continue of #1356276], as some patches there have been adding a ProfileHandlerInterface which might be a sensible place to define the constant.

Comments

joachim created an issue. See original summary.

joachim’s picture

joachim commented
Issue summary: View changes

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nicxvan’s picture

nicxvan commented

Let's add it here https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

I propose a new section at the very end

# Hook order in profiles
Profiles are hardcoded to have a weight of 1000.
This means xyz....

joachim’s picture

joachim commented
Issue summary: View changes

#3266057: Allow profiles to define a base/parent profile [continue of #1356276] now says it'll probably never be in core.

We could put this in ExtensionDiscovery, or create a ProfileHandler for consistency?

nicxvan’s picture

nicxvan commented
Status: Active » Fixed

I added a line on the page documenting that 1000 is the weight.

I don't think a constant is necessary people can see in the core.extension.yml.

I'm going to mark this as fixed.

If you think we need further docs feel free to suggest something here.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.