For those of you using the Store Locator Plus WordPress Plugins (WPSLP) , here is something to be aware of when migrating and upgrading sites. The correct process is to first MIGRATE the Store Locator Plus installation THEN update the plugins.
Some site administrators are first installing the latest version of the WPSLP plugin stack on the new site THEN bringing over the data. This can cause some settings to start “seeing ghosts”. This will manifest itself in unanticipated ways, such as the map behaving as the old setting is active when it is not set on the admin settings interface.
This particular issue cost me some time when testing new features with the Experience 4.8.3 update coming out later this week. I was playing with the show/hide home marker at startup feature but despite havign unchecked that box it still behaved as if it was enabled (not showing the home marker when the map loads).
It turns out that my settings had not “migrated” from the old-school serialized options to the newer Smart Options architecture. If the old serialized options are still in the data they will take precedence. This is by design to avoid backward compatibility issues.
Normally when you install a newer version of an SLP add on, such as the Experience add on, it will detect the new Smart Option then locate the legacy option to get the value of the setting and delete it. From this point on the Smart Option is the only setting in play. Everything will work by “magic”.
However if you first upgrade the plugins then port your data over from an older system you are also bringing over the add on version data. Since much of WordPress, including our add ons and plugins, rely on accurate version data to trigger events (or more importantly to NOT keep running events over-and-over again that should only happen ONCE during an upgrade) this will skip things like settings being upgraded from “legacy” to Smart Options.
What Is “Data”
For WPSLP users the data that you migrate is both the location data, including all relevant category mapping and extended data table, plus select rows from the WP_Options table that store the settings for the SLP add ons. When migrating your sites first make sure you bring over all the proper data values THEN install the same version of your SLP plugins, then update the plugins to ensure all the data values follow the proper migration path.
This should be the standard process for ANY site migration as many plugins and themes use data migration and upgrade techniques similar to those found in SLP. We did not invent these techniques, in fact much of what we build into our architecture come from WordPress veterans. You will find our methodologies in many other WordPress products.
For MySLP Users