Problem/Motivation
The widget migration doesn't handle text_textarea_with_summary.
Steps to reproduce
Migrate a field using text_textarea_with_summary. You always end up with a migrated widget with 9 rows, which is the default value in TextareaWithSummaryWidget::defaultSettings(). This happens because we don't actually migrate this setting, and we end up using the default vlue.
Proposed resolution
Add text_textarea_with_summary, but also refactor slightly so that the defaults aren't hard coded, but rather come from the widget defaultSettings.
See also #3108302: [PP-2] Field formatter & widget settings: fall back to default if missing plugin
Comments
Comment #2
douggreen commentedComment #3
douggreen commentedHere's a much simpler patch that changes nothing, but adds the settings for text_textarea_with_summary. ... I figured a minimal change has a higher chance of getting committed ... although I think the optimizations in the first patch are a better solution.
Comment #4
douggreen commentedComment #5
mikelutzThis sounds like a bug, and as such requires a test proving the bug exists and that the fix fixes the issue.
Comment #6
quietone commentedIs this just for D6 sources?
Comment #7
douggreen commentedjust adds text_textarea_with_summary, was missing
Comment #13
quietone commentedThe Migrate Drupal 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 #3522602: [meta] Tasks to remove Migrate Drupal module and the removal work in #3522602: [meta] Tasks to remove Migrate Drupal module.
Migrate Drupal will not be moved to a contributed project. It will be removed from core after the Drupal 12.x branch is open.
Comment #15
quietone commentedMigrate Drupal is removed from the Drupal 12 branch. Only necessary tasks, or critical or major bug fixes will be make on the Drupal 11 branch.
Therefore, this is closed as won't fix.