Store Locator Plus® Internal Docs
SLP Internal Documentation
In the debug logs , any time super admin would list customers it would throw an error from
\MySLP_User::load() saying could not load blog for user #310.
Turns out this was caused by user 310 (cici) not having an associated site ID as it is a super admin account. Set the fallback to point to the main site (Site #1) when super admin does not have a site id.
Fixed in MySLP Dashboard 2503.04.01 and MySLP Architect 2503.04.01.
The problem here was that some users, older users, were not loading the Premier plugin when switching to the user. This problem ONLY manifests on staging and development servers.
Turns out the wp_blogs domain column MUST match the primary site domain or the user elements that are loaded very early by WordPress will not load properly. That means things that load early like mu_plugins or plugins themselves may not load because they are being only loaded for the primary site for the entire blog. Honestly not a great design from WordPress core to use a PATH from user meta versus looking at the actual user info and pulling related sites that way. Very fragile.
Reworked the MySLP dashboard to detect and reset the domain value in wp_blogs when not on production and the site url is a mismatch. Worked well on dev test. Needs staging test.
The wp_blogs table needs the domains the be changed to match the main URL or get_sites() and get_site_by_path() will not work.
The issue was in Dashboard where the AJAX mode was being forced to ‘load’ (initial look) all the time and ignoring the search mode.
Also SLP was flipping logic of search and load limits with search pulling the initial limit and load pulling the after search limit.
Resolved in Dashboard 2303.05.01 and SLP 2303.05.01
Concur > Cici
RESOLVED by unchecking results setting ” Disable Initial Directory.”
May have been as the result of Map hidden checked off so the first search only made the map appear without listing the results under the MAP
when doing an initial search on the map, the locations do now show up under the map on first search
For example, it's set to ALL by default in the category type, if you enter a zip code and don't change any of the dropdown boxes it will not show the results,
if you select a category or a radius it will show the results under the map.
https://americanbreastcare.com/retailers-near-me/Enterprise customers are seeing the boundaries setting even when Boundaries Influences Guess is set to None.
The Premier Admin JavaScript should be managing that information and hiding the div when the setting is none.
Turns out the JS was not loading due to the page name change with the menu update. It also requires Google Maps to be loaded for this JavaScript to initialize.
Had to add a new SLP Google Maps loader as the existing enqueue_google_maps is really designed for the front end and attached to the ‘google_maps’ handle. A new gmaps handle and enqueue without an init callback is in place to allow for non-user presentation (admin) maps.
While testing the generate embed Directory By State feature for Enterprise users it was noted that clicking on a state generates a “mySLP.POWER.directory” is undefined noted on the generate embed tab.
On the Generate Embed feature the JavaScript console reports the following when trying to fetch the map_marker_tooltip (Enterprise feature) option:
{
"code": "invalid_option",
"message": "Not a valid option slug.",
"data": null
}I have always had the reporting functionality turned on. I noticed it no longer is on and when enabled it displays this code:
Fatal error: Uncaught Error: Class \"SLP_Power\" not found in /var/www/html/wp-content/plugins/slp-power/include/module/admin/SLP_Power_Admin_Reports2022.php on line 37
Error: Class \"SLP_Power\" not found in /var/www/html/wp-content/plugins/slp-power/include/module/admin/SLP_Power_Admin_Reports2022.php on line 37
A basic typo in the reports module was performing an include in the wrong place.
Resolved in Power 2502.25.02.
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.
This report involves two primary issues. The bigger issue is in the MySQL 8 conflict and is being resolved. We are still investigation the Settings Reset issue.
Some user settings (noted below) are not the same as they were originally on the production server after the 2502 update. This is still being investigated.
See https://internal.storelocatorplus.com/settings-reset-to-default/
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.
See https://internal.storelocatorplus.com/mysql-8-rank-field-conflict/
The map is not working, and the pins are not showing up. Please let me know what happened. Thanks! We need to fix this ASAP.
Account: uws_at_*_dot_com
Account Level: Professional
Status: active
Expires: 2025-02-26 04:39:09
Versions:
SLP: 2502.21.01
myslp-dashboard-options: 2502.24.01
slp-premier-options: N/A
slp-power: 2502.18.01
slp-experience: 2502.20.01Some users with active accounts are reporting an expired account notification when viewing the embedded locations on their website.