UPDATE_CURRENT

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

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

update_cron

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

update_fetch_data

update_fetch_data() Attempts to fetch update data after loading the necessary include file. See also \Drupal\update\UpdateProcessor::fetchData() File core/modules/update/update.module, line 395 Handles updates of Drupal core and contributed projects. Code function update_fetch_data() { \Drupal::service('update.processor')->fetchData(); }

update_fetch_data_finished

update_fetch_data_finished($success, $results) Batch callback: Performs actions when all fetch tasks have been completed. Parameters $success: TRUE if the batch operation was successful; FALSE if there were errors. $results: An associative array of results from the batch operation, including the key 'updated' which holds the total number of projects we fetched available update data for. File core/modules/update/update.module, line 409 Handles updates of Drupal core and contributed projects.

update_do_one

update_do_one($module, $number, $dependency_map, &$context) Implements callback_batch_operation(). Performs one update and stores the results for display on the results page. If an update function completes successfully, it should return a message as a string indicating success, for example: return t('New index added successfully.'); Alternatively, it may return nothing. In that case, no message will be displayed at all. If it fails for whatever reason, it should throw an instance of Drup

update_calculate_project_data

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_check_incompatibility

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_calculate_project_update_status

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_create_fetch_task

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