RESOLVED: Search With Categories, No Results

Posted by lcleveland in Bugs, Closed Bugs

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

User Report (americanbreast)

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/
Read More “RESOLVED: Search With Categories, No Results”

Map Marker Icons AWOL

Posted by lcleveland in Bugs, Open Bugs

Some users are not seeing the proper map marker urls (schmiggitty).

Home Marker

Saved: https://local.storelocatorplus.com/schmiggitty_at_gmail_dot_com/wp-content/mu-plugins/store-locator-le/images/icons/bulb_yellow.png (empty)
Corrected: https://local.storelocatorplus.com/wp-content/mu-plugins/store-locator-plus/images/icons/bulb_yellow.png

End Marker

Saved: https://local.storelocatorplus.com/schmiggitty_at_gmail_dot_com/wp-content/mu-plugins/store-locator-le/images/icons/bulb_azure.png (empty)
Corrected: https://local.storelocatorplus.com/wp-content/mu-plugins/store-locator-plus/images/icons/bulb_azure.png

Dev notes

https://storelocatorplus.youtrack.cloud/issue/SLP-11/Map-Marker-Icons-AWOL

On staging (and production I assume) these both work as expected. The long URL with the customer ID works.

Premier Boundaries shown on Settings

Posted by lcleveland in Bugs, Closed Bugs

Enterprise customers are seeing the boundaries setting even when Boundaries Influences Guess is set to None.

Dev Notes

Premier Admin Tab JS Not Loading

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.

Enabling Reports Produces Fatal Error

Posted by lcleveland in App Updates, Bugs, Closed Bugs

User Report (texas)

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

Dev Notes

A basic typo in the reports module was performing an include in the wrong place.

Resolved in Power 2502.25.02.

Ignore Radius Breaks Search Button

Posted by lcleveland in App Updates, Bugs, Closed Bugs

Search Button Not Working (User: Teivin)

From their website, search button does not fire.

Analysis

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.

Read More “Ignore Radius Breaks Search Button”

SLP Updates 2502.23.XX – 2502.24.XX

Posted by lcleveland in App Updates, Release Notes

Updates

The following issues have been updated starting with the 2502.23 release.

  • Fatal error: Uncaught Error: Undefined constant “MYSLP_DEPLOYMENT_LEVEL”
    • resolved: MySLP Dashboard 2502.23.01
      • Deployed to production 25/02/23 15:20 EST
  • Uploaded files : csv imports, custom map marker images stability
    • resolved: AWS system configuration update on shared EFS mount for uploads folder
      • Deployed to production 25/02/23 18:20 EST
  • Expired Account Notification for Active Users
    • Resolved: MySLP dashboard update on check_activation in the REST_API
      • Deployed to production 25/02/24 01:00 EST
  • MySQL 8 Rank Field Conflict
    • Resolved: Experience update on \SLP_Experience_AJAX::create_string_CustomSQLOrder() to address rank reserved work in MySQL 8.
    • Deployed to production 25/02/24 04:00 EST
  • My Profile Updates
    • Fix Stripe “Test Mode” warning on View Profile
    • Show UID/Site ID on top of customer profile section
    • Remove avatar/image sidebar and move edit profile to the top right of main bar
    • Reformat some headers on the page
    • Deployed to production 25/02/25 12:15 EST
  • Main Theme
    • Show the site tagline on bottom right corner of image
    • Will be used to manually update the version so users can easily see there is an update
    • Deployed to production 25/02/25 12:15 EST
  • Contact Us
    • Show a preview of the extra meta that will be sent to support
    • Add UID/Site ID next to the user name
    • Deployed to production 25/02/25 12:15 EST
Read More “SLP Updates 2502.23.XX – 2502.24.XX”

MySQL 8 Rank Field Conflict

Posted by lcleveland in Bugs, Closed Bugs

Part of the Pins Not Showing Up for uws_at issue.

Rank Field Conflict With MySQL 8

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.

Read More “MySQL 8 Rank Field Conflict”