Verified that the module + migration plugin was installed correctly first:
$ drush migrate:status d7_views_migration
-------------------- -------- ------- ---------- ---------------- ------------- ---------------
Migration ID Status Total Imported Needing update Unprocessed Last Imported
-------------------- -------- ------- ---------- ---------------- ------------- ---------------
d7_views_migration Idle 19 0 0 19
-------------------- -------- ------- ---------- ---------------- ------------- ---------------
However...
$ drush migrate:import d7_views_migration
[error] The configuration property display.default.display_options.filters.type.value.event doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.company_profile doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The "published-notpublished" plugin does not exist. Valid plugin IDs for Drupal\Core\Field\FormatterPluginManager are: comment_permalink, comment_username, comment_default, datetime_custom, datetime_default, datetime_time_ago, datetime_plain, file_video, file_rss_enclosure, file_size, file_audio, file_filemime, file_table, file_uri, file_url_plain, file_link, file_default, file_extension, image, image_url, link_separate, link, list_default, list_key, entity_reference_rss_category, text_summary_or_trimmed, text_default, text_trimmed, author, user_name, number_integer, uri_link, email_mailto, basic_string, number_unformatted, timestamp, language, entity_reference_entity_id, timestamp_ago, entity_reference_entity_view, string, entity_reference_label, number_decimal, boolean (/home/ide/project/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php:53)
[error] The configuration property display.default.display_options.filters.field_result_value.value.Pass doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The "active-blocked" plugin does not exist. Valid plugin IDs for Drupal\Core\Field\FormatterPluginManager are: comment_permalink, comment_username, comment_default, datetime_custom, datetime_default, datetime_time_ago, datetime_plain, file_video, file_rss_enclosure, file_size, file_audio, file_filemime, file_table, file_uri, file_url_plain, file_link, file_default, file_extension, image, image_url, link_separate, link, list_default, list_key, entity_reference_rss_category, text_summary_or_trimmed, text_default, text_trimmed, author, user_name, number_integer, uri_link, email_mailto, basic_string, number_unformatted, timestamp, language, entity_reference_entity_id, timestamp_ago, entity_reference_entity_view, string, entity_reference_label, number_decimal, boolean (/home/ide/project/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php:53)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.rid.value.31 doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.rid.value.31 doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.uid_raw.value.value doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.type.value.payment_exam_info doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.rid.value.46 doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
[error] The configuration property display.default.display_options.filters.field_result_value.value.Pass doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
1/19 [▓░░░░░░░░░░░░░░░░░░░░░░░░░░░] 5% [error] A valid cache entry key is required. Use getAll() to get all table data. (/home/ide/project/web/core/modules/views/src/ViewsData.php:140)
[error] The configuration property display.default.display_options.filters.type.value.course doesn't exist. (/home/ide/project/web/core/lib/Drupal/Core/Config/Schema/ArrayElement.php:76)
19/19 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
[notice] Processed 19 items (1 created, 0 updated, 18 failed, 0 ignored) in 1.3 seconds (870.2/min) - done with 'd7_views_migration'
In MigrateRunnerCommands.php line 350:
d7_views_migration migration: 18 failed.
These seem to all refer to custom content types/fields.
Comments
Comment #2
sundharViews fields from relationships configured.
Views Boolean filters configured.
"published-notpublished","active-blocked" plugins not available in D8. So this plugins resigned to "yes-no" plugin
Comment #4
sundharComment #5
webchickHey, awesome, now we're up to 2/19!
It's probably not really possible to troubleshoot this without more info, so I'll try spinning off individual issues.
Comment #6
sundharComment #7
sundharHi webchick,
Last update not configured filter plugins. now its configured.
I think now we're up to 16/19 views will be migrate.
Comment #9
webchickHmmm. Actually, now it's just sitting there hanging after I run
drush mim d7_views_migration:Whereas the other day stuff started happening immediately.
Nothing in Watchdog.
If I try and check migration messages, I get:
Any ideas..?
(I SUPER appreciate your willingness to help; sorry for being such a n00b. :D)
Comment #10
webchickOther details that might be relevant?
Comment #11
sundharHi webchick,
I have checked it out,
And figured out something.
If we run
drush mmsg d7_views_migrationwithout run any migration its throw exception.Try this command
This will also throw the same exception.
Comment #12
sundharWebchick, Will you share your
drush mimerrors?Comment #13
webchickAh-ha. Right you are. I do get the same mmsg error after uninstalling the module entirely. Filed #3212411: Calling drush mmsg before migrations have run causes a pile of errors for that, since I couldn't find an existing issue about it.
After first running into #2868762: D7 Migration failing on d6_filter_format and #3144216: [SOLVED] D7->D8 Migration failing on filter_formats v. filter_format... :P
And hangs here...
Well at any rate, seems like the "drush mim is hanging" problem has nothing to do with Views Migration since it's currently still uninstalled... I will do some Googling.
Comment #14
webchickHm. After manually importing d7_user_settings and then re-running things, I get:
(the import command still hangs for d7_views_migration, however...)
...is this what you're looking for?
Comment #15
webchickI still have no idea what's going on with my install, which is still hanging... but I tried downgrading to Drush 10.3.6 in case that was the issue and it worked for a second before stalling, so I can confirm that yes, we are officially down to 16/19. WOOHOO! :)
Comment #16
sundharHi webchick,
In this module takes more process to map the real table of the field.
Example:
In D7, If the user & node entity has the same field like field_name. This two fields data has been stored in the same table field_data_field_name. But In D8 site It store two different tables node__field_name and user__field_name. Table mapping takes long process.
We try to reduce the loopings in this functionality.
So that's the problem.
Comment #17
sundharHi webchick,
Function calling methods changed & Argument plugins configured in new vesion.
Comment #18
sundharLater found why its hanging on, checking field relationship till relationship is none,
In D7 some views version using
'relationship' = 'none'another some views using'relationship' = ''.Comment #20
webchickAwesome, thanks so much for all of your work!
Today, after a fresh install with Drupal 9.1.8, Views Migration 1.1.2, and Drush 10.5.0:
Might once again be something on my end. I'll take a poke around.
Comment #21
webchickOk, in doing some rudimentary debugging, that problem seems to be legitimate, and is coming from the "page_2" display on my "UserSearch" view. Here is an export of the D7 view.
You first get " [warning] Invalid argument supplied for foreach() ViewsMigration.php:858" and then the barf of errors.
If I end up figuring out _why_, I will spin-off a sub-issue for that. But maybe this helps give a pointer somehow?
Comment #22
sundharHi webchick,
I review the code & find that issue on checking relationships.
Comment #24
webchickThat patch seems logical, but for some reason I'm still seeing (more or less) the same problem, even with the tip of the 1.1.x branch:
Comment #25
webchickOk. After some more rudimentary debugging, I think this one is being caused by the reports_partners view. Export attached.
In it, there's a relationship to a field_relationship_tid which presumably doesn't exist yet, since this is the first and only migration I've run. So probably a fair enough problem to have, but maybe some extra hardening is in order to give folks an idea of what to do.
Comment #26
sundharI analyse your exported view. Its more helpful to find the problem.
This issue occurred by Views Relationships uses All dispalys option. It store the relationships data in default display options. If using 'This block (override)' and it store the relationships data in 'related display(page_1,block_1,etc...) display options'
Comment #28
webchickOH OH OH!! THINGS ARE HAPPENING!!! :D (Using tip of 1.1.x branch)
These seem like incredibly legit problems!
ALSO!
YEAAAAHHHHH!!! :D
Thank you SO much, @Jeya sundhar! Let me see if I can get to the bottom of that one remaining failing view and we can close out this sucker.
Comment #29
webchickOk this time the failure seems to be coming from the courses_list view, block_1 display. Export attached.
Comment #30
webchickAlso ran into this: #3213864: Imported views not shown on admin/structure/views? ... not sure if this is a "me" problem or an "everyone" problem, though.
Comment #31
webchickHm. Also puzzling... #3213870: Views migration complains about roles not existing despite them existing
Comment #32
webchickOk, sweet. With the commit of the roles patch (thank you!), error output is now down to:
Comment #33
sundharHi webchick
Install draggable views module for courses_list view & then migrate the views.
And I remove non existing fields in views.
Comment #35
webchickOh my, isn't it EXTREMELY late for you? :O Thank you for the help! Though, hm. Even applying that patch, and with draggableviews enabled, still same issue:
Comment #36
webchickMore specifically, it seems to be choking on the "reverse_field_track_node" relationship in the courses_list view.
Comment #37
sundharHi webchick
I have analyse the Courses_list view nearly 4 times.
Last I have understood your content fields & field_types.
Drupal7 has lot of modules and I learn about references in D7. finally i find that problem is node_reference fields aren't migrated to Drupal 9.
I think you are using references module for track & course field.
entity_reverseplugin working with term reference.Comment #38
sundharReferences Table field changes
Comment #40
sundharHi webchik
Sandbox: References Migration supports to migrate node_reference to migrate entity_reference.
Comment #41
webchickOOOOH exciting! :D However, even installing this sandbox module I seem to be getting the same issue.
Hmmm. Did I do something wrong? Any other info I can give you?
Comment #42
webchickFor the record, also tried:
SO. CLOSE. :D
Comment #43
webchickOh wait! That's a NEW error!
This time it's about "file_uri" type of field, which is on the "field_badge_image_fid" relationship.
So a file reference field? On the User Certifications view. Which is... here!
Comment #44
sundharComment #45
sundharHi webchick :D
In the user_certification view has user reference Its field_name end with field_name"_uid" in Drupal 7 but when we migrate references its changed to field_name"_target_id" then File:Path field is not available in Drupal 8. Before 2 commits I had disabled the removeNonExistFields function, Now its enable for filtering non exist filelds in view display.
Comment #47
webchickSO sorry for the delay! Thank you so much for working on this!!
Mostly the same problem. Hmmm.
Sorry, I am running out the door and don't have time to debug this right now, but will post more debugging info by Friday.
In the meantime... I wonder if there's a way to at least surface in the error messages which view + field/relationship/etc. is the one that's problematic? That seems like it would allow faster debugging of the problem. (Currently I'm trawling through various variables in XDebug and can never remember where to find the view name so it always takes 10+ minutes. 😅)
Comment #48
sundharI am sorry webchik, I forgot to update the reference_migration patches.(This sandbox module only need for 9.1.x) (Migrate Drupal 7 node/user reference fields supports >9.2.x ) Now reference_migration sandbox updated. once recheck it.
Wow, so great are you using XDebug. My TL Pravin_ajaaz already told about this XDebug method. But my lap has just 4GB RAM. so I didn't use this. But In my case using print_r & vardump is the better debugging method.
Comment #49
sundharComment #50
webchickSadly/Unsadly, due to a job change, I no longer have access to the data that I was basing this analysis on. :)
However, your amazing analysis and debugging accomplished a WHOLE bunch of good for the module, that will help others with similar Views in the future. I'm comfortable marking this fixed. Thanks again. <3