function taxonomy_xml_requirements in Taxonomy import/export via XML 6.2

Same name and namespace in other branches

1. 7 taxonomy_xml.install \taxonomy_xml_requirements()

Implementation of hook_requirements().

Advice on missing functionality

File

./taxonomy_xml.install, line 47

Install, update and uninstall functions for the taxonomy_xml module.

Code

function taxonomy_xml_requirements($phase) {
  $requirements = array();
  if ($phase == 'runtime') {

    // Advise that taxonomy_enhancer is useful
    if (module_exists('taxonomy_guid')) {
      $requirements['taxonomy_guid'] = array(
        'value' => t('taxonomy_guid module is available.'),
        'severity' => REQUIREMENT_OK,
        'description' => t('
          taxonomy_guidwill assist taxonomy imports
          by enabling a unique Identifier for each imported term.
        '),
      );
    }
    else {
      $requirements['taxonomy_guid'] = array(
        'value' => t('taxonomy_guid module is not enabled.'),
        'severity' => REQUIREMENT_INFO,
        'description' => t('
          taxonomy_guid is very useful to taxonomy_xml
          if you are planning to import external taxonomies from web services.
          <em>It is not required</em>, but will enable us to add a GUID (unique identifier)
          field to your terms so that imports can be structured correctly.
          Without it we cannot import vocabulary heirarchies via spidering,
          although small all-in-one vocabulary imports (from a single file)
          should still work.
        '),
      );
    }
    $requirements['taxonomy_guid']['title'] = t('taxonomy_guid (for taxonomy_xml)');
  }
  $requirements['taxonomy_xml'] = array(
    'title' => 'Taxonomy XML is enabled',
    'value' => "Taxonomy XML is intended as a run-once setup or migration module, you may be able to disable it once it's done its job",
    'severity' => REQUIREMENT_INFO,
  );
  return $requirements;
}