minnur / location_migration
Migration plugins for migrating Drupal 7 location data from Drupal 7 to Drupal 9
Installs: 145
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 0
Type:drupal-module
pkg:composer/minnur/location_migration
Requires
- php: >=7.1
- drupal/address: ^1.8
- drupal/geolocation: ^3.2
README
The Drupal 7 Location module allows users to store locations in a
location field (location_cck submodule), and also directly for node,
taxonomy_term and user entities (location_node, location_taxonomy and
location_user submodules).
With location_email, location_fax, location_phone and location_www
submodules, the data stored for a location can be extended with additional
email, fax number, telephone number and www address properties.
The Location Migration module provides migration path for these data.
HOW IT WORKS
For location data stored in a field,
- The original
locationfield type gets mapped toaddressfield, and every address-like location property is migrated into this address field. - Non-empty geographical coordinates are migrated into a new
geolocationfield with_geolocfield name suffix. - When
location_emailis enabled on the source site, the email addresses stored for a location will be migrated into a newemailfield with_emailfield name suffix. Theemailfield type is available in Drupal 8/9 by default. - When
location_faxis enabled on the source site AND thetelephonefield type is available on the destination site (core Telephone module), the fax number of a location will be migrated into a newtelephonefield with_faxfield name suffix. - If
location_phoneis enabled on the source site AND thetelephonefield type is available on the destination site, the telephone number stored for a location will be migrated into a newtelephonefield (_phonefield name suffix). - When
location_wwwis enabled on the source site AND thelinkfield type is available on the destination site (core Link module), the www address stored for a location will be migrated into a newlinkfield (_urlfield name suffix).
For location data stored directly for node, taxonomy_term and user
entities, Location Migration basically repeats the same what it does for the
location fields, but the name of the (this time new) address field, and the base
name of the additional fields will be location_node, location_taxonomy_term
and location_user, accordingly. If this entity location was configured to
store multiple locations, the new field's name will have an additional
_<cardinality> suffix as well.
Location Migration wants to migrate as much data as possible. If you don't need any of the additional fields, you can delete them after the migration was executed.
REQUIREMENTS
This module depends on the following modules:
- Address (https://www.drupal.org/project/address)
- Geolocation (https://www.drupal.org/project/geolocation)
- Migrate Drupal (included in Drupal core)
INSTALLATION
You can install Location Migration as you would normally install a contributed Drupal 8 or 9 module.
CONFIGURATION
This module does not have any configuration option.
MAINTAINERS
Current maintainer:
- Zoltán Horváth (huzooka) - https://www.drupal.org/user/54136
This project has been sponsored by Acquia