What specific service(s) from Google Maps should be used to activate the Anahita Locations capabilities? I see several listed, but couldn't figure out which corresponded to the Browser API key & Server API key:
Ok I just checked my own code and you need both browser and server API keys. The server API key is used for obtaining longitude and latitude of an address. The browser key is used in the search view to lookup a place and use it to search within a radius of it.
Good, don't forget a database backup of your 4.2.4 before upgrading to 4.3. There is a big change in both the db schema and file structure. Your db size will be smaller though as well as your codebase size.
@rastin - does the location component require any modifications based on the changes from Google maps? I registered an API key, but i'm not sure how to differentiate between a server/browser key (the above links redirect to the same page).
@robsaric looks like we need to update com_locations, because google is now passing client_id instead of key and they have a new way of issuing keys. Looks like right now our website is using legacy support. I'll put that in the fixes for the next maintenance release. I know our facebook OAuth needs updating too.
Love location as a core feature, so I hope it's not a tough fix. So many practical ways I can think of organizations leveraging it, my hope is to build an autonomous check-in/check-out process when people are on premise in certain locations. Kudos on your work with Anahita - glad to be building with it again.
@robsaric I just checked and not much has changed on google services. Perhaps it would be better if we renamed the Server Key to Geocoding Key and rename Browser Key to Maps API Key. The current locations would work with Google's free service which is quite generous. At this point we aren't going to bother with incorporating with Google's premium service until someone ask us. I don't think any of the Anahita installations are generating the kind of traffic that require Google's Premium account.