Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Alpha users will experience troubles in the update from the 8.x-2.0-alphaX to the 8.x-2.0-beta1.
Beta1 has been a great change and improvement in the module: since the Beta1 the module is able to set (and work with) Plugins Options, properly Reverse Geocode, work more correctly (without apparent crashes) in the field Formatters and finally integrate with the Address module.
Due to important schema and configuration changes in its updated model, and the lack of proper update path to this new beta1 version (sorry for this) the simple update of its code from the alpha to the beta1 will certainly produce crashes.
So it is strongly suggested to reinstall the module from scratch and reproduce the your Geocoders setup both in the Fields widgets and in the Formatters.
For those who can't do that, here is a more fluent update path:
- apply the attached patch;
- run application update (from update.php or with $drush updb);
- visit and re-save the Geocoder configuration page (admin/config/system/geocoder), eventually with your plugins options;
- go and set them again all the geocoder settings for the interested Fields Widgets and Fields Formatters;
Everything should work properly from there on, with the new beta1.
If not let us know. We might further amend this patch.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | Screen Shot 2018-01-24 at 11.02.54 AM.png | 59.28 KB | anandangalig |
| #9 | update_patch_from_alphax_to_beta1-2938195-9.patch | 3.41 KB | itamair |
Comments
Comment #2
itamair CreditAttribution: itamair as a volunteer commentedComment #3
itamair CreditAttribution: itamair as a volunteer commentedComment #4
itamair CreditAttribution: itamair as a volunteer commentedComment #5
itamair CreditAttribution: itamair as a volunteer commentedComment #6
itamair CreditAttribution: itamair as a volunteer commentedComment #7
itamair CreditAttribution: itamair as a volunteer commentedComment #8
itamair CreditAttribution: itamair as a volunteer commentedComment #9
itamair CreditAttribution: itamair as a volunteer commentedComment #10
anandangalig CreditAttribution: anandangalig commentedHi there,
I am using the 8.x-2.0-alpha5+6-dev version of Geocoder, but trying to upgrade to beta1. So, I followed your instructions above:
And, yet I am still seeing the
Am I missing something here?
Comment #11
itamair CreditAttribution: itamair as a volunteer commenteddid you run the 4th point ("go and set them again all the geocoder settings for the interested Fields Widgets and Fields Formatters")
for ALL the Fields Widgets and Fields Formatters?
It seems some old (alpha versions) 'third_party_settings' still remains in your Fields configurations.
Comment #12
anandangalig CreditAttribution: anandangalig commentedHey itamair,
I appreciate your response!
I definitely checked my Geolocation field to make sure it was using the appropriate settings:
Still, I am not able to save my Location node. It crashes with a notice:
PS: I would be happy to test things out if it helps your efforts
Comment #13
itamair CreditAttribution: itamair as a volunteer commentedtnx @hoppin_levels for your availability ... but there is nothing more to test on the beta1 and its update process from alpha,
because:
- extensive tests have been run, and if you still experience issues it might depend on your specific configurations;
- the beta2 release has been issued yesterday, with extensive releases notes on the upgrade paths from both beta1 and alphaX;
I kindly suggest you to reinstall the last release of the module, and reset from scratch your configurations (that shouldn't be that much as Geocoder wasn't even able to deal with Plugin Options before the beta 1).
I am closing this, as reviewed from community / outdated.
Please open new issues on any that arise on the new beta2 release (or dev branch) of Geocoder.
Comment #14
itamair CreditAttribution: itamair as a volunteer commentedComment #15
xpersonas CreditAttribution: xpersonas commentedI know this is a closed ticket. But for what it's worth, I've hit the same issue as #12. I have a site with tens of thousands geocoded locations. Debating how to handle this going forward, or if I'll have to continue using alpha indefinitely.
Since opening a new ticket would be duplication, and adding to a closed ticket is frowned upon, I'm not sure what the best strategy is. However, I thought I would add my comment here in case anyone else encounters this and finds a solution.
Worth mentioning, upgrading from alpha5 to alpha8 to beta1... at no point do I have any database updates that need to be made. So while I followed the steps mentioned above, for what ever reason, there was never an update to be applied.