Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Seeing that there are still quite a number of deployed phone.module, it will be good to have a migration option from D5 & D6 of phone.module. However the data migration might be a problem as the phone number is captured entirely including country codes and extension, whereas in cck_phone these are separated pieces. Would like to see proposal on how this can be done.
Comments
Comment #1
will_in_wi CreditAttribution: will_in_wi commentedSubscribe
Comment #2
scottrigby@ckng Maybe something like this pseudocode below?
I didn't add configurations – I can image different options for handling the move from phone to cck_phone:
Ideally it'd be good to keep it simple. I'm kind of leaning toward favoring replacing all old phone fields with new cck_phone fields of the same name – as a configuration, so site admins can take or leave the migration option… What do you think?
Comment #3
ckngYes, we should keep it simple.
I would imagine a link or menu item to let user migrate all old phone fields with new cck_phone fields of the same name.