Store Locator Plus® continues to upgrade the outdated 2002 style PHP interfaces that were inherited with our WordPress framework to modern React interfaces. Our latest updates focus on replace the mix of old JavaScript and PHP code on the Location Import interface.
Updated locations import interface
Separate Upload / Import Progress Meters
The new interface has a clear separation between the file upload process with its own progress meter and the import processing. The import is designed to separate the file upload process from the file import process. The import process is asynchronous, which means the user can go to other parts of the app to continue working, then come back at any time to the import page and see how their location imports is progressing.
Updated import progres meter.
Sidebar: For smaller files with a couple of hundred of locations this may not seem important. For our customers that are uploading files with 35,000+ locations it is critical that the file upload process is distinct from the processing of the file. While uploads that large can take up to an hour, depending on the user’s connection speed, the import is more challenging. For our customers that do not use our SaaS platform, they can be running on slower smaller web hosting platforms. Importing 35,000 locations will break those servers as they run out of memory or “time out” during the 2-3 hour import process (our SaaS servers are far larger and faster than most self-WordPress sites; if you are doing large location imports you may want to switch to our SaaS platform). The Store Locator Plus® import process manages this by detecting pending timeout issues and keeps track of the current line being imported. If a timeout is imminent the import will stop on the last record processed and queue up a new import request to pick up the process where it left off. That allows the memory and processor to “take a breath” – preventing server crashes and getting those large import files fully loaded without additional user intervention.
Remote File Imports
Remote file location import interface
Remote file imports allow user to load CSV files that are hosted on a different server. This is often used for companies with a separate CMS or inventory management system that exports their locations on a nightly basis to a private URL. The remote file imports can be setup to read those remote files on a regular basis, keeping the list of locations in Store Locator Plus® in sync with external services.
This section now has its own interaction panel with related messages and processing details.
Recent Uploads – new feature
Recent location import files
A new Recent Uploads section allows users to see the list of recent CSV file imports. From here the files can be re-imported (without uploading), downloaded, viewed, or deleted.
Viewing the file shows the details of the most recent import as well as a summary of the first 20 records in the file. To view the complete file, the user can download the CSV file.
Uploaded location file details.
CSV Processing Settings
The shared CSV processing settings are shared between the uploaded CSV, remote processing, and re-import actions. The setting can be accessed via the settings icon on the top right of the Import panel.
Location Import Settings
Load Locations From WordPress
This feature is now part of the Professional and Enterprise accounts and is included in the Import tab as a new section.
This feature allows users to load locations from a WordPress site they own that has the Store Locator Plus® plugin installed.
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.
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.
