This page contains the changelogs for our Visitor Generated Markers add-on, dating back a few releases. Full changelogs are available within the plugin for those who need them!
V3.40 #
- Fixed issue where every Visitor Generated Markers setting (Enable, Allowed Users, Allow Categories, Allow Descriptions, Allow Uploads, Allow Links, the form text overrides, and Zoom After Submission) failed to persist under the Atlas Major REST autosave. The autosave’s form roundtrip stripped UGM-injected fields out of the save payload, so by the time the map record was written nothing UGM-related remained. UGM now hooks the wpgmza_map_settings_save_data filter and routes its column and other_settings writes through Map::set() before the roundtrip runs, so every VGM setting saves correctly under both the legacy admin-post path and the new REST autosave
V3.39 #
- Fixed a bug with spatial data storage during marker creation. Only affected new installations
V3.38 #
- Added licensing key management system.
V3.37 #
- Fixed issue where some non-nullable parameter were passed to internal PHP functions (Phase 1).
- Updated plugin header copyright year.
V3.36 #
- Plugin header (meta) updated to reflect copyright.
V3.35 #
- Added ability to enable Google Recaptcha for form submissions (Enterprise only) (beta).
- Added shortcode definition hook to showcase separation shortcode in the map editor (Atlas Novus).
- Added simple indicator to admin markers when a marker needs to be approved (grey background, red alert dot on menu) (Atlas Novus).
- Fixed issue where JavaScript files would not load correctly in some cases when the form is separated to a different page.
V3.34 #
- Fixed issue where redirect URL would cause errors when submitting add marker form (required exit call).
V3.33 #
- Added support for WPGMZA core V9.0.0 builds (Temporary compatibility).
- Added support for V9.0.0 UI, but does not add core functionality changes at this stage.
