Update the history interface on the profile page. Use a newer React based interface, simplify the data and make it easier to follow.
This will likely include updates to various logging of events changes.

Store Locator Plus® Internal Docs
SLP Internal Documentation
Update the history interface on the profile page. Use a newer React based interface, simplify the data and make it easier to follow.
This will likely include updates to various logging of events changes.

While testing Power : Imports Are Not Working a warning was noted in the JavaScript console.
🔲 Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading
A new feature to track settings history.
These are the option names we want to keep track of.
This is a code consistency/standard thing.
Why different options?
MySLP uses a lot of SITE_ID_CURRENT_SITE.
looks to be related to get_network_option() calls.
Some places use BLOG_ID_CURRENT_SITE.
Mostly, but not exclusively, for swith_to_blog() calls.
Both are defined in the Docker composer and both are set to 1.
Looks to be a legacy thing where there was (is?) a plan to have a network (the SITE ID) of blogs (the blog ID). In our case they will be one and the same.
Show the current selected “Locator Style” in text on the selector header so we don’t have to scroll down to look for it.
