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”

Pins Not Showing Up for uws_at

Posted by lcleveland in App Updates, Bugs, Closed Bugs

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.

Settings Reset To Default

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/

Rank Field Conflict With MySQL 8

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/

User Report

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.01
Read More “Pins Not Showing Up for uws_at”

SLP SaaS Updates : 2411.01 To 2502.23

Posted by lcleveland in App Updates, Release Notes

Server Platform Architecture Updated

The core platform has been moved from a proprietary server cluster on Amazon EC2 instances that were self-managed to a container-based platform. This will allow for seamless software updates with minimal downtime during the update process. The previous platform would go into maintenance mode and be unavailable for users for up to 20 minutes when a major software update was performed. The new platform switches software in less than 2 minutes, often with no noticeable downtime for users.

Underlying Core Software Updated

PHP is running on version 8.3.2 which improves security and performance.
WordPress, a core element of the SaaS platform, is running 6.4.5 which improves security and fixes multiple bugs related to user session stabilization.
MySQL, the core database, is running version 8.x which is faster for most queries.

Locator Styles

Changing the styles of the Store Locator Plus® interface has been updated to a completely new design. This feature replaces the previous Settings | View | Locator Style interface and now resides in its own top level menu as “Style”.

The SaaS version of Store Locator Plus® will show a preview of the newly selected interface after the settings have been updated. The page will refresh to ensure the encapsulated CSS styling that goes with the new settings is loaded in its entirety.

The new Style Interface for Store Locator Plus® starting in 2025.

This interface replaces the legacy interface shown below:

The previous locator style interface.

Pages : New Feature

While the generate embed interface helps preview what the map interface may look like on your site, it is often difficult to see the full impact as the page sizes are limited. Users can now create their own test pages to try out a wider variety of page layouts with the embedded map.

The new pages menu appears in the sidebar when a user is logged in.

While we do not restrict the pages at the moment, this is NOT meant to be a full location services or public web hosting option. Please do not direct your general website visitors to pages published on the Store Locator Plus® SaaS platform. This feature can change at any time and is not guaranteed to always be visible to the general public.

Stripe Payment Processing Update

The Stripe payment processing engine has been updated to version 3, a major upgrade — two in fact, since the core Stripe engine was initially implemented in the Store Locator Plus® SaaS platform. This will enable us to extend the subscription renewal and modification system and include automated billing for overages while providing more detailed reports on customer usage in a future release.

Add SaaS Signup Page On SaaS Dashboard

Add a SaaS Sign up page using the latest Stripe V3 JavaScript API on the SaaS dashboard site. This is mostly to enable rapid turn around testing on staging and development servers but will also provide for newer UX updates to the sign up process as well as better account and subscription management through Stripe in the future.

Dev Notes

  • 2411.xx releases
  • 2412.xx releases
    • Moved all Store Locator Plus menu entries to reside as top-level entries to reduce the number of user clicks to perform an action. This is the start of the redesign to use a modern React-style top-level design and move away from the shackles of the very outdated WordPress PHP driven interface design.
    • Ensure the SaaS edition initializes the customer info when starting data I/O, moving the SLP database init to the post WordPress set_current_user hook
  • 2501.XX releases
    • Fixed an issue with WPSLP generating a null error when performing a new install.
    • Final removal of all WPML references in SLP, Experience, and MySLP Dashboard.
    • Force Load JavaScript is not longer supported as it was designed to allow SLP to work with malformed or poorly written WordPress themes.
    • Info tab on SaaS is removed, it is the main SLP logo menu item now that shows info.
  • 2502.XX releases
    • Long latitude/longitude entries (over 14 characters total, more than 9 after decimal) would not save, this has been resolved. Maximum lat/lng resolution is 9 precision or about 11cm.
    • Settings|Search Radius Behavior was showing duplicate entries for Professional and Enterprise users. This was due to an internal code object being duplicated, impacting memory consumption and performance. This has been resolved.
    • Settings | Tools – minor ux update to align the import/export settings buttons.

Add Location With Lat/Lng Does Not Save

Posted by lcleveland in Bugs, Closed Bugs

Fixed in SLP 2502.19.01

Reproduction

Got to Location Details | Add
Name: Test
Latitude: 32.8393273773774
Longitude: -79.85448363551637

Code Tracing

In \SLPlus_Location::MakePersistent

$dataTooWrite = 
array (
  'sl_store' => 'Test',
  'sl_address' => '',
  'sl_address2' => '',
  'sl_city' => '',
  'sl_state' => '',
  'sl_zip' => '',
  'sl_country' => '',
  'sl_latitude' => '32.8393273773774',
  'sl_longitude' => '-79.85448363551637',
  'sl_tags' => '',
  'sl_description' => '',
  'sl_email' => '',
  'sl_url' => '',
  'sl_hours' => '',
  'sl_phone' => '',
  'sl_fax' => '',
  'sl_image' => '',
  'sl_private' => '',
  'sl_neat_title' => '',
  'sl_linked_postid' => 0,
  'sl_pages_url' => '',
  'sl_pages_on' => '',
  'sl_option_value' => '',
  'sl_initial_distance' => 943.4293089967016,
)

Error Logs

Database insert error:

WordPress database error: Processing the values for the following fields failed: sl_latitude, sl_longitude. The supplied values may be too long or contain invalid data.

Resolution

The problem is that Google is falsely creating GPS coordinates on the Google Maps interface likely in an effort to thwart data harvesting.

The latitude/longitude combination 32.8393273773774, -79.85448363551637 represents 14 places after the decimal.

9 places after the decimal represents a length on the earth’s surface of approximately 110 microns.

Anything after the sixth decimal place, about 11cm is fairly useless for general map locations.

In Store Locator Plus 2502.19.01 the \SLP_Admin_Locations_Actions::add_location() method was updated to format incoming latitude and longitude data to present no more than 9 places after the decimal. This is necessary to fit the data into a 14 character data field which is stored as a string.

This can include values with negative representation including “-180.123456789”.