update_build_dependency_graph($update_functions) Constructs a graph which encodes the dependencies between module updates. This function returns an associative array which contains a "directed graph" representation of the dependencies between a provided list of update functions, as well as any outside update functions that they directly depend on but that were not in the provided list. The vertices of the graph represent the update functions themselves, and each edge represents a requirement th

update_calculate_project_data($available) Calculates the current update status of all projects on the site. The results of this function are expensive to compute, especially on sites with lots of modules or themes, since it involves a lot of comparisons and other operations. Therefore, we store the results. However, since this is not the data about available updates fetched from the network, it is ok to invalidate it somewhat quickly. If we keep this data for very long, site administrators are

update_calculate_project_update_status(&$project_data, $available) Calculates the current update status of a specific project. This function is the heart of the update status feature. For each project it is invoked with, it first checks if the project has been flagged with a special status like "unsupported" or "insecure", or if the project node itself has been unpublished. In any of those cases, the project is marked with an error and the next project is considered. If the project itself i

update_check_incompatibility($name, $type = 'module') Tests the compatibility of a module or theme. File core/includes/update.inc, line 37 Drupal database update API. Code function update_check_incompatibility($name, $type = 'module') { static $themes, $modules; // Store values of expensive functions for future use. if (empty($themes) || empty($modules)) { // We need to do a full rebuild here to make sure the database reflects any // code changes that were made in the filesyste

update_check_requirements() Checks update requirements and reports errors and (optionally) warnings. File core/includes/update.inc, line 96 Drupal database update API. Code function update_check_requirements() { // Check requirements of all loaded modules. $requirements = \Drupal::moduleHandler()->invokeAll('requirements', array('update')); $requirements += update_system_schema_requirements(); return $requirements; }

update_clear_update_disk_cache() Clears the temporary files and directories based on file age from disk. File core/modules/update/update.module, line 707 Handles updates of Drupal core and contributed projects. Code function update_clear_update_disk_cache() { // List of update module cache directories. Do not create the directories if // they do not exist. $directories = array( _update_manager_cache_directory(FALSE), _update_manager_extract_directory(FALSE), ); // Search fo

update_create_fetch_task($project) Adds a task to the queue for fetching release history data for a project. We only create a new fetch task if there's no task already in the queue for this particular project (based on 'update_fetch_task' key-value collection). Parameters $project: Associative array of information about a project as created by \Drupal\Update\UpdateManager::getProjects(), including keys such as 'name' (short name), and the 'info' array with data from a .info.yml file for the pr

update_cron() Implements hook_cron(). File core/modules/update/update.module, line 212 Handles updates of Drupal core and contributed projects. Code function update_cron() { $update_config = \Drupal::config('update.settings'); $frequency = $update_config->get('check.interval_days'); $interval = 60 * 60 * 24 * $frequency; $last_check = \Drupal::state()->get('update.last_check') ? : 0; if ((REQUEST_TIME - $last_check) > $interval) { // If the configured update interval ha

Project is up to date. File core/modules/update/update.module, line 44 Handles updates of Drupal core and contributed projects. Code const UPDATE_CURRENT = 5;

update_delete_file_if_stale($path) Deletes stale files and directories from the update manager disk cache. Files and directories older than 6 hours and development snapshots older than 5 minutes are considered stale. We only cache development snapshots for 5 minutes since otherwise updated snapshots might not be downloaded as expected. When checking file ages, we need to use the ctime, not the mtime (modification time) since many (all?) tar implementations go out of their way to set the mtime o