function pmperson_migrate_page_callback in Drupal PM (Project Management) 7.2

Same name and namespace in other branches

1. 8 pmperson/includes/pmperson.migrate.inc \pmperson_migrate_page_callback()
2. 7.3 pmperson/includes/pmperson.migrate.inc \pmperson_migrate_page_callback()

Page callback for PM_PMPERSON_RESOLVE_DEPENDENCIES_LINK.

See also

pmperson_menu()

1 string reference to 'pmperson_migrate_page_callback'

pmperson_menu in pmperson/pmperson.module

Implements hook_menu().

File

pmperson/includes/pmperson.migrate.inc, line 141

Migration functions for the PM Person module.

Code

function pmperson_migrate_page_callback() {
  if (pmperson_migrate_update_could_be_performed()) {
    drupal_set_message(t('PM Person migration conflicts have been resolved.'));
    drupal_goto('update.php', array(
      'script' => 'update.php',
    ));
  }
  $form_fix_1 = drupal_get_form('pmperson_migrate_fix_existing_users_form');
  $render = array(
    'preface' => array(
      '#markup' => "\n        <p>The information captured by legacy PM Person nodes is now incorporated\n        into user accounts.</p>\n        <p>This page will ensure that all PM Person nodes can be uniquely matched\n         to existing users so that the data migration can take place.</p>\n      ",
    ),
    'table_1_info' => array(
      '#markup' => "\n        <h2>Suggested matches</h2>\n        <p>\n        This table shows PM Person nodes with the same email address as a user\n        account.\n        </p><p>\n        Normally these can be matched automatically by clicking the button below.\n        Remaining PM Person nodes will need to be manually matched.\n        </p>\n      ",
    ),
    'table_issue_1' => _pmperson_migrate_get_conflicting_email_with_existing_users_table(),
    'try_fix_1' => array(
      '#type' => 'markup',
      '#markup' => render($form_fix_1),
    ),
    'table_2_info' => array(
      '#markup' => "<br />\n        <h2>Conflicts</h2>\n        <p>This table shows PM Person nodes where a match cannot be made automatically due to data differences between them.</p>\n        <p>Edit the PM Person node or user accounts until there are no remaining\n        conflicts.</p>\n      ",
    ),
    'table_issue_2' => _pmperson_migrate_get_conflicting_email_with_attached_users_table(),
  );
  return $render;
}