Closed (fixed)
Project:
Views migration from Drupal 7 to Drupal 10
Version:
1.1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2021 at 19:23 UTC
Updated:
29 Oct 2021 at 18:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
greg boggsThis error happens when you export a view for a display type that doesn't exist in D9.
Comment #3
greg boggsAfter improving some error checking in core, I get the migration to run with some results.
[error] A valid cache entry key is required. Use getAll()
[error] The "date_default" plugin does not exist.
[error] The "taxonomy_term_reference_plain" plugin does not exist.
The "taxonomy_term_reference_link" plugin does not exist.
The configuration property display.default.display_options.filters.machine_name.value.location doesn't exist.
(This error repeats for all content types references in views)
The configuration property display.default.display_options.filters.type.value.image doesn't exist.
The "text_plain" plugin does not exist.
The "node" plugin does not exist.
The "taxonomy_term" plugin does not exist.
entityreference plugin does not exist.
The "entity_view" plugin does not exist.
Comment #4
greg boggsRunning this migration as is will be a fatal error that's unrecoverable because once a view is migrated, the site is unloadable.
Comment #5
sundharHi Greg Boggs,
drush migrate:statusin your terminaldrush migrate:import d7_views_migrationComment #6
greg boggsMy site has the standard plugins installed from the standard profile.
Comment #7
greg boggsComment #8
greg boggsI believe some of the plugin names got updated from D7 to D9. But, I'm just guessing. I'll work on this some more. If you're having trouble replicating this because your source database has no broken views in it, create a view in D7 with a plugin you don't have in D9.
Comment #9
damienmckennaComment #11
sundharYes correct Greg boggs,
some of the plugin names not updated from D7 to D9.
so, we re-assign default drupal views plugin for unavailable plugins.
Comment #12
greg boggsYou are a very fast programmer! I'll give it a test.
Comment #13
greg boggsOk! No more null error and 10 of 53 views migrated! There are still a few plugin name mismatches.
This comment might have some useful code in it for us:
https://www.drupal.org/project/drupal/issues/2456259#comment-10543118
The "date_default" plugin does not exist. (This needs to be datetime_default)
The "taxonomy_term_reference_link" plugin does not exist. (I don't know what this should be)
The "taxonomy_term" plugin does not exist. (I don't know about this)
The "node" plugin does not exist. (not sure here either)
The "entityreference_label" plugin does not exist. (this needs to become entity_reference_label)
The "taxonomy_term_reference_plain" plugin does not exist. (This becomes entity_reference_label), I believe.
The "text_plain" plugin does not exist. (Unsure here maybe text_default?)
The configuration property display.default.display_options.filters.type.value.performer doesn't exist. (performer is one of my content types referenced in the view)
Valid plugin IDs for Drupal\Core\Field\FormatterPluginManager are: comment_default, comment_username, comment_permalink, datetime_plain, datetime_custom, datetime_time_ago, datetime_default, daterange_custom, daterange_plain, daterange_default, feeds_item_imported, feeds_uri_link, feeds_item_url, feeds_item_target_entity_view, feeds_item_target_id, feeds_item_target_label, feeds_item_guid, file_default, file_rss_enclosure, file_extension, file_filemime, file_uri, file_url_plain, file_video, file_audio, file_table, file_size, file_link, image, image_url, link, link_separate, list_key, list_default, entity_reference_rss_category, text_default, text_summary_or_trimmed, text_trimmed, user_name, author, entity_reference_entity_view, timestamp, entity_reference_entity_id, entity_reference_label, boolean, number_decimal, language, basic_string, string, timestamp_ago, uri_link, number_integer, number_unformatted, email_mailto
Comment #14
sundharsome of the field formatters not available in D8 or D9
so, we re-assign default drupal field formaters for unavailable field formatters.
Comment #16
sundharComment #17
sundharArgument, & Argument validate type plugins configured.
Comment #18
sundharComment #21
sundharchanges:
default_argument_optionsis only array or null , not a string.pluginListvariable access with$thisComment #23
sundharComment #24
damienmckennaI think "fixed" is the correct status, given changes were committed. FYI the status of any "fixed" issue will automatically change to "Closed (fixed)" after two weeks, so there's no need to manually change it.
Comment #26
sundharThankyou for testing @Greg Boggs,
Thankyou for guidance @DamienMcKenna