Location List Pagination

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

Location Import Fixed (WordPress plugins only)

One of our users reported an issue where their location import stopped working after updating the Power add on to a new release. This was never an issue for our SaaS users given the strict nature of the directory configuration, WordPress version, and PHP version running on that platform.

If a user downloads a new version of the Power add on (a zip file) and already has a prior version of the slp-power.zip file in the download directory on their laptop, the browser may create a new file named slp-power-2.zip without direct notification or confirmation it has done so.

If the user uploads this file to the WordPress installation it will create a NEW installation of the Power plugin at ./wp-content/plugins/slp-power-2/. This may or may not reside alongside a version of the older installation at ./wp-content/plugins/slp-power/ which is the standard installation path.

Even if a user deactivates and deletes the existing Power add on , which is best practice, before uploading the new slp-power-2.zip , the new path for the plugin will not match the prior path.

This causes the JavaScript for location imports included in the Power add on to not be loaded.

While some users may still encounter this issue depending on how their servers are configured (WordPress version, PHP version, and other variables can impact how the plugins behave).

There is a patch out in the latest version of the Store Locator Plus® WordPress plugin v2511.05.01 and Power add on v2511.05.01 that make this process less fragile. That will alleviate issues on some server configurations, but best practices should still be followed when updating plugins.

Premier users can login to their account at the SLP WordPress plugin store, scroll to the bottom of the page and click the downloads link to get the latest versions of all SLP plugins.

Tired of dealing with plugin version issues, server issues, and Google API billings? Try the Store Locator Plus SaaS edition. It works with WordPress, no plugins required, as well as most other online presence services including Squarespace, Wix, Weebly, and others.

Editing Categories and Location Import/Export

During the month of June we have been working on several patches for both Store Locator Plus® SaaS platform and WordPress plugin users. We have also performed multiple tweaks to improve performance including leveraging some PHP 8 specific performance tweaks.

SaaS User Editing Categories

All SaaS users received an updated earlier this week patching the category edit functionality. Buried deep in the new settings history tracker was an issue that prevented categories from being edited and saved after they were created. 

Since our SaaS platform still runs most of the core features through the old-school WordPress core code it inherits a lot of garbage including the very outdated category editor (we are hoping to replace that someday with a modern React style editor). Part of the garbage that is inherited with that 15-year-old janky interface is the fact that the only way to add extended attributes to categories, like our custom map markers and icons, is to store the extra metadata in the WordPress options table. It just so happens that is the MAIN settings storage area.

We missed that when adding our settings history feature to the SaaS plugin. Thus, any time a user saved their category updates for their locations the WordPress engine would fire the “hey, we just saved some settings” trigger. Our code was expecting actual settings not category data and didn’t handle it well.

That has been patched and is already deployed for all SaaS users.

Read more: Editing Categories and Location Import/Export

Location Import/Export

Users that have installed the Power add for WordPress may have issues importing and exporting locations. After a week of tracking down this issue, which only happens on SOME WordPress sites, we have found that the WordPress user settings for administrators can be corrupted. This causes the admin interface to not load properly. That causes the JavaScript for the Power add on (and likely lots of other plugins, not just ours) to not be loaded.

This is NOT corruption caused by our plugin code. We are not sure what triggers it, but in some case a WordPress install will start thinking it is a “multisite” install and attaches either the network_admin or user_admin attribute to a logged in user session. When that happens the “do this when an administrator is on the Store Locator Plus® admin pages” does not fire. 

What did we do to fix this? In our test installations where we could reproduce the problem we went to our administrator user profile , changed the website URL (you can change ANY data — might be a good time to update your passwords) and saved. After we re-saved our user profile with a new website URL or password everything came back as expected.

How did the user admin meta get out-of-whack? We may never know.

Bottom line, if you location imports or exports are broken try re-saving your user profile in WordPress.

This issue does NOT impact SaaS users.

Post image by Lance Cleveland