Problem/Motivation

On #2886609-50: Migrate translations for D6 i18n taxonomy 'localized' terms, I tested migrating a D6 site into D8, as follows:

a) Downloaded latest drupal 8.6.x dev tgz file from drupal.org (easier than git for me for Drupal core at the moment).
b) Installed Drupal from the UI, using the Minimal install profile, and configured site without Update module.
c) Turned on Seven/Bartik themes, and a bunch of core modules: Migrate, Migrate Drupal *UI, Migrate Drupal UI; all 4 multilingual modules; Toolbar; plus some my migrated d6 site would need: Taxonomy, Views, a bunch of field modules, custom blocks and custom menu items. Note at this point there are no content types or vocabularies in my D8 database, and no node or term data.
d) Went to /upgrade, clicked Continue, and entered the site database/files information from a D6 site that I wanted to migrate. This site has 2 languages, and some translated nodes and taxonomy terms in it.
e) Got this warning on the next page:
Warning when migrating

Problems with this:

  • The warning says "WARNING: Content may be overwritten on your new site", but I have no content to be overwritten.
  • In order to continue, I have to click a button saying "I acknowledge I may lose data. Continue anyway". This sounds like a legal disclaimer, and again, I have no data in my site to lose.
  • (minor) The more information link text says "Upgrade handbook" but we don't really use the word "handbook" to refer to community documentation pages any more. Or at least, we shouldn't. The page title is "Known issues when upgrading from Drupal 6 or 7 to Drupal 8" anyway, and it's in a Guide that is called "Upgrading to Drupal 8". So the link title should probably be something more descriptive, like "known issues with migrations page".
  • The page it takes me to https://www.drupal.org/docs/8/upgrade/known-issues-when-upgrading-from-d... does not have current information, as it refers to work in progress on an issue that is actually marked Closed (fixed). Anyway, it tells me "If you are executing a complete upgrade at once and you are performing the upgrade to an empty Drupal 8 site, everything should be OK.". Yes, it should - I don't have any data to conflict with.

So, this warning is totally unnecessary, and is incorrect.

Proposed resolution

Don't warn the user about ID conflicts if there is no data to conflict with in the database.

Remaining tasks

Make a patch and test it.

User interface changes

No warning about data loss if there is no data to lose.

API changes

Probably not.

Data model changes

Probably not.

Comments

jhodgdon created an issue. See original summary.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone commented
Title: Data loss warning in D6 to D8 migration when I have no data to lose » Add audit of translation content
Issue tags: +Needs change record, +Migrate API

The screenshot shows that it is 'translated content' that is causing the warning message to be displayed. This is because translation are not yet handled by the auditor. There was an issue for this that has not yet been worked on, closed that one as a duplicate #2905759: Before upgrading, audit for potential i18n ID conflicts

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

joachim’s picture

joachim commented
Issue tags: +Needs issue summary update

If #3259581: Update migration warning 'There is translated content of these types' is closed as a duplicate of this, then the IS needs updating for #6 - the warning about translated content shouldn't be shown when it's not true.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Issue tags: -Migrate API +Migrate critical

Updating tags for #3565085: Drupal core issue tag cleanup,

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.