Welcome to Toolset Maps 1.1.1. This is a small bug-fix update.
Improvements
Support for CRED forms submitted using AJAX
CRED 1.7 will bring AJAX to its forms, so you can submit a form and save its data without reloading the page. In most of the cases, the form will be shown again after being submitted, but the fields need to be initialized again.
Toolset Maps 1.1.1 is fully compatible with this, and address fields will get initialized at the right time, so user get the address autocomplete and preview without glitches.
Bug Fixes
Map clusters icons are not shown
Toolset Maps is using a well known cluster script to group markers together. The script included a hardcoded reference to the default marker icons, located in their own repo. It seemed a good idea to keep it, despite the fact that we were indeed bundling those icons with our plugin, because it meant that icon requests were routed outside of the current site (hence improving performance).
But it was not a good idea at all.
Recently, the project moved from code.google.com to github, so all the icons were moved to a new location. For some time, even the examples they offered on their new repository were using the old hardcoded images URL, so no cluster image was shown at all. In fact, they fixed it as late as… May 25.
With this change, we will use our bundled copy of the default cluster icons, so we can be sure they will be rendered.
Google Maps API key is missing on frontend maps
You were already capable of creating and using a Google Maps API key within Toolset Maps, but it was mainly used on the backend, when adding Types address fields and getting geolocation data from a given address.
In the frontend, we were not including such a key, since it is only recommended and not mandatory, so we were getting a console warning Google Maps API warning: NoApiKeys that, even if not blocking or breaking the functionality, was not nice.
Starting on Toolset Maps 1.1.1, when you add your API key in the Toolset Maps settings, it will also be included in the frontend calls. You can use the same API key that you already had.
We will also update our documentation, as you might need to enable both the Google Maps Geocoding and JavaScript APIs.