Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
API page: https://api.drupal.org/api/drupal/core!lib!Drupal!Core!Extension!module....
Enter a descriptive title (above), then describe the problem you have found:
End of the 3rd line:
> At this stage Drupal is already fully repaired so you can use any API as you wish.
I believe this is supposed to read:
> At this stage Drupal is already fully bootstrapped so you can use any API you wish.
Or similar.
Steps to reproduce
Proposed resolution
Change to "At this stage Drupal is already fully bootstrapped so you can use any API you wish.
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3532469
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #2
quietone commentedIn Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies. Also mentioned on the version section of the list of issue fields documentation.
Changing to the standard issue template.
Removing tag because this is already in the documentation component
Comment #5
cilefen commentedIt's from a long time ago: #2538108: Add hook_post_update_NAME() for data value updates to reliably run after data format updates. That issue doesn't mention "repair" any comments. I agree that "repair" seems like the wrong word.
Comment #6
chhavi.sharma commentedComment #8
chhavi.sharma commentedComment #9
longwaveBikeshedding: Is "bootstrapped" more descriptive than "loaded"?
Comment #10
quietone commentedAs I read it is trying to say that since
hook_update_Nhas run the db is in a state where it is safe to run other updates. In that sense, 'repaired' makes sense. Although I would prefer "updated" to allow for fixes and features.For history, 'repaired' was added in #2538108: Add hook_post_update_NAME() for data value updates to reliably run after data format updates, at this comment. I did not find the word 'repair' in the issue.
Comment #11
smustgrave commentedSo should this be closed if repaired is preferred?
Comment #13
quietone commentedLet's go with the suggestion by longwave.
Comment #15
stefan lehmannMerged in main (should probably have done a rebase?) and changed the wording to "bootstrapped".
Comment #16
stefan lehmannEdited issue description.
Comment #17
stefan lehmannComment #18
nicxvan commentedBootstrapped makes sense!
I searched the codename and this is the only user of repaired.
I suspect repaired because it's after database changes are made. But bootstrapped is more accurate.
I read the full other issue, that was fascinating.
Comment #20
longwaveBackported down to 10.6.x as a documentation fix.
Committed and pushed to main, 11.x, 11.3.x and 10.6.x. Thanks!