function upgrade_status_calculate_project_data in Upgrade Status 6
Same name and namespace in other branches
- 5 upgrade_status.admin.inc \upgrade_status_calculate_project_data()
- 7 upgrade_status.compare.inc \upgrade_status_calculate_project_data()
Given the installed projects and the available release data retrieved from remote servers, calculate the current status.
This function is the heart of the update status feature. It iterates over every currently installed project. For each one, 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 is valid, the function decides what major release series to consider. The project defines what the currently supported major versions are for each version of core, so the first step is to make sure the current version is still supported. If so, that's the target version. If the current version is unsupported, the project maintainer's recommended major version is used. There's also a check to make sure that this function never recommends an earlier release than the currently installed major version.
Given a target major version, it scans the available releases looking for the specific release to recommend (avoiding beta releases and development snapshots if possible). This is complicated to describe, but an example will help clarify. For the target major version, find the highest patch level. If there is a release at that patch level with no extra ("beta", etc), then we recommend the release at that patch level with the most recent release date. If every release at that patch level has extra (only betas), then recommend the latest release from the previous patch level. For example:
1.6-bugfix <-- recommended version because 1.6 already exists. 1.6
or
1.6-beta 1.5 <-- recommended version because no 1.6 exists. 1.4
It also looks for the latest release from the same major version, even a beta release, to display to the user as the "Latest version" option. Additionally, it finds the latest official release from any higher major versions that have been released to provide a set of "Also available" options.
Finally, and most importantly, it keeps scanning the release history until it gets to the currently installed release, searching for anything marked as a security update. If any security updates have been found between the recommended release and the installed version, all of the releases that included a security fix are recorded so that the site administrator can be warned their site is insecure, and links pointing to the release notes for each security update can be included (which, in turn, will link to the official security announcements for each vulnerability).
This function relies on the fact that the .xml release history data comes sorted based on major version and patch level, then finally by release date if there are multiple releases such as betas from the same major.patch version (e.g. 5.x-1.5-beta1, 5.x-1.5-beta2, and 5.x-1.5). Development snapshots for a given major version are always listed last.
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 cache the results into the {cache_update} table using the 'update_project_data' cache ID. 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 more likely to see incorrect results if they upgrade to a newer version of a module or theme but do not visit certain pages that automatically clear this cache.
Parameters
$available: Array of data about available project releases.
See also
upgrade_status_get_available()
1 call to upgrade_status_calculate_project_data()
- upgrade_status_status in ./
upgrade_status.report.inc - Menu callback. Generate a page about the upgrade status of projects.
File
- ./
upgrade_status.compare.inc, line 87
Code
function upgrade_status_calculate_project_data($available) {
// Retrieve the projects from cache, if present.
// US: Directly use private cache getter to skip Update's cache invalidation.
$projects = _update_cache_get('upgrade_status_project_data');
// If $projects is empty, then the cache must be rebuilt.
// Otherwise, return the cached data and skip the rest of the function.
if (!empty($projects)) {
return $projects->data;
}
$projects = update_get_projects();
update_process_project_info($projects);
foreach ($projects as $project => $project_info) {
if (isset($available[$project])) {
// If the project status is marked as something bad, there's nothing
// else to consider.
if (isset($available[$project]['project_status'])) {
switch ($available[$project]['project_status']) {
case 'insecure':
$projects[$project]['status'] = UPDATE_NOT_SECURE;
if (empty($projects[$project]['extra'])) {
$projects[$project]['extra'] = array();
}
$projects[$project]['extra'][] = array(
'class' => 'project-not-secure',
'label' => t('Project not secure'),
'data' => t('This project has been labeled insecure by the Drupal security team, and is no longer available for download. Immediately disabling everything included by this project is strongly recommended!'),
);
break;
// US: Maintainers are doing lots of nightmares with in development
// releases, so we have to take unpublished, revoked, and unsupported
// into account.
case 'unpublished':
case 'revoked':
case 'unsupported':
break;
case 'not-fetched':
$projects[$project]['status'] = UPDATE_NOT_FETCHED;
$projects[$project]['reason'] = t('Failed to fetch available update data');
break;
default:
// Assume anything else (e.g. 'published') is valid and we should
// perform the rest of the logic in this function.
break;
}
}
if (!empty($projects[$project]['status'])) {
// We already know the status for this project, so there's nothing
// else to compute. Just record everything else we fetched from the
// XML file into our projects array and move to the next project.
$projects[$project] += $available[$project];
continue;
}
// Figure out the target major version.
$existing_major = $project_info['existing_major'];
$supported_majors = array();
if (isset($available[$project]['supported_majors'])) {
$supported_majors = explode(',', $available[$project]['supported_majors']);
}
elseif (isset($available[$project]['default_major'])) {
// Older release history XML file without supported or recommended.
$supported_majors[] = $available[$project]['default_major'];
}
if (in_array($existing_major, $supported_majors)) {
// Still supported, stay at the current major version.
$target_major = $existing_major;
}
elseif (isset($available[$project]['recommended_major'])) {
// Since 'recommended_major' is defined, we know this is the new XML
// format. Therefore, we know the current release is unsupported since
// its major version was not in the 'supported_majors' list. We should
// find the best release from the recommended major version.
$target_major = $available[$project]['recommended_major'];
// US: Projects may port from 6.x-1.x to 7.x-2.x to change their APIs.
# $projects[$project]['status'] = UPDATE_NOT_SUPPORTED;
}
elseif (isset($available[$project]['default_major'])) {
// Older release history XML file without recommended, so recommend
// the currently defined "default_major" version.
$target_major = $available[$project]['default_major'];
}
else {
// Malformed XML file? Stick with the current version.
$target_major = $existing_major;
}
// US: Some projects are renumbering to 1.x with each new core version.
# $target_major = max($existing_major, $target_major);
$version_patch_changed = '';
$patch = '';
// US: Of course, not yet ported don't have any releases. ;)
# // Defend ourselves from XML history files that contain no releases.
# if (empty($available[$project]['releases'])) {
# $projects[$project]['status'] = UPDATE_UNKNOWN;
# $projects[$project]['reason'] = t('No available releases found');
# continue;
# }
foreach ($available[$project]['releases'] as $version => $release) {
// US: insecure, unpublished, revoked, unsupported have no meaning.
// See if this is a higher major version than our target and yet still
// supported. If so, record it as an "Also available" release.
if ($release['version_major'] > $target_major) {
if (in_array($release['version_major'], $supported_majors)) {
if (!isset($available[$project]['also'])) {
$available[$project]['also'] = array();
}
if (!isset($available[$project]['also'][$release['version_major']])) {
$available[$project]['also'][$release['version_major']] = $version;
}
}
// US: Some projects are renumbering to 1.x with each new core version.
# continue;
}
// Look for the 'latest version' if we haven't found it yet. Latest is
// defined as the most recent version for the target major version.
if (!isset($available[$project]['latest_version']) && $release['version_major'] == $target_major) {
$available[$project]['latest_version'] = $version;
}
// Look for the development snapshot release for this branch.
if (!isset($available[$project]['dev_version']) && $release['version_major'] == $target_major && isset($release['version_extra']) && $release['version_extra'] == 'dev') {
$available[$project]['dev_version'] = $version;
}
// Look for the 'recommended' version if we haven't found it yet (see
// phpdoc at the top of this function for the definition).
if (!isset($available[$project]['recommended']) && $release['version_major'] == $target_major && isset($release['version_patch'])) {
if ($patch != $release['version_patch']) {
$patch = $release['version_patch'];
$version_patch_changed = $release['version'];
}
if (empty($release['version_extra']) && $patch == $release['version_patch']) {
$available[$project]['recommended'] = $version_patch_changed;
}
}
// US: Don't stop searching, even if we hit the currently installed version.
// US: Ignore dev snapshot handling.
// US: Ignore security updates.
}
// If we were unable to find a recommended version, then make the latest
// version the recommended version if possible.
if (!isset($available[$project]['recommended']) && isset($available[$project]['latest_version'])) {
$available[$project]['recommended'] = $available[$project]['latest_version'];
// US: No recommended version means there's a dev snapshot.
$projects[$project]['status'] = UPGRADE_STATUS_DEVELOPMENT;
$projects[$project]['reason'] = t('In development');
}
// Stash the info about available releases into our $projects array.
$projects[$project] += $available[$project];
//
// Check to see if we need an update or not.
//
// US: Skip security update status handling.
// US: Check new Drupal core improvements, regardless of what's figured
// out below.
if (upgrade_status_moved_into_core($projects, $project)) {
$projects[$project]['status'] = UPGRADE_STATUS_CORE;
$projects[$project]['reason'] = t('In core');
}
if (isset($projects[$project]['status'])) {
// If we already know the status, we're done.
continue;
}
// If we don't know what to recommend, there's nothing we can report.
// Bail out early.
if (!isset($projects[$project]['recommended'])) {
$projects[$project]['status'] = UPDATE_UNKNOWN;
$projects[$project]['reason'] = t('No available releases found');
continue;
}
// US: Ignore dev snapshot handling.
// Figure out the status, based on what we've seen and the install type.
// Note: If we were not yet able to assign a status, this project already
// provides a stable release.
switch ($projects[$project]['install_type']) {
case 'official':
case 'dev':
$projects[$project]['status'] = UPGRADE_STATUS_STABLE;
$projects[$project]['reason'] = t('Available');
break;
default:
$projects[$project]['status'] = UPDATE_UNKNOWN;
$projects[$project]['reason'] = t('Invalid info');
}
}
elseif (upgrade_status_moved_into_core($projects, $project)) {
$projects[$project]['status'] = UPGRADE_STATUS_CORE;
$projects[$project]['reason'] = t('In core');
}
else {
$projects[$project]['status'] = UPDATE_UNKNOWN;
$projects[$project]['reason'] = t('No available releases found');
}
}
// Give other modules a chance to alter the status (for example, to allow a
// contrib module to provide fine-grained settings to ignore specific
// projects or releases).
drupal_alter('update_status', $projects);
// US: Same for us, afterwards.
drupal_alter('upgrade_status', $projects);
// Cache the site's update status for at most 1 hour.
_update_cache_set('upgrade_status_project_data', $projects, time() + 3600);
return $projects;
}