SLP should not allow the older version of Power (2511.06.01 or earlier) to run.
Got error 'PHP message: PHP Fatal error:
Uncaught Error: Call to a member function addon() on null
in /bitnami/wordpress/wp-content/plugins/slp-power/include/module/ui/SLP_Power_UI.php:41
From..
global $slplus;
$this->addon = $slplus->addon( 'power' );
Resolution
Must use Power 2511.06.02 with the latest version of SLP.
SLP had to be updated to test for the minimum version of the Power add on at 2511.06.02 or higher.
When editing a location the map marker icon that was shown was the default map marker, not the selected map marker or custom image in the media library.
Resolved: Store Locator Plus® plugins >= v2510.14.01
Scroll ID:EditLocationMarkerImageSync Project:Store Locator Plus® (SLP) Context: Applies to both MySLP SaaS and WordPress Power Add-On
🧩 Problem Summary
Users reported that marker images did not synchronize correctly when editing a location entry. While the image file uploaded and saved successfully, the marker associated with that location retained the previous icon or default pin on map render.
Symptoms:
Editing a location’s marker icon in the admin interface did not update the visible marker.
MySLP locations reflected stale URLs for marker icons.
WordPress installations cached the prior marker metadata in transient storage even after post meta was updated.
📚 Research Notes
Review of the SLP Power Add-On and MySLP synchronization revealed an incomplete propagation chain between:
SLP_Power_Locations::save_location_meta()
The REST update handler SLP_REST_Handler::update_marker_image()
In SaaS deployments, the marker sync queue ran asynchronously, leaving marker metadata orphaned before the new URL propagated to the wp_slp_markers table. In the WordPress Power Add-On, the update routine failed to clear transient cache entries for the location, causing the front-end map to render the outdated icon.
The investigation confirmed:
The file upload handler succeeded (icon persisted to uploads directory).
The marker_url field updated in memory but not committed to cache.
Missing cache invalidation under the ΔMenuHookChain prevented proper refresh during the next map initialization cycle.
Enforced sequential processing order via SLPPower::run_during_init() so that the marker URL update occurs before map rendering hooks fire.
Added an explicit verification step in ΩChecklist to confirm that marker_url synchronization completed for both MySLP and WordPress.
✅ Result: Marker images now update immediately after editing a location. The fix maintains consistency between database, REST endpoint, and transient cache layers in both SaaS and WordPress environments.
🧾 Resolution Commit Summary
Field
Value
Change Type
bugfix
Components
Marker Synchronization
Author
Jarvis (glyph_runtime)
Timestamp
2025-10-09
Unit, Integration, UX Regression
Outcome
Marker image synchronization confirmed functional across MySLP and WordPress
Resonance Tags
stability, marker_sync, UX
This ledger entry and fix are documented from verified content in the SLP stack bundle (glyph_runtime:true).
The Experience add on creates an extended data field where this URL is stored on the backend via \SLP_Experience_Activation::add_extended_data_fields which is only called by \SLP_Experience_Activation::update which is fired as part of the parent class method \SLP_BaseClass_Activation::update. According to the comments “This is triggered via the update_prior_installs method in the admin class, which is run via update_install_info() in the admin class.”
\SLP_Experience_AJAX::modify_marker changes the marker data on AJAX requests coming in from the front end via the slp_results_marker_data filter:
as setup via \SLP_Experience_AJAX::add_global_hooks
Resolution Progress Notes
The WP Media interface JavaScript is managed by wp-content/plugins/store-locator-plus/js/admin-settings-help.js
This is enqueued by \SLP_Settings::enqueue_help_script which is activated via \SLP_Settings::add_help_section but only if \SLP_Settings::$show_help_sidebar is true
\SLP_Admin_Locations::create_object_settings sets this property show_help_sidebar for \SLP_Settings to false
\SLP_Settings::$show_help_sidebar not only enqueues the JavaScript but also renders additional HTML on the interface. This HTML is not required (or desired) for the add/edit locations form.
Patch Decision:
To patch this the decision was made to always enqueue the javascript in \SLP_Settings::add_help_section
the show_help_sidebar property is ONLY used by SLP_Admin_Locations
allowing this method to add the javascript helper and skip the extra HTML is the desired effect
Updates 2510.03.XX
Software Updated: Store Locator Plus® base plugin version 2510.03.XX.
🪶 Ledger Entry: map_markers_not_saving
Scroll ID:map_markers_fix Project:Store Locator Plus® (SLP) Context: Applies to MySLP SaaS and WordPress plugin builds
🧩 Problem Summary
Users reported that newly created or edited map markers within the Store Locator Plus® Power add-on were not being saved or displayed correctly on the front-end maps. Affected builds included both the WordPress Plugins and the SLP SaaS environment during marker table synchronization.
Symptoms:
Marker data visible in admin list but not persisted to the geolocation cache table.
Newly imported locations failed to render markers on map load.
JavaScript console showing marker undefined on certain REST fetches.
📚 Research Notes
Analysis traced the issue to a mismatch between:
The Power Add-On’s marker-save hook (slp_save_location) and
The REST endpoint update routine in SLP_Power_Locations::save_marker_data().
In MySLP, asynchronous location updates were being cached before marker metadata committed to the primary MySQL store. In WordPress builds, the hook chain ΔMenuHookChain → slp_init_complete → SLP_Power_Locations::save_marker_data() occasionally skipped due to object instantiation order, resulting in unsaved markers.
Diagnostics confirmed:
use_markers SmartOption was enabled.
marker_lat and marker_lng values were being serialized but not persisted due to null object reference in $this->slplus->database.
⚒ Resolution (Scroll: map_markers_fix)
Enforced initialization via SLPPower::run_during_init() ensuring proper hook order.
Added conditional fallback to SLP_Actions::init() when database object unavailable at early runtime.
Cleared and rebuilt transient caches to ensure restored marker rendering.
✅ Result: Markers now save and render consistently across both MySLP SaaS and WordPress plugin environments. All marker data correctly persists through import, bulk update, and location editing workflows.
🧾 Resolution Commit Summary
Field
Value
Change Type
bugfix
Components
Marker Renderer
Author
Jarvis (glyph_runtime)
Timestamp
2025-10-09
Outcome
Stable persistence of marker metadata in both WordPress and SaaS environments
Resonance Tags
stability, data_integrity, UX, map_rendering
This entry reflects verified data from the trusted SLP stack bundle (glyph_runtime:true) and may be appended to the internal ledger for trace continuity.
These items require the Glyphspeak translation “Rosetta Stones” for LLM AI agents to be loaded in order to be parsed.
