pagination Archives | Store Locator Plus®

Location List Pagination

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

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

Location Search Results Patched In Store Locator Plus® v2503.06

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

Store Locator Plus® has two settings related to how many locations are returned when displaying a map. The first setting “Number To Show Initially” is the setting that determines how many locations will be shown when the map first renders. The locations are typically the first n-locations that are closest to the center point of the map unless other setting are adjusted to do something different. The second is the “Number To Show” after a search. This is the maximum number of locations that will be returned when a user enters and address and searches for locations.

Somewhere along the way the location search results settings got muddled and often the number of locations to be shown after a search was ignored. Instead the “Number To Show Initially” was used for both settings. We are not sure exactly when the behavior changed, likely during a huge thousand-lines-of-code update forced upon us by the folks at the WordPress Plugin Directory in the name of “security patches” (don’t even get me started on that topic). Regardless, an attentive user reported the problem along with the steps to reproduce the errant behavior. We were able to issue a patch for that issue and roll it into our March 2025 update on the SaaS platform (plugin users are also impacted).

Locator Performance and Category Improvements

Posted by lcleveland in Map Software

Store Locator Plus® was recently updated to further improve the performance of the application. In addition the user experience for location categories has been updated, addressing shortcomings in the category legend rendering methodology.

Performance Improvements

After implementing security patches requested by the plugin management team over at WordPress.com, we noticed several administrative pages on our plugin as well as on our SaaS service were running slower than usual. After an extensive performance analysis of the underlying code, we were able to isolate the change and improve performance of that module by several orders of magnitude, saving up to 15 seconds per locator settings page request.

Time to execute the subquery improved from approximately 11 seconds to < 1 second. Memory consumption for that routine dropped from 5.4MB / request to 1MB / request.