The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.In rc2, upgrading from Drupal 6 site doesn't work. The upgrade process gets stuck at 49%. See the attached screenshot. After refreshing the page, following Notices were reported:
Notice: Undefined offset: 1 in Drupal\text\Plugin\migrate\cckfield\TextField->processCckFieldValues() (line 51 of core/modules/text/src/Plugin/migrate/cckfield/TextField.php).
Notice: Undefined offset: 1 in Drupal\text\Plugin\migrate\cckfield\TextField->processCckFieldValues() (line 51 of core/modules/text/src/Plugin/migrate/cckfield/TextField.php).
Notice: Undefined index: contact_category in Drupal\migrate_upgrade\Form\MigrateUpgradeForm->buildConfirmForm() (line 916 of modules/migrate_upgrade/src/Form/MigrateUpgradeForm.php).
Notice: Undefined index: contact_category in Drupal\migrate_upgrade\Form\MigrateUpgradeForm->buildConfirmForm() (line 917 of modules/migrate_upgrade/src/Form/MigrateUpgradeForm.php).
I went to /upgrade again and restarted the upgrade the process. This time it worked fine. There was one Notice at the end:
Notice: Undefined index: upgrade_option in Drupal\migrate_upgrade\Form\MigrateUpgradeForm->submitConfirmForm() (line 1023 of modules/migrate_upgrade/src/Form/MigrateUpgradeForm.php).
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | d6_to_d802_stuck_log_after_refresh.png | 314.6 KB | rcodina |
| #6 | d6_to_d802_stuck_log.png | 343.83 KB | rcodina |
| #6 | d6_to_d802_stuck.png | 246.95 KB | rcodina |
| Screen Shot 2015-10-23 at 10.27.59 AM.png | 294.95 KB | neeravbm |
Comments
Comment #2
neeravbm commentedComment #3
neeravbm commentedComment #4
mikeryanThis "upgrade getting stuck" sounds like you hit the problem at #2606466: Migration of uid 1 breaks batch upgrade process - the migration of uid 1 (the admin account) breaks the batch API the next time it goes to fully refresh the page (new request). Can you try again using that patch (and if it works for you, report it in that issue? Or if for that matter it doesn't work...)?
I haven't seen those notices. #2324649: Migrate text fields correctly based on their text_processing setting. has changed the file with the text notices, but I'm guessing what you're seeing as line 51 is
Suggesting that you have a field with widget_type 'optionwidgets_onoff' where there's only one allowed_value, or at least maybe the allowed_values aren't separated by newlines? Can you tell if you have such a field and what the allowed values should be for it? Also, since there were significant changes in the text field handling in #2324649: Migrate text fields correctly based on their text_processing setting. (just committed this Monday), could you try with the latest -dev of core (or RC3 when it's out, maybe today) and see if that makes a difference?
The contact_category notices point out that the hard-coded $moduleUpgradePaths needs to add source/destination modules for that migration. I'll add that in for now, still hoping we can address #2569805: For Drupal migration, identify the source module and not keep having to do this manually.
I did see the upgrade_option notice once, need to look into that.
Comment #5
mikeryanAdded issues #2608316: Missing module mappings for migration(s) and #2608318: Notice for undefined index upgrade_option. As for the text issue, I'm guessing that would probably be a core issue to deal with whatever your allowed_values configuration is, but waiting to see if you can offer details on the field triggering this.
Comment #6
rcodinaI also got upgrade process stuck at 88% upgrading from D6.20 to D8.0.2. So I refreshed the page and it continued till 100%.
I think maybe the issue is related with taxonomy term import from D6. However, I guess this process takes a lot of time and may seem its stuck and its not. So I think it's just a matter of patience, not an issue. It just imported correctly all taxonomies and linked them correctly to nodes.
Comment #7
mikeryan