I think #3381981 → is a better solution.
#4 works. Drupal 10.2.6 Paragraphs Browser 1.1.0.
brayn7, that works. Thanks!
Sorry, i got migration plus confused with migration tools.
Looks like this does not omit the server url, it sets it to an empty string:
"parameters":{"server":{"url":""}}
Which gives me this error:
URL constructor: /<my-server-id> is not a valid URL.
When I manually delete the parameters section above, it works. So I think url needs to be completely omitted.
Cribbed from migrate_plus.
https://git.drupalcode.org/project/migrate_plus/-/blob/6.0.x/src/Plugin/...
Fix formatting in the issue description.
bander2 → created an issue.
I can confirm that this issue does not exist in Drupal 10.0.9. So, maybe this is due to a change in 10.1.
Possibly related to 3340020.
for me, the workaround is to install libraries first and then keyboard_shortcuts.
It's working, thanks!
I am still getting this with your migration on a fresh install:
Drupal: 9.5.3
PHP: 8.0.27
Drush: 9.0.27
Migrate Source GraphQL: 2.03
Running drush mim migrate_morty -v gives me:
In Results.php line 54:
[GraphQL\Exception\QueryError]
Expected type String, found Morty.
drush migrate:status -v produces this output.
[error] Could not retrieve source count from migrate_morty: Expected type String, found Morty.
[error] Could not retrieve source count from migrate_morty: Expected type String, found Morty.
[error] Could not retrieve source count from migrate_morty: Expected type String, found Morty.
--------------- -------- ------- ---------- ------------- ---------------
Migration ID Status Total Imported Unprocessed Last Imported
--------------- -------- ------- ---------- ------------- ---------------
migrate_morty Idle N/A 0 N/A
--------------- -------- ------- ---------- ------------- ---------------
The error itself comes from the endpoint. I believe that we are intending to send a query like this:
query Query {
characters(filter: {name: "Morty"}) {
results {
id
name
}
}
}
But instead are sending:
query Query {
characters(filter: {name: Morty}) {
results {
id
name
}
}
}
I don't know what the difference could be between your environment and mine that would account for this.
bander2 → created an issue. See original summary → .