Ftw.geo

Latest version: v1.4.2

Safety actively analyzes 688775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

1.1

----------------

- Use message IDs and defaults in error message translations.
[lgraf]

- Improved exception handling when doing geocoding on save.
Deal with network errors and any other unhandled exception,
and display meaningful messages for all cases.
[lgraf]

- Fix tests according to the new features
[mathias.leimgruber]

- Display a status message when automatic geocoding didn't yield any results.
[lgraf]

- Make sure to import exceptions we check for from the googlev3 geocoder
after switching to V3 geocoding API.
[lgraf]

- Deal with multiple results for automatic geocoding.
When automatic geocoding on save for a content item results in
more than one match, choose the first one and display a message
to the user that he might want to change it.
[lgraf]

- Remove api key usage. The geopy GoogleV3 Geocoder does not
implement an api key.
[mathias.leimgruber]

- Use google map api V3 of geopy 0.95.
See -> http://plone.293351.n2.nabble.com/collective-geo-GBadKeyError-when-geocoding-w-geopy-td7563845.html
[mathias.leimgruber]

1.0

----------------

- Added import step to uninstall Products.Maps using quickinstaller.
[lukasg]

- First implementation.
[lukasg]

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.