2503.19 updates were kept to a minimum while testing the new GitHub projects , issue tracking, and code integration processes for project management.
The updates for this release are not user-facing, testing should be for baseline functionality.

Store Locator Plus® Internal Docs
SLP Internal Documentation
2503.19 updates were kept to a minimum while testing the new GitHub projects , issue tracking, and code integration processes for project management.
The updates for this release are not user-facing, testing should be for baseline functionality.
From their website, search button does not fire.
If Settings | Search | Radius Behavior is set to “Do not use” it will trigger the problem.
The backend code in the Experience codebase has a bug that is not using a properly initialized AJAX class. This is a side effect of the PHP upgrade.
It is resolved in the 2502.25.01 release of Experience.
Part of the Pins Not Showing Up for uws_at issue.
While changed settings is an issue and still needs to be investigated, the main culprit here is the upgrade from MySQL 5 to MySQL 8. Servers were upgraded to MySQL 8 as the prior release we no longer supported. Amazon RDS services dropped support for the older MySQL version with a hard cut off in the fall of 2024. As such we were forced to upgrade MySQL; A good thing overall but it involved a lot of data query and code updates and testing.
MySQL added the work “rank” as a reserved word. This conflicts with our Professional an Enterprise feature that has used rank as a standard field name for a decade. Turns out we missed on location where we need to specially mark this field in the data query.
Any sites that have, or had, a location with the rank field set may experience an issue with initial location results not appearing.
Resolved in the 2502.24.01 update to the Experience module.
Testing underway 25/02/24 13:00 EST.
On production as of 25/02/24 14:45 EST.
Location categories provides a way to place categories into groups that can be filtered via the administrative tools and on the front end user experience.
Managing categories is provided by the Power add on.
The underlying technology uses the built-in WordPress category management system. Some of the core functionality of adding, removing, and assigning categories is managed by WordPress and thus requires additional testing whenever WordPress posts a new release.
The Power add on extend this default functionality to provide custom administrative and user interactions with location categories.
WordPress 6+
Store Locator Plus 5.13+
Power Add On 5.11+
The use cases are based on the WordPress plugins. Most of the processes described within apply to the MySLP SaaS implementation as well.
WordPress environment is setup and configured including activation of the following plugins
In addition map service (Google API keys) should be in place and some locations should be added to the system.
A page has been created with the [slplus] shortcode present and the map is rendering properly.
Users are logged in as a WordPress administrator (the process will be slightly different for SaaS users).
Create a location category and attach it to an existing location.
The new category should appear on the category list on the page.
The category is assigned to the location and appears on the location table.
The search form for the map should show a category drop down.
Only the locations that match the search criteria, including the category filter, should be shown.