Store Locator Plus® May Updates

Posted by lcleveland in Google Maps, Map Software, MySLP SaaS, Release Notes, Store Locator, Store Locator Plus, WPSLP

Several minor updates have been made to the Store Locator Plus® application that was released this week. As always, our SaaS platform users do not need to do anything to receive the updates.

WordPress users will need to manually download and install the Store Locator Plus® base plugin to get updates since the WordPress plugin directory is not properly distributing updates at this time. Once upgrading to the latest version, the main Store Locator Plus® plugin will route directly to our update servers and start receiving inline updates (no manual download zip file, activate process).

The following items are included in this update…

Store Locator Plus® WordPress Plugin Updates

As noted in the opening of this article, the main Store Locator Plus® plugin for WordPress now pulls updated directly from our official update server. If you are on a version older than 2604.06.01, you will need to login to your our WordPress plugin store and manually download then install the new version. Note: Our SaaS platform users do NOT need to do this, head on over to the Store Locator Plus® Dashboard and login.

Make sure your .zip file does NOT have a different name as that can confuse WordPress. The file name should be store-locator-plus.zip. If you end up with store-locator-plus-2.zip (or any other version), WordPress will install multiple copies of the plugin as it assumes the prefix before the .zip extension is a unique plugin name. Not our design, that is legacy WordPress for you.

Another reason to think about replacing your self-managed WordPress plugin install with our fully managed SaaS version. (As an added incentive – we have more features coming to SaaS only with plans for better user interaction reports coming for all plan levels , joining our Settings History feature that was added for all SaaS users in Q4 2025.)

Google Map Domains (Country Codes)

In one of our recent updates, we extended the list of country codes that are supported to match the full list of 100+ countries available on Google Maps today. Two things happened with that update which we missed on release which are now fixed.

First – our Map Domain (country) selection was ordered by country codes (the 2-letter code assigned to each country) which did NOT match the order of the text displayed on the drop down menu. That meant that “United Kingdom” with a NEW country code of “gb” appeared in the middle of the “Gs” on our list. That’s not right! Easy fix to sort our dropdown list by displayed text not country codes. This was a non-functional change but makes the user experience work as expected.

Speaking of United Kingdom, apparently in the ancient history of the Google Map Domains there was an alternative country code of “uk” versus the standardized code of “gb”. Apparently Google Maps stopped supporting “uk” as a country code, which meant that any of our users that had “United Kingdom” selected as their map domain started having issues. Their country code of “uk” was not longer found, and Google did the obvious thing… use the first country code on the list of “Ascension Islands” to try to show the map and addresses. In the most recent update, Store Locator Plus® will automatically convert anyone with the “uk” code to the “gb” code on first launch of the plugin. SaaS user accounts have already been recitified.

Google Maps Latitude/Longitude Links

Another minor update related to Google and the map interface is the link in Location Details. Under each location is the latitude and longitude of the location. Google changed their map search URL which resulted in those links bringing up a 404 page. This has been resolved and once again show the location on a separate Google Maps window. This allows for a quick sanity check that the encoded latitude and longitude align with the Google Maps public service.

Image by Lance Cleveland from Pixabay

Location List Pagination

Posted by lcleveland in Google Maps, Map Software, MySLP SaaS, Release Notes, Store Locator, Store Locator Plus, WPSLP
Field and mountains: Location List Pagination

Store Locator Plus® Late February 2026 Updates

The late-February 2026 maintenance window focused on stability and cleanup across the Store Locator Plus ecosystem—especially around Locations import UI reliability, continued PSR-12/PHP 8 compatibility cleanup, and some Google Maps loading improvements.

Release window covered in this post: February 19, 2026 through February 26, 2026.

Pagination Fixes

The most important fix for this release is addressing pagination for lists of locations. A feature available to Enterprise SaaS users and Premier subscription users is the ability to page location search results. This allows for a smaller list of locations to appear on the user-facing location search and map interface with standard next page, previous page buttons. The functionality stopped working at some point in the past. This was brought to our attention by our clients and has been patched in this release.

Locations Import: Fixes for “Broken Tabs / Corrupted Admin UI”

Another important fix in this window was addressing an issue where HTML output from the Import tab could become malformed and then “bleed” into other admin panels. In practice, that could cause subsequent tabs or sections to render incorrectly or behave unpredictably.

Updates included:

  • Fix for rogue/corrupt HTML output in the Locations import UI.
  • Hardening work in Power add-on import to prevent Import tab output from impacting adjacent tabs.

If you’ve ever seen the Locations admin screen behave strangely after viewing Import, this release is aimed squarely at eliminating that fragility.

Google Maps Loading Improvements (Async + Dependency Fix)

We continued improving how Google Maps assets are enqueued and loaded—especially for admin-side usage—so maps can load more efficiently while reducing edge-case failures.

Highlights include:

  • Async script loading support for Google Maps enqueues (including appropriate URL attributes).
  • Defensive checks to ensure required keys are present before attempting to enqueue certain map assets.
  • Dependency fix related to Google Maps script loading (to prevent mis-ordered enqueues or missing prerequisites).

