I just updated drupal today from 8.8.4 to 8.8.5
When I launch after composer update -> drush updatedb :
[notice] Update started: admin_toolbar_tools_update_8001
> [error] The "default" plugin does not exist. Valid plugin IDs for Drupal\geofield\Plugin\GeofieldBackendManager are: geofield_backend_default
> [error] Update failed: admin_toolbar_tools_update_8001compose update has updated geoflied before :
Updating drupal/geofield (1.8.0 => 1.11.0): Downloading (100%)
without asking update db operations...
Do you think it's due to geofield module or admin_toolbar ?
Regards,
Comments
Comment #2
kbrodej commentedHey. Encountered the same issue on 8.8.3 only upgrading geofield module. Was updating from 8.x-1.8 to 8.x-1.11, which failed. Downgraded to 8.x-1.10 same thing meanwhile after downgrade to 8.x-1.9 worked.
Also disabled and completely removed admin_toolbars before I updated.
Changing to Major as page is broken after update.
BR.
Comment #3
itamair commentedit looks definitely an admin_toolbar_tools issue: https://www.drupal.org/project/admin_toolbar/issues/2833121
Please try to follow what advised here: https://www.drupal.org/project/admin_toolbar/issues/2833121#comment-1182...
and confirm ...
Comment #4
rick hood commented[error] The "default" plugin does not exist. Valid plugin IDs for Drupal\geofield\Plugin\GeofieldBackendManager are: geofield_backend_default^ I am encountering what seems like a similar error during a D7 to D8 migration of a content type.
D8 version 8.8.5
D7 Geofield 7.x-2.4
Drush version : 9.7.2
Errors I see when
drush migrate-import --group yig_node_news(The second 2 of the above errors are related to geofield, the top one is not)
I get this error whether admin_toolbar is enabled or not.
The failure is ruing the upgrade_yig_field the config of that is shown below:
Comment #5
itamair commentedThis looks something related to a Drupal core issue.
This seems to face it: https://www.drupal.org/project/drupal/issues/3056633
and the #36 comment looks something to tryout.
Actually nothing might be changed in Geofield in relation to this, because the only @GeofieldBackend plugin present in the module is the "geofield_backend_default" one.
Something further you may try as workaround if #36 doesn't solve and this really does block you (that I hardly believe) is to create a new @GeofieldBackend plugin named "default" into a custom module of you.
Comment #6
rick hood commentedJust reporting that #2 worked for me: "downgrade to 8.x-1.9".
After I downgraded from 1.11 to 1.9 I stopped getting error I reported in #4 above during migrate-import and geofield fields successfully migrated from D7 to D8, in that I now see the field_geofield as part of the field list here: /admin/reports/fields
I have not migrated nodes that contains field_geofield, so not sure if all is well for sure yet.
Comment #7
mjgruta commentedI can confirm that #2 also worked from me "downgrade to 8.x-1.9" without disabling admin_toolbar
Can we say that this is an issue with geofield?
Comment #8
itamair commentedOk ... I see. May be this commit changes are causing the issue?
https://git.drupalcode.org/project/geofield/commit/b214a1e#01ab7f00315fb...
https://git.drupalcode.org/project/geofield/commit/b214a1e#01ab7f00315fb...
May someone rollback those changes and see if everything is fixed by it?
(and even better which between them is causing this ...)
Thanks ...
Comment #9
itamair commentedComment #11
itamair commentedOk got it. Actually the above mentioned Commit brought a better check of the @GeofieldBackend in the GeofieldItem ... but some appropriate handling of exceptions was missing.
Geofield 8.x-1.12 new release fixes all this ...
Good Geofield(ing) to all!
Comment #12
tjtj commentedI have this issue in drupal 8.8.5 trying to update to 1.12. The update works, and all the files in geofield are dated april 17, but update says I still have 1.11 installed.