Almost no one uses /update.php but instead runs drush updb or drush deploy (which invokes updb.) Drush allows commands to specify the kernel when executing, which can be drupal (standard), update, or installer. I know it's standard practice, but I prefer preserving caches and crafting appropriate cache invalidations when needed for deployments.) Is that it? The difference is that Drupal's caches are flushed before hook_post_update_NAME is invoked? We already are not getting cached values back, but defining a hook_post_update_NAME – empty or with content ensures all of Drupal's caches are flushed (which I'm not a fan of dumping all your caches in a deployment. ![]() Each post-update hook is then added to the batch.If there are post-update hooks, drupal_flush_all_caches is invoked to reset all of Drupal's caches.Then the post-update hooks are discovered. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |