@tomd39, looking into your issue for future reference, potentially related to a unique server setting.
Just clearing up a few statements …
Cyber Sprocket Labs (CSL):
We’re actually a branch off of that plugin (around that version) a couple of years ago,
Response:
Their plugin is a branch off of 1.2.39.3 (around December of 2010). We’ve made several updates since then, so their plugin will continue to hopefully diverge in its functionality and look. However, theirs isn’t branched off of our more recent versions.
CSL:
Also, that plugin is seriously old. WordPress has changed a LOT in just the last couple of months rendering many plugins useless (happened to us) and causing some newer plugins to be incompatible with older versions of wordpress (also happened to us).
Response:
Ours works with the latest version of WordPress (v3.4.1). Also, we’ve consciously strived to make our plugin as backwards-compatible (down to WordPress v2.5) as possible for flexibility. Even though backwards-compatible, we also are incorporating newer functionality/capabilities for users as well, so that is always a priority.
Additionally, some updates from v1.2.39.3 until now (v1.9.2) have been focused on updating deprecated (old) WordPress plugin API functions with their newer function counterparts in the WordPress plugin API (also helpful for developers that like to use ‘WP_DEBUG’ mode when developing).
CSL:
But the important thing is, do not have both plugins activated at the same time … depending on which plugin gets called first vs last could be detrimental to the locations db (ie our plugin adding columns to the locations table first, then the viadat plugin deleting them — or the other way around).
Response:
Correct, since their plugin uses some of our original functionality + their functionality, functions may still collide, causing errors if both are activated. However our plugin doesn’t delete DB columns.
CSL:
Also, our plugin will only do a db update if it detects that it has been updated (so we’re not trying to change the db on every page load)
Response:
Similarly, ours does the same — DB updates (if any) are only performed on plugin activation or updates.
CSL:
Also, gmaps 3 is NOT compatible with gmaps 2. I noticed that no locations are showing at all on your map. The viadat store locator doesn’t even know to convert gmap 3 map settings to gmap 2 … so you’ll need to reset all your settings in the map to overwrite the gmap 3 settings.
Response:
Correct, not compatible. Yes, go to the Map Designer page, and re-save settings if switching between plugins. Google Maps v3 upgrade has been completed on our end for some time now — coming soon — currently making sure to test it thoroughly with other newly integrated functionality.
