Contrib.social

Migrate configuration from 7.x-3.x

Open on Drupal.org →
Created on 19 February 2021, over 3 years ago
Updated 22 February 2024, 4 months ago

Problem/Motivation

Note that, as of 8.8.x, modules can declare their Drupal 8 (or 9) upgrade status ( changelog → , issue #2936365: Migrate UI - allow modules to declare the state of their migrations → ). Since there is no data to migrate from diff-7.x-2.x, diff-6.x-2.x, and diff-6.x-1.x, we should mark those migrations as "finished".

As a site owner migrating my site from Drupal 7 running diff-7.x-3.x to Drupal 8 or 9 running diff-8.x-1.x, I want to migrate configuration from diff, so that my Drupal 8/9 site has the same behavior as my Drupal 7 site.

It appears that 7.x-3.x stores the following data:

  1. Global variables:
    1. - migrations exist as of #5
    2. - migrations exist as of #5
    3. - done since there is no corresponding 8.x-1.x features/settings
    4. - migrations exist as of #5
    5. - done since there is no corresponding 8.x-1.x features/settings
  2. For node and user entities, the following variables:
    1. - done since there is no corresponding 8.x-1.x features/settings
    2. - done since there is no corresponding 8.x-1.x features/settings
    3. - done since there is no corresponding 8.x-1.x features/settings
    4. - done since there is no corresponding 8.x-1.x features/settings
  3. For file fields, a diff_file_field_file_default_options variable that contains the following data:
    1. show_header (boolean)
    2. show_id (boolean)
    3. compare_alt_field (boolean)
    4. compare_title_field (boolean)
    5. property_separator(string)
    6. markdown (string)
    7. line_counter (string)
  4. For image fields, a diff_file_field_file_default_options variable that contains the following data:
    1. show_header (boolean)
    2. show_id (boolean)
    3. compare_description_field (boolean)
    4. compare_display_field (boolean)
    5. property_separator(string)
    6. markdown (string)
    7. line_counter (string)
  5. For each list field type, a diff_list_field_{$fieldType}_default_options variable that contains the following data:
    1. show_header (boolean)
    2. compare (string)
    3. markdown (string)
    4. line_counter (string)
  6. For each text field type, a diff_text_field_{$fieldType}_default_options variable that contains the following data:
    1. show_header (boolean)
    2. compare_format (boolean)
    3. markdown (string)
    4. line_counter (string)
  7. For taxonomy [term reference] fields, a diff_taxonomy_field_taxonomy_term_reference_default_options variable that contains the following data:
    1. show_header (boolean)
    2. show_id (boolean)
    3. sort (string)
    4. markdown (string)
    5. line_counter (string)
  8. For each remaining field type, a diff_{$d7Module}_field_{$fieldType}_default_options variable that contains the following data:
    1. show_header
    2. markdown
    3. line_counter

Proposed resolution

Add migrations.

Declare the finished upgrade path from D6 by creating a migrations/state/diff.migrate_drupal.yml and populating it appropriately.

Remaining tasks

  2. Decide whether we want to migrate field configurations
    1. If "yes", then update the patch to migrate field configurations
  3. Review and feedback
  4. RTBC and feedback
  5. Commit
  6. Release

User interface changes

None.

API changes

None.

Data model changes

None.

📌 Task
Status

Needs review

Version

1.0

Component

Code

Created by

🇨🇦Canada mparker17 UTC-4

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 4 months ago →
    🇨🇦Canada mparker17 UTC-4

    I am happy to report that I was able to use this patch to successfully migrate my Diff module configuration from my drupal-7.99 site running diff-7.x-3.4 to a drupal-10.2.1 site running diff-8.x-1.1.

    Unfortunately, I cannot RTBC this issue because I wrote the patch → . But, hopefully, my success will help other people migrating D7 to D10.

    Unfortunately, however, now that my D7 to D10 site migration is complete, my ability to contribute further to this issue is severely limited, because the D7 site that I had been using to test has been retired. I'll keep an eye on this issue though.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024