UPDATE_REVOKED

Current release has been unpublished and is no longer available. File core/modules/update/update.module, line 29 Handles updates of Drupal core and contributed projects. Code const UPDATE_REVOKED = 2;

update_replace_permissions

update_replace_permissions($replace) Replace permissions during update. This function can replace one permission to several or even delete an old one. Parameters array $replace: An associative array. The keys are the old permissions the values are lists of new permissions. If the list is an empty array, the old permission is removed. File core/includes/update.inc, line 671 Drupal database update API. Code function update_replace_permissions($replace) { $prefix = 'user.role.'; $cut = strl

update_refresh

update_refresh() Refreshes the release data after loading the necessary include file. File core/modules/update/update.module, line 386 Handles updates of Drupal core and contributed projects. Code function update_refresh() { \Drupal::service('update.manager')->refreshUpdateData(); }

update_requirements

update_requirements($phase) Implements hook_requirements(). Return value An array describing the status of the site regarding available updates. If there is no update data, only one record will be returned, indicating that the status of core can't be determined. If data is available, there will be two records: one for core, and another for all of contrib (assuming there are any contributed modules or themes enabled on the site). In addition to the fields expected by hook_requirements ('value',

update_resolve_dependencies

update_resolve_dependencies($starting_updates) Resolves dependencies in a set of module updates, and orders them correctly. This function receives a list of requested module updates and determines an appropriate order to run them in such that all update dependencies are met. Any updates whose dependencies cannot be met are included in the returned array but have the key 'allowed' set to FALSE; the calling function should take responsibility for ensuring that these updates are ultimately not per

UPDATE_NOT_CURRENT

Project has a new release available, but it is not a security release. File core/modules/update/update.module, line 39 Handles updates of Drupal core and contributed projects. Code const UPDATE_NOT_CURRENT = 4;

UPDATE_NOT_FETCHED

There was a failure fetching available update data for this project. File core/modules/update/update.module, line 59 Handles updates of Drupal core and contributed projects. Code const UPDATE_NOT_FETCHED = -3;

update_page_top

update_page_top() Implements hook_page_top(). File core/modules/update/update.module, line 110 Handles updates of Drupal core and contributed projects. Code function update_page_top() { /** @var \Drupal\Core\Routing\AdminContext $admin_context */ $admin_context = \Drupal::service('router.admin_context'); $route_match = \Drupal::routeMatch(); if ($admin_context->isAdminRoute($route_match->getRouteObject()) && \Drupal::currentUser()->hasPermission('administer site confi

update_process_project_info

update_process_project_info(&$projects) Determines version and type information for currently installed projects. Processes the list of projects on the system to figure out the currently installed versions, and other information that is required before we can compare against the available releases to produce the status report. Parameters $projects: Array of project information from \Drupal\Update\UpdateManager::getProjects(). File core/modules/update/update.compare.inc, line 19 Code requir

UPDATE_NOT_CHECKED

Project's status cannot be checked. File core/modules/update/update.module, line 49 Handles updates of Drupal core and contributed projects. Code const UPDATE_NOT_CHECKED = -1;