Posted on

SLP Zoom Controls

Store Locator Plus 4.4.36 has an adjustment for zoom controls that addresses a change in the Google Maps API.

In older releases of the Google Maps JavaScript API the rendering engine would often render the map with one-or-more pins on the edge of the map. These pins would often be inaccessible as they fell under the Google map controls. Sometimes the info bubble would be cut off. The Store Locator Plus JavaScript interface would adjust for this by pulling the zoom level back one level on anything other than the 3 widest views (global zoom levels) which were not affected by the edge-of-map anomaly.

SLP Google Pins Cut Off (older Google API)
SLP Google Pins Cut Off (older Google API)

In the continued Google Maps JavaScript API improvements the edge-of-map pins stopped happening. It wasn’t until recent customer feedback that we realized this had changed. In Store Locator Plus 4.4.36 the zoom tweak is no longer auto-adjusted for non-global views of the map. Store Locator Plus will now use the Google default bounding boxes which keeps all pins within the map bounds. The info bubbles also auto-adjust to bring the entire bubble into focus on the map to prevent text from being cut-off.

SLP Google Normal Pins
SLP Google Normal Pins
Posted on

Store Locator Plus v. 4.3.18 update, Google Maps JavaScript API information

Google Maps JavaScript API Geocoding issues, Part 2

Following up on the recent updates to Store Locator Plus and the Google Maps APIs, the Store Locator Plus developer found some major changes to the Google Map query structure that is effecting query returns when the geocoding function intiates from the SLP search. SLP 4.3.18 provides support to alleviate this issue while an alternative solution is investigated. For more information on how Google Maps Javascript Application Programming Interface (API) works with Store Locator Plus and the issues please watch Lance’s video, Google Map JavaScript API part 2.

Store Locator Plus 4.3.18

The recent patch to SLP is intended to prevent the endless looping of the geocoding query from your search form to Google. The endless loop may manifest itself as a result of a Google server glitch, and may freeze up your interface, preventing your map from loading at all. This was an issue when the Google server was down and coming back with no results found for locations, thus initiating the query over and over. The recent development is occurring due to changes to the Google Map API and is discussed in the developers video above. 4.3.18 also fixes the default email link that was incorrectly rendering under the results section. Additionally, 4.3.18 adds support for renaming extended data field slugs to improve the Extended Data Manager add-on interface. See the SLP Change Log and the developer’s short video for more information.

Thank you to those forum posters who are working with us when reporting any issues and providing the SLP support team with their Plugin environment.

Change Log