0.3.5 Release

This release is fairly minor. We've tested it with WordPress 4.9 and updated both leaflet-php and wp-geometa-lib, but that's pretty much it.

0.3.2

• Update to wp-geometa-lib 0.3.2.
• Updated internal filter callback function names to match the filter they're for.
• Updated branding to reflect company name change.
• Updated handling if submodules aren't checked out.

0.3.1

I forgot to tag a release for 0.3.0, so here's the changes for both versions.

• Moved core functionality to a library (wp-geometa-lib) so it can be used in other plugins.
• Most of the previous changelog is no longer applicable to this plugin, but to wp-geometa-lib
• Fixed issue that made plugins using WP-GeoMeta as a library to be activated twice.
• Support for custom MySQL functions (User Defined Functions and stored functions).
• Built-in support for some functions which may be useful for working with Lat/Lng distances and bearings.
• Fixed issue where duplicate function names would appear in get_capabilities result set.
• Fixed OSM tiles to not be hardcoded to http://
• Added button to rebuild known spatial function list cache

0.2.2

I'm happy to announce the release of WP-GeoMeta 0.2.2. The main feature of this release is support for separate latitude and longitude fields, including built-in support for WordPress' Geodata standard.

• Added built-in support for the WordPress Geodata standard
• Added filter and action to handle arbitrary lat/lng pair metavalues
• Added documentation for hooks and filters
• Leaflet is now loaded locally instead of from the CDN

0.2.1

• Handle multi-feature GeoJSON correctly in MySQL 5.7 (convert to GEOMETRYCOLLECTION)
• Use ON DUPLICATE KEY UPDATE to combine added and updated postmeta handlers.

Penny Priddy

WP-GeoMeta 0.2.0 is the version where everything I've been hoping to get working in the initial release came together. We've got good spatial query support with sorting, support for a range of MySQL, PHP and WordPress versions and a dashboard so you can see the status of your spatial system.

WP-GeoMeta is largely a tool for developers — in order to store data you'll need to write some code — but as developers write plugins using WP-GeoMeta, this plugin will let users visualize their spatial data with ease.

Changes in this release

• Upgrading no longer truncates and rebuilds the meta tables!
• Fix for joins so user meta should work again (umeta_id vs meta_id key name issue)!
• A beautiful dashboard!
• Plugin activation hooks so that deactivating/activating without upgrading will recreate database tables!
• Translation ready!
• Portuguese translation!
• Code documentation!
• Changed geometry type so that all geometries are stored as multipoint to work across MySQL versions!
• Tested on MySQL 5.1 - 5.7, PHP 5.2 - 7.0 and WordPress 4.1 - 4.6!

Penny Priddy

This is a alpha release of 0.2.0. Version 0.2.0 will be submitted to the WordPress plugin directory.

The main features of this release are:

• Upgrading no longer truncates and rebuilds the meta tables.
• Fix for joins so user meta should work again (umeta_id vs meta_id key name issue).
• A beautiful dashboard!
• Plugin activation hooks so that deactivating/activating without upgrading will recreate database tables
• Translation ready!
• Portuguese translation!
• Code documentation!

Perfect Tommy 0.1.1

Despite being a point release there's a great new feature here, which is that orderby should now work. To get orderby working it was neccissary to take a closer look at how joins were being done which resulted in some cleaner PHP code AND the generated SQL is much more readable, and probably more efficient.

I also discovered and fixed a small bug that was present when upgrading WP-GeoMeta.

Perfect Tommy

This release has two big changes and several small ones:

1. WP_GeoMeta can now work as a plugin or a library. It will intelligently load the most recent version.
2. Single-geometry operations now work in WP_Query meta queries, giving your 51 supported MySQL and MariaDB spatial functions to work with.
3. Additional functions were added to WP_GeoUtil to convert WKT back to GeoJSON and check if something is already GeoJSON.
4. A proper test suite has begun. You must run it when it's installed as a plugin since the tests use wp-load.php.

With these features, and with the additional testing I've done the next steps will be to add support for spatial orderby, and to prepare some sort of UI so that it can be added to the WP repository so people can start to find and use it.