User profile migration should send a warning if image module is disabled

Created on 15 February 2018, over 7 years ago

Updated 21 May 2025, about 1 month ago

Problem/Motivation

A follow up to #2934145: Image field migration plugin in wrong module → . There are two nice descriptions of the problem in that issue, copied here for convenience.

From #29 →

heddn> quietone: one thing to consider is that if you have a d6 fixture that has a profile photo. and on d8 the image module is disabled, then we 1) should error the user migration 2) we should show that image module isn't enabled on d8.
<heddn> quietone: and that means that imagefield or whatever they call it should show up in the missing upgrade paths. that currently doesn't happen. our current d6 test enables image so we don't surface this problem.
<phenaproxima> quietone: I think the way to test this is to simply use those deprecated classes and instantiate them, and ensure that they do, indeed, throw deprecation notices. No?

And from heddn's comment in #36 →

The option to include user profile photos is a config option in D6. And by default it is turned off. If it is turned on, then we want to somehow notify the user upgrading their site that they will loose user profile photos. User profile photos in d6 are unique, because are not managed files. They are just a string location of where the file is located on the disk. However, when that gets sucked into D8, that becomes a managed file. So, the "source" of the data is the user module in D6. The destination is image module in D8. And we want to warn users.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Postponed

Version

11.0 🔥

Component

migration system

Created by

🇳🇿New Zealand quietone

Live updates comments and jobs are added and updated live.

migrate-d6-d8

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 1 month ago →
🇳🇿New Zealand quietone
The Migrate Drupal Module was approved for removal in 📌 [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL Fixed .

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 📌 [12.x] [Meta] Tasks to remove Migrate Drupal module Postponed and the removal work in 📌 [12.x] [Meta] Tasks to remove Migrate Drupal module Postponed .

Migrate Drupal will not be moved to a contributed project. It will be removed from core after the Drupal 12.x branch is open.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024