- 🇨🇦Canada adriancid Montreal, Canada
I think there is clear explanation in this change notice: hook_post_update_NAME() introduced to change content after hook_update_N() runs →
In Drupal 8 there are two ways for a module to run configuration/schema/database updates. One is by creating a hook_update_N hook in your module's .install file. The other way is new to Drupal 8 and is to create a hook_post_update_NAME hook in your module's .post_update.php file.
Problems:
First, we need to establish hard and fast rules about these hooks. I don't know what they are. I generally just understand that it's not safe to put certain changes in hook_update_n(). But if it were as simple as that, then why not just use post_update for everything?
Active
11.0 🔥
Enhances developer experience.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think there is clear explanation in this change notice: hook_post_update_NAME() introduced to change content after hook_update_N() runs →