function upgrade_status_moved_into_core in Upgrade Status 5

Same name and namespace in other branches

1. 6 upgrade_status.module \upgrade_status_moved_into_core()
2. 7 upgrade_status.module \upgrade_status_moved_into_core()

Return status and notice about modules moved into Core.

Assign custom upgrade information for certain modules.

Parameters

$projects: Array of projects from upgrade_status_calculate_project_data().

$project: Project name to check.

Return value

TRUE if module has been moved into core.

1 call to upgrade_status_moved_into_core()

upgrade_status_calculate_project_data in ./upgrade_status.admin.inc

Given the installed projects and the available release data retrieved from remote servers, calculate the current status.

File

./upgrade_status.admin.inc, line 277

Checks to see if your installed modules are available for the next major release of Drupal.

Code

function upgrade_status_moved_into_core(&$projects, $project) {
  $core = TRUE;
  switch ($project) {
    case 'actions':
      $projects[$project]['in_core_since'] = '6.x';
      $projects[$project]['in_core_note'] = t('Please note that the syntax for actions used by the 5.x-1.x and 4.7 versions of Actions module are different to triggers in Drupal 6.x. For further information please refer to the <a href="!project-url">Actions</a> module project page.', array(
        '!project-url' => 'http://drupal.org/project/actions',
      ));
      break;
    case 'ahah_forms':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'autolocale':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'book_bridge':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'find_path':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'html_to_text':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'htmlcorrector':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'javascript_aggregator':
      $projects[$project]['in_core_since'] = '6.x';
      $projects[$project]['in_core_note'] = t('Please note that there is a version of <a href="!project-url">JavaScript Aggregator</a> module for Drupal 6.x, which additionally minifies JavaScript.', array(
        '!project-url' => 'http://drupal.org/project/javascript_aggregator',
      ));
      break;
    case 'openid':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'themesettingsapi':
      $projects[$project]['in_core_since'] = '6.x';
      break;
    case 'update_status':
      $projects[$project]['in_core_since'] = '6.x';
      $projects[$project]['in_core_note'] = t('Please note that some of the advanced settings in the 5.x version of Update status are not present in the update.module in 6.x core, and have been moved into the <a href="!project-url">Update status advanced settings</a> module for Drupal 6.x and beyond.', array(
        '!project-url' => 'http://drupal.org/project/update_advanced',
      ));
      break;
    case 'user_status':
      $projects[$project]['in_core_since'] = '6.x';
      $projects[$project]['in_core_note'] = t('There is no database upgrade path for sites that used the 5.x version of the user_status module to migrate the message templates to the new settings in core. Furthermore, the place-holders available in these templates are different in 6.x core. Therefore, users will have to re-enter their message templates into the core settings at admin/user/settings.');
      break;
    default:
      $core = FALSE;
  }
  if ($core) {
    $projects[$project]['status'] = UPGRADE_STATUS_CORE;
  }
  return $core;
}