This is part of an ongoing effort to make map loading more consistent across WordPress admin screens and reduce the “works on one screen but not another” class of problems.

Payments / Subscription Workflow Patch (MySLP)

On the MySLP Payments side, this window included a small but important stability fix to prevent a case where subscription detail retrieval could return a WP_Error unexpectedly (stemming from return declaration/typing cleanup work).

Net effect: fewer “mysterious” failures when subscription details are being fetched and surfaced in the UI.

Compatibility & Maintenance: PSR-12 / Cleanup / Version Bumps

As usual, there were a number of housekeeping improvements that help keep the codebase modern and easier to maintain:

  • PSR-12 and typing cleanup in several components (core + Premier).
  • Removal of unused methods/properties to reduce surface area and future confusion.
  • Version bumps across multiple plugins/add-ons as part of packaging these updates.

What You Need To Do

SaaS users (dashboard.storelocatorplus.com): nothing—these updates are part of ongoing platform maintenance work.

WordPress plugin users: if you are impacted by Locations Import UI oddities or admin rendering glitches, you’ll want to update to the latest Store Locator Plus / add-on releases that include the late-February fixes.

If you run into anything unexpected (especially around Imports or Google Maps loading), contact us—those reports are extremely helpful for prioritizing the next round of stability patches.

About This Article

This article was written by an AI agent and refined by a human.

The AI agent was running the openai-codex/gpt-5.2 model with deeper context hints provide by the Store Locator Plus® Qdrant database. The database evaluates the code changes, commit notes, and R&D documentation on our internal documentation site. It generates a basic summary of what changed since the last production release.

Image by Studio Lichtfang from Pixabay

Store Locator Plus® February 2026 Updates (SaaS)

Posted by lcleveland in Map Software, MySLP SaaS, Store Locator, Store Locator Plus
store-locator-plus-february-2026-updates

The February 2026 update for the Store Locator Plus® SaaS platform is now live. This release continues our ongoing work to modernize the administrative experience by replacing legacy PHP-driven interfaces with a faster, more consistent React-based UI.

Release window covered in this post: January 31, 2026 through February 18, 2026.

My Profile Gets a Modern React Refresh

The primary focus of the February release was a major update to the My Profile area of the SaaS dashboard. My Profile is one of the most frequently used “account management” sections of the app—so improving clarity, performance, and messaging here tends to pay off immediately.

Highlights in this update include:

  • React-based interface improvements that provide a cleaner, more modern user experience for profile and subscription management.
  • Improved notifications and messaging throughout the My Profile workflow, including better guidance when something goes wrong and clearer confirmation when actions succeed.
  • More consistent subscription/card update behavior, including better handling of edge cases where payment processor details may be missing or incomplete.

This work also helps set the foundation for more React-driven administrative updates throughout 2026, as we continue moving away from older WordPress-admin-era UI patterns.

Contact Us Page Updated (React Form)

Alongside the My Profile work, we also refreshed the Contact Us experience inside the SaaS platform with a modern React form. In addition to improving the look-and-feel, this change reduces overhead by ensuring the Contact Us components load only when needed.

Performance & Stability Improvements Behind the Scenes

While most of the visible changes are centered around My Profile and Contact Us, this release includes several important “under the hood” updates that make the dashboard faster and less fragile:

  • Reduced unnecessary loading of Customer Profile and Contact Us components across unrelated admin pages.
  • Improved behavior during WordPress heartbeat/AJAX cycles to prevent duplicate processing and avoid extra subscription-related calls.
  • Cleanup of legacy assets (older CSS/JS/tooling) to keep the codebase leaner while preserving the older interfaces that still power Locations and Generate Embed.

Subscription & Billing Workflow Refinements

Several updates in this window focused on improving the reliability and consistency of subscription management—especially around card updates and cancellation/renewal edge cases.

  • Improved “Update Card” logic with shared, standardized handling of card details and user-facing messages.
  • Better fallback behavior when Stripe returns an empty message (or an error) so you get clearer feedback in the interface.
  • Fixes for subscription cancellation/renewal edge cases to ensure payment method/source information is preserved properly.

These changes are designed to reduce confusion and eliminate “silent failures” during common billing actions.

What You Need To Do

SaaS users: nothing. These updates are already deployed on dashboard.storelocatorplus.com.

If you have suggestions or run into anything unexpected, please contact us and let us know. Your feedback directly helps us prioritize which parts of the dashboard get modernized next.

About This Post

This post was written via OpenClaw running on an NVIDIA DGX Spark while connected to the ChatGPT 5.2 Codex LLM. It used vector database information which is configured to ingest nightly updates from our Internal R&D documentation site as well as the git code repositories. This is combined with web access via Brave API which helped it read the latest articles on this site to set the tone and writing style. A non-AI biological agent named “Lance” read the results, added some images, and added this last paragraph.