When tracing the settings for active_style_css, it looks like it is loading multiple times… need to investigate later for possible performance improvements.
Call 1
Call 2
Call 3
Call 4
Call 5
Multiple Settings Loading Calls (active_style_css)
Tracking Down Style Changes After Updates
Related to: Prod V Stage Settings Testing
active_style_css settings
RESOLVED: typo in Dashboard access to ‘active_style’ versus ‘active_style_css’ introduced 04/18/2025.
Store in the “private” settings (nojs).
This setting contains a cached copy of the CSS for the style the user has selected.
Prod v Stage Settings Testing
ZIP Code Dataset incorrect address returned
Central PA food bank issue Zip code for Harrisburg PA returns incorrectly or no results , V 2503-06
We are currently having an issue where Harrisburg PA Zip codes 17110, 17123, 17124,17125, 17130 when searched using our MYSLP map to locate food resources is returning a home point that is not in the correct area, 17110 returns to somewhere in Washington state, and the others are showing as out of the country which is also not correct. Please advise how to address this. The map with the issues is located at https://www.centralpafoodbank.org/find-help/find-food/.
Interestingly we had the same thing happen Jan 31, 2024
Google Algorithm issue?
v2503.19 Updates
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.
SLP Updates 2503.06 Release
Versions 2502.26 – 2503.06
Updates
- Smart Option Fetch map_marker_tooltip fails
- Resolved: SLP 2502.26.01
- Premier Boundaries shown on Settings
- Resolved: Premier 2503.03.01 + SLP 2503.03.01
- Premier Plugin Not Activating (Staging/Development)
- Resolved: Dashboard 2503.04.01
- List Customers : Could Not Load User 310
- Resolved: Dashboard 2503.04.01, Architect 2503.04.01
- After Search Number to Show Not Working
- Resolved: Dashboard 2503.05.01 , SLP 2503.05.01
- Map Preview From Main Site
- Added: Theme 2503.05.01, Signup 2503.05.01
- Cron User for Super Admin Deprecated String Use
- Resolved: Customer Maintenance 2503.06.01
- Cannot change Category Selector (Save settings) on staging
- Resolved: WAF issue on staging that is being testing before production, no code changes needed.
Cron : User for Super Admin
Going to Cron : User for Super Admin generates an error.
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/html/wp-content/plugins/myslp-customer-maintenance/include/MySLP_Cron_List_Table.php on line 226
Resolved in
Customer Maintenance 2503.06.01
Performance 2503.06.01
Protected: Category Selector dropdown selected and Saved
Show Map For Logged In Users (Main Page)
Once logged in a preview of the map without generate embed is available by going to the main dashboard page (https://dashboard.storelocatorplus.com) to view the embed on a basic page template.
This page outputs a direct embed script include in the HTML with minimal page processing from within the SaaS platform. This should be very close to the display on a generic website with minimal styling.
You can also find the URL for this preview in the My Profile section under “MySLP Site”.
Resolved: Theme 2503.05.01, Signup 2503.05.01
Pagination Not Working
Customer Report from (cvtsoft : 834.832)
Number to show after search is set to 25.
Enabled Pagination is checked.
Pages are not showing up when results are returned.
Could Not Load User 310
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.
Premier Not Activating
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.