Problem / motivation
We introduced an audit for ID conflicts in #2876085: Before upgrading, audit for potential ID conflicts. This introduced a confirmation / warning in Migrate Drupal UI that existing data will be overwritten.
#2773205: Come up with a design for highly destructive operations in confirm forms is about harmonizing a way how destructive changes are confirmed in the UI. When this issue lands, we should also reflect this in the warning of ID audit conflict accordingly.
Postponed on #2773205: Come up with a design for highly destructive operations in confirm forms
Comments
Comment #2
yoroy commentedThanks for opening this issue!
Comment #7
quietone commentedComment #15
quietone commentedThe Migrate Drupal UI Module was approved for removal in #3371229: [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL.
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 #3463321: Deprecate Migrate Drupal UI and the removal work in #3522601: [meta] Tasks to remove Migrate Drupal UI module.
Migrate Drupal UI will not be moved to a contributed project. It will be removed from core after the Drupal 12.x branch is open.
Comment #17
quietone commentedThe Migrate Drupal and Migrate Drupal UI modules are deprecated and will be removed from Drupal 12. For these modules, effort is now focused on bug fixes and necessary tasks. Therefore, this task is closed as won't fix.
Thanks to all for working on this!