function update_get_available in Drupal 7

Same name and namespace in other branches

1. 8 core/modules/update/update.module \update_get_available()
2. 6 modules/update/update.module \update_get_available()
3. 9 core/modules/update/update.module \update_get_available()
4. 10 core/modules/update/update.module \update_get_available()

Tries to get update information from cache and refreshes it when necessary.

In addition to checking the cache lifetime, this function also ensures that there are no .info files for enabled modules or themes that have a newer modification timestamp than the last time we checked for available update data. If any .info file was modified, it almost certainly means a new version of something was installed. Without fresh available update data, the logic in update_calculate_project_data() will be wrong and produce confusing, bogus results.

Parameters

$refresh: (optional) Boolean to indicate if this method should refresh the cache automatically if there's no data. Defaults to FALSE.

Return value

Array of data about available releases, keyed by project shortname.

See also

update_refresh()

update_get_projects()

4 calls to update_get_available()

update_cron in modules/update/update.module

Implements hook_cron().

update_manager_update_form in modules/update/update.manager.inc

Form constructor for the update form of the Update Manager module.

update_requirements in modules/update/update.install

Implements hook_requirements().

update_status in modules/update/update.report.inc

Page callback: Generates a page about the update status of projects.

File

modules/update/update.module, line 397

Handles updates of Drupal core and contributed projects.

Code

function update_get_available($refresh = FALSE) {
  module_load_include('inc', 'update', 'update.compare');
  $needs_refresh = FALSE;

  // Grab whatever data we currently have cached in the DB.
  $available = _update_get_cached_available_releases();
  $num_avail = count($available);
  $projects = update_get_projects();
  foreach ($projects as $key => $project) {

    // If there's no data at all, we clearly need to fetch some.
    if (empty($available[$key])) {
      update_create_fetch_task($project);
      $needs_refresh = TRUE;
      continue;
    }

    // See if the .info file is newer than the last time we checked for data,
    // and if so, mark this project's data as needing to be re-fetched. Any
    // time an admin upgrades their local installation, the .info file will
    // be changed, so this is the only way we can be sure we're not showing
    // bogus information right after they upgrade.
    if ($project['info']['_info_file_ctime'] > $available[$key]['last_fetch']) {
      $available[$key]['fetch_status'] = UPDATE_FETCH_PENDING;
    }

    // If we have project data but no release data, we need to fetch. This
    // can be triggered when we fail to contact a release history server.
    if (empty($available[$key]['releases'])) {
      $available[$key]['fetch_status'] = UPDATE_FETCH_PENDING;
    }

    // If we think this project needs to fetch, actually create the task now
    // and remember that we think we're missing some data.
    if (!empty($available[$key]['fetch_status']) && $available[$key]['fetch_status'] == UPDATE_FETCH_PENDING) {
      update_create_fetch_task($project);
      $needs_refresh = TRUE;
    }
  }
  if ($needs_refresh && $refresh) {

    // Attempt to drain the queue of fetch tasks.
    update_fetch_data();

    // After processing the queue, we've (hopefully) got better data, so pull
    // the latest from the cache again and use that directly.
    $available = _update_get_cached_available_releases();
  }
  return $available;
}