GEO my WP v4.0 beta 5 is now ready.
Click here to download GEO my WP v4.0 beta-5.
If you are a license key holder, you can download the beta-5 version of GEO my WP's extensions from your account page.
- Also check out GEO my WP v4.0 beta-1, v4.0 beta-2, and v4.0 beta-3, and v4.0 beta-4 for more info about the developement of GEO my WP v4.0.
Additional information about this beta version will be posted soon...
GEO my WP v4.0 beta 4 is now ready and hopefully will be the last beta version before the final release.
Click here to download GEO my WP v4.0 beta-4.
If you are a license key holder, you can download the beta version of GEO my WP's extensions from your account page.
- Also check out GEO my WP v4.0 beta-1, v4.0 beta-2, and v4.0 beta-3 for more info about the developement of GEO my WP v4.0.
The main changes in this beta version are the form data importer and the new sub-navigation of the Settings page. Both features mentioned in more detail below. Other than that, there was more code cleanup, PHP 8.0 errors/notices, and other improvements and minor bug fixes.
The structure of the form builder had changed quite a bit in GEO my WP's v4.0. Because of that, editing an existing form after updating to GEO my WP v4.0 would result in missing options/settings. And so far, with the previous beta versions of GEO my WP v4.0, users had to edit their existing forms after the update so they would work properly.
Now, with GEO my WP v4.0 beta-4, there is an internal importer that should import the form data from the structure of GEO my WP v3.0 to v4.0. So the exsiting forms on your site should work properly after updating to GEO my WP v4.0. You don't need to do anything regarding that. GEO my WP should import the data automatically and silently.
However, I still recommend editing your existing forms after the update to v4.0. Not only to verify that all the settings are in place, but also to check out the new form settings that were introduced in GEO my WP v4.0.
A new sub-navigation was added to the settings page of GEO my WP to try and better organize it and to prevent confusion. The settings of GEO my WP and the different extensions are now grouped together and will show in a sub-navigation item under the main extension or the "component" they belong to.
For example, instead of having a menu item in the main settings page of GEO my WP for both the "Members Locator" and the "BP Xprofile Fields Geolocation" extensions, now the settings for the BP Xprofile Fields extension are placed in a submenu item under the Member Locator menu item.
One additional change that took place was to the Location Form of the Edit Post page in the admin's dashbaord. Instead of loading the Location Form directly into the page, it is now placed in a pop-up modal that opens with a click of a button.
I made this change mainly to try and keep the Edit Post page as clean as possible when it first loads. With additional plugins and theme options, the Edit Post page can quick become messy and diffcult to work with.
So now, in the Location tab of GEO my WP, you should only see the current address of the post and a "Edit Location" Button.
add_filter( 'gmw_edit_post_location_form_modal_disabled', '__return_true' );
With the official release of GEO my WP v4.0, I will also release a new extension - Meta Fields Geolocation.
Using the Meta Fields Geolocation extension, you can sync specific meta fields ( custom post field for posts, user meta for users and BP members, etc... ) with GEO my WP. Once synced, whenever that meta field is updated ( or deleted ) with an address on your site, GEO my WP will geocode that address and update it in GEO my WP database table.
Using this feature, you ( and the users of your site ) will be able to update GEO my WP's locations from the front-end ( or back-end ) of your site using custom forms or custom functions where the address is saved in meta fields. That's instead, or in addition to using GEO my WP's location form in the "Post Edit" page of the dashboard or using the Location form provided with the Members Locator or Users Locator extensions.
If you have one of GEO my WP access passes and would like to test the Meta Fields Geolocation extension, contact me via the support page and I will provide you with a beta version.
With the release of the previous beta version, GEO my WP v4.0 beta-3, I announced the upcoming release of the PeepSo Geolocation extension that integrates GEO my WP with the PeepSo plugin. At the time, The PeepSo Geolocation extension integrated with PeepSo Members only. The integation was not yet avaialble for PeepSo Groups.
However, after working closely with the PeepSo team members ( who were very responsive and happy to help ), I was able to add the integration for PeepSo Groups.
Listed below are the live demo pages for the PeepSo Groups Geolocation. To log-in, use demo for both the username and the password.
I plan to release the PeepSo Geolocation extension with the official release of GEO my WP v4.0. However, If you have one of GEO my WP access passes and would like to test the PeepSo Geolocation extension, contact me via the support page and I will provide you with a beta version.
Please use the comments section below for feedback, questions, and bug reports regarding GEO my WP v4.0 beta 4.
Thank you.
GEO my WP v4.0 Beta-3 is finally here along with a new beta version for all of GEO my WP extensions.
Click here to download GEO my WP v4.0 beta-3.
If you are a license key holder, you can download the beta version of GEO my WP's extensions from your account page.
- Also check out GEO my WP v4.0 beta-1 and v4.0 beta-2 for more info about the developement of GEO my WP v4.0.
GEO my WP v4.0 beta 3 introduces a few new integrations and a couple of new ( minor ) features. But for the most part, the focus of v4.0 beta-3 was on bug fixes, code enhancement, code cleanup, and improving the integration between GEO my WP core plugin and the premium extensions.
The first new integration in this version is between GEO my WP and the PeepSo plugin. GEO my WP enhances the PeepSo Members Directory page with proximity search features, allowing filtering members based on location and displaying the location of those members on a map ( see demo ).
Also, when used in combination with the WordPress Users Locator extension, GEO my WP adds a location tab to the Member's profile page to allow members easily add and update their location ( see demo ), and you can use the forms builder of GEO my WP to create custom members mashup maps and proximity search form ( see demo ).
Please note that at the moment the integration works with PeepSo members only. Integration with PeepSo Groups is not available at the moment, but I am working together with the PeepSo team to try and make GEO my WP integration with PeepSo Groups as well.
This demo site showcases the different features of the integration between GEO my WP and the PeepSo plugin.
This integration requires the PeepSo plugin, GEO my WP core plugin, and GEO my WP's PeepSo Geolocation premium extension. The WordPress Users Locator extension is options for additional features.
The PeepSo Geolocation extension is currently in beta and not yet available to purchase or download directly from GEO my WP's website. However, if you have a valid license key for any of GEO my WP's access passes and wish to test the beta version, please contact me via the support page.
- Visit the PeepSo official website for additional information regarding the PeepSo plugin.
Another new integration of GEO my WP is with the Youzify plugin.
Since Youzify uses the BuddyPress plugin, GEO my WP integrates directly with both the Members Directory ( see demo ) page and the Groups directory page ( see demo ) of the Youzify plugin. In addition, new search results template files that match the Youzify template files were added to the Members Locator and Groups Locator forms of GEO my WP. So you can now use GEO my WP's forms builder to create custom members and groups search forms that match the look of the Youzify plugin ( see demo ).
This demo site showcases the different features of the integration between GEO my WP and the Youzify plugin.
This integration requires the Youzify plugin, GEO my WP core plugin, and GEO my WP's BuddyPress Members Directory Geolocation extension and the BuddyPress Groups Locator extension ( if you wish to integrate GEO my WP with Groups ).
- Visit the Youzify official website for additional information regarding the Youzify plugin.
Another new integration of GEO my WP is with the BuddyX theme ( both the Free and the Pro version ). The BuddyX theme can be used with either BuddyPress or BuddyBoss and no matter which plugin you chose to use, GEO my WP fully integrates with it.
GEO my WP integrates directly with the Members Directory page ( see demo ) and the Groups Directory page ( see demo ) of the BuddyX theme.
GEO my WP also added new search results template files that match the look of the BuddyX theme. So you can now use GEO my WP's forms builder to create custom Members and Groups locator search forms that will match the look of the BuddyX theme ( see demo ).
This demo site showcases the different features of the integration between GEO my WP and the BuddyX theme.
This integration requires the BuddyX theme ( either the Free version or the Pro version ), GEO my WP core plugin, and GEO my WP's BuddyPress Members Directory Geolocation extension and the BuddyPress Groups Locator extension ( if you wish to also integrate GEO my WP with BuddyPress Groups on your site ).
- Visit the BuddyX official website for additional information regarding the BuddyX theme.
The integration with BuddyBoss was already introduced in GEO my WP v4.0 beta-2. However, beta-3 enhances this integration and takes care of some styling issues and other bug fixes and conflicts.
GEO my WP integrates directly with the Members Directory page ( see demo ) and the Groups Directory page ( see demo ) of the BuddyBoss theme.
GEO my WP also added new search results template files that match the look of the BuddyBoss theme. So you can now use GEO my WP's forms builder to create Members Locator and Groups Locator proximity search forms that match the look of the BuddyBoss theme ( see demo ).
This demo site showcases the different features of the integration between GEO my WP and the BuddyBoss theme.
This integration requires the BuddyBoss theme and Platform, GEO my WP core plugin, and GEO my WP's BuddyPress Members Directory Geolocation premium extension and the BuddyPress Groups Locator premium extension ( if you wish to integrate GEO my WP with Groups ).
Please use the comments section below for any feedback, questions, and bug reports regarding GEO my WP v4.0 beta 3.
Thank you.
It took a bit longer than I expected, but GEO my WP v4.0 beta 2, and the first beta of ( most of ) the Premium Extensions are finally ready for testing.
You can download GEO my WP v4.0 beta 2 from here.
- Check out this post to learn more about the first beta of GEO my WP v4.0.
GEO my WP v4.0 beta 2 comes with a few additional features in comparison to the first beta, but the main focus was to make it better integrated with the premium extensions.
While working on the different premium extensions, I went over every single file of every extension to see where it can be improved. In that process, I cleaned up a huge amount of redundant code, modified the existing code to take advantage of the new classes and functions of GEO my WP v4.0, enhanced the search queries of the different extensions for better performance, and improved other areas of the extensions. This had resulted in a better file/code structure, and a noticeably much smaller code across the different extensions and GEO my WP. Code that will be much easier for me to maintain going forward. In addition, some new features were added to some extensions as well as a very few features were deprecated.
Integration of GEO my WP with the BuddyBoss Platform and Theme had been on my to-do list for a while and is finally ready. New "Buddyboss" search form and search results template files were added to the different Members Locator and Groups Locator ( requires the Groups locator extension ) forms. It is included with the Members Locator forms of GEO my WP core plugin, as well as with the Global Maps, and the AJAX Forms extensions. The new Buddyboss template files inherit their styles from the Buddyboss theme which makes GEO my WP forms look like part of the theme.
One of the new features added to the search form is the "Filters Modal Box". This is a popup modal box that displays some of the form filters inside it. This feature can be useful when having many filters in the search form and we wish to keep the search form minimal. Enabling this feature will display a "Filters" button inside the search form that will toggle the popup modal box.
The "Smartbox" feature of the Premium Settings extension does no longer support jQuery Chosen, and instead it now support the fSelect library. That is, in addition to the Select2 library. So you can now choose between fSelect or Select2 for the Smartbox feature.
The above are only a few of the changes that took place in GEO my WP v4.0 beta-2 and the first beta of the extensions. However, a lot had changed in the back-end, front-end, and under the hood. So I might still update this post with additional changes and information. Until then, you are welcome to test the new versions and find out for yourself.
You can download GEO my WP v4.0 beta 2 from here.
You can download the beta versions of the premium extensions from your account page ( an active license key is required ).
Note that the only extensions that are not yet ready for GEO my WP v4.0 are the Nearby Locations and the Multiple Locations extensions. I am going to start working on those extensions this coming week.
Please note that I rewrote all the premium extensions almost from scratch. And many changes took place in GEO my WP v4.0 beta 2 as well. Because of that, bugs are expected. So please use the comments below to report any bugs, typos, styling issues, or any feedback you would like to share.
Thanks,
Eyal
GEO my WP v3.2 is a major release that improves some of the location search queries, locations function, and the geocoder function. You can download GEO my WP v3.2 beta 1 beta 2 beta 3 from here.
Back on June of this year Google introduced its new Maps Platform. One of the changes to the new platform is that a server Maps API key is now required for server-side geocoding.
Until now, GEO my WP required a single Maps API Key, which is a browser key ( client-side ). This API key is still required and is responsible for displaying maps, directions, and client-side geocoding. However, this key does no longer work for server-side geocoder. GEO my WP has a few functions ( usually being used with custom scripts ) that use the server-side geocoder, and those functions now fail to geocode a location.
In GEO my WP v3.2 there is new input box in the Settings page for a server-side API key. You need to create a new Google Maps API key and set it as a server key. In this tutorial you can learn how to create both browser and server API keys. In step 9 you can see how to set up a server key. Once you generated the server key, navigate to GEO my WP Settings page -> Maps & Geocoders tab, and enter it in the server key input box.
You can now test the your Google Maps Server API key to make sure that it is set up and working properly.
After generating your Google Maps Server API key and adding it in GEO my WP Settings page, navigate to the API Testing tabs of GEO my WP Tools page ( dashboard-> GEO my WP -> Tools -> API Testing tab ) and click the 'Test Server Key' button. The plugin will then run the server-side geocoder and try to geocode a default address.
If geocoding successfull you will see a success message. Otherwise, you will see a detailed error message. The error message should help you understand what is wrong with the setup of your server API key.
Other changes in GEO my WP 3.2 include improvements to the search queries and location functions, new functions, new hooks, various bugs, and coding standards.
A few of the premium extension, which are listed below, require an update in order to be compatible with GEO my WP 3.2:
If you have a valid license key you can downlaod the new version of the extensions from your account page.
Your feedback on GEO my WP 3.2 is greatly appreciated.
Not too long since the last major update of GEO my WP ( GEO my WP v3.0 ), and the next major release, v3.1, is already here.
For the last couple of months, since the announcement of the new pricing modal and usage limit of Google Maps API, I have been busy working on adding an alternative to Google Maps. Mainly to provide a solution for users who might end up paying for Google Map services because of the new usage limit. But also to expand GEO my WP and make it possible to use any maps provider in the future.
GEO my WP 3.1 includes new geocoding and mapping classes that can be extended to work with different geocoding and maps providers. Out of the box, GEO my WP now supports Google Maps, and LeafLet as the maps engine, using OpenStreetMaps for layers and geocoding services.
It is important to understand that the features differ between maps providers. Not all the features that Google Maps provides, OpenStreetMaps provides as well. So features like address autocomplete, Map Types and Map Styles, are not yet available with LeafLet and OpenStreetMaps. If you decide to use LeafLet instead of Google Maps, some features will not be available.
Same as with maps providers, there is also a difference between Geocoding providers. Some geocoding providers are more accurate than others, have different coverage areas, and some are faster and more reliable than others. Switching between different geocoding providers in GEO my WP might affect the user experience and performance when adding or updating a location, and when searching for locations.
To choose the maps provider, navigate to the dashboard -> GEO my WP -> Settings -> Maps & Geocoder tab, and select the maps provider from the "Map provider" drop-down menu. Once you choose, you will see the settings for the specific maps provider that you chose.
Note that the Google Maps API key input box moved under the new Maps & Geocoder tab.
As always, I first release a major update as a beta and I need your help testing it. You can download GEO my WP 3.1 beta 1 from here.
GEO my WP's premium extensions were also updated, and are now compatible with GEO my WP 3.1. You can download the new version of the extensions from your account page.
You can use the comments below to post any questions, feedback and bug reports related to this update.
Thank you,
Eyal
GEO my WP beta 7 beta 7.0.1 7.0.2 is now ready for testing, and hopefully will be the last beta version before the official release. You can downlaod it from here.
At this point, all of GEO my WP official extensions are compatible with GEO my WP 3.0. They were all redone from scratch, with improved code, bugs fix, and new features.
Listed below are the extensions and the versions which are compatible with GEO my WP 3.0 beta 7 beta 7.0.1 7.0.2. You can download them from Your Account page:
If GEO my WP 3.0 beta 7 beta 7.0.1 7.0.2 is the first beta you test, please carefuly read the post on v3.0 beta 1 and v3.0 beta 2 to make sure the update goes as smooth as possible.
Your comments, questions and feedback regarding the updates are greatly appriciated.
Thank you.
GEO my WP beta 6 is now ready for testing ( there were a few minor beta versions between beta 2 and beta 6 ). I have also updated most of GEO my WP extensions to be compatible with version 3.0, except for one; the Global Maps extension.
Listed below are the extensions and versions which are ready to work with v3.0. You can download them from Your Account page:
I will work on the Global Maps extension this coming week.
Before updating to v3.0, please carefuly read the post on v3.0 beta 1 and v3.0 beta 2 to make sure the update goes as smooth as possible.
You can download GEO my WP 3.0 beta 6 from here.
Your comments, questions and feedback regarding the updates are greatly appriciated.
Thank you.
I am pleased to announce the release of GEO my WP 3.0 beta 2, which includes many bugs fix and improvements. The download link provided at the end of the post, but please make sure to read this post before upgrading from an earlier version.
It took a while ( 3 months ) from the first beta release, mainly because I was working on the update of the premium extensions at the same time. This way I was able to improve GEO my WP in the way it integrates with the extensions. This mostly concerns developers, but it now should be easier to develop extensions for GEO my WP using its many functions, classes, APIs, and hooks.
GEO my WP 3.0 Beta 2 is now more stable ( as far as I could test myself ). If you just start using GEO my WP, I do recommend to use this version, as I don't expect any major issues. If you are upgrading from an earlier version of GEO my WP, I suggest that you do it with caution. Make sure to backup everything before you upgrade, and it is recommended that you set up a staging environment where you can upgrade and test everything before you go live with version 3.0. Just to make sure everything goes smooth with the changes applied in the first beta ( see this post ) and with the changes added in beta 2 and described below.
Note, the premium extensions are still not ready for version 3.0. Except for the Premium Settings extension, which I will release the first beta that is compatible with v3.0 later today.
Improving the new GMW_Register_Addon class and adding new functions to make it easier and more efficient to develop an extension for GEO my WP. Once v3.0 is officially released I will start document the new ( and old ) functions and classes that GEO my WP provides.
New helper classes added in this version. Classes that can be used to generate more custom form elements ( search form and search results elements ) when needed.
In previous versions of GEO my WP, form elements like address field, radius filter, units filter, post types, taxonomies and so on, were limited and couldn't be modified/customized much. For example, the function
gmw_get_search_form_radius( $gmw );
,in previous versions, was the core radius field function which directly generated a radius dropdown based on the settings form the form editor.
Now there is a new class GMW_Search_Form_Helper that provides core functions for the different search form elements. For example, using the function
GMW_Search_Form_Helper::radius_field( $args );
, you can generate custom radius select menu by passing arguments like class, id, default_value, options and more. This probably more for developers, but also for users who have been looking to customize some of the form elements, but it was not very simply ( or possible at all ) in previous versions.
The radius field is just one example out of many functions that can be used this way. The new classes can be found in geo-my-wp/includes/template-functions.
Along with the new helper classes mentioned above, many new template functions were added in this version as well. Most of the new template functions can, and should, be used directly in the search forms and search results template files.
The template functions generate the form elements, using the new helper classes, based on the settings of the form editor. For example, the radius function
gmw_get_search_form_radius( $gmw );
, that in previous versions was directly generating the radius dropdown, is now using the radius settings from the form editor and pass it into the helper function:
GMW_Search_Form_Helper::radius_field( $args );
This way, not only integrations with GEO my WP and future updates will be much easier to manage ( for me and other developers ). Also, the search forms and search results template files, which often are being customized by the users, are cleaner and easier to manage.
In a search results template file, for example, to display the post's featured image, in a previous version the function looked like:
This function checks if the image is enabled in the form settings, if the featured image exists, and pass the width and height of the image.
Now, you can simpy use the function:
gmw_search_results_featured_image( $post, $gmw = array() );
which does everyting for you.
*If you are using custom search forms or search results template files, it is highly recommended that you update your custom templates and use the new template functions.
Some of the core extensions and template files folders were renamed in this version for better workflow and to make more sense.
The folders that hold the core extensions, such as "posts" and "friends", were renamed to "posts-locator" and "members-locator". The folder names are now dynamically generated by GEO my WP based on the extension's slug/name.
*If you are using custom search forms or search results template files, which located in the theme's or child theme folder, you will need to rename the folders name as well ( same name it is in GEO my WP core plugin ), so GEO my WP will "see" your custom templates.
More functions were deprecated in this version of GEO my WP, which most were replaced with a new function.
*If you use custom template files and have WP_DEBUG enabled, you will most likely see warnings regarding the deprecated functions. It is highly recommended that you update your custom template files and replace the deprecated functions. You can use one of the template files provided in GEO my WP plugin as a guide.
If you are upgrading from an earlier version of GEO my WP and use custom search form and search results template files, please make sure to read the above.
Pay attention to the new template functions, deprecated functions and make sure to rename the template folders in the theme's folder.
Along with this version of GEO my WP, I also released the first beta of Premium Settings 2.0. This is the first extension that is compatiable with GEO my WP 3.0.
This version includes many bugs fix, major improvements and a good amount of new features.
If you have an active license key for the Premium Settings extension you can download version 2.0 from Your Account page.
You can download GEO my WP 3.0 beta 2 from here.
Any feedback regarding the new beta vesions of GEO my WP 3.0 and the Premium Settings extension is greatly appriciated.
After almost 2 years of development, GEO my WP 3.0 is finally here and ready to be tested. You can find the download link at the end of this post. It is, however, important that you read this post before updating.
Version 3.0 is a major update and the most complicated one since the initial release of the plugin. 80% of the plugin was rewritten from scratch to improve performance, user and developer experience, better integration and more.
Before I go into details and list some of the major changes in this version, please note that this is the first beta of version 3.0 with massive core changes, so bugs are expected and it is not recommended to install this version of the plugin on a production site. Also, the premium extensions will need to be updated in order to be compatible with GEO my WP 3.0. So any of the premium extensions installed on your site will most likely not work properly with this beta version GEO my WP 3.0.
Please also keep in mind that I am a single developer working on GEO my WP. Which means the development of the core plugin and the extensions, updates, documentation, and support. This is the main reason it took me nearly 2 years ( on and off development ) to wrap up version 3.0. I tested this version on multiple environments and fixed all the issues I could find. However, as a single developer I am limited and cannot test it enough. Therefore, more issues are expected. When this happens, kindly use the comments below to report it.
The main focus in this version was to make GEO my WP more extendable and developer friendly. With many new classes, functions, and hooks that can be used to extend GEO my WP, I am hoping that themes and plugins developers will contribute and integrate their work with GEO my WP. With some of the new classes, it should be easier to register a custom extension ( add-on ), use the proximity search queries with the custom extension, use the location form and more. More details for developers I will post in the future. Perhaps, after the official release of the plugin.
Up to this version of the plugin a custom database table, which holds the geolocation data, was created for each object ( posts, BP members, Groups... ). Custom tables like wp_places_locator, wppl_friends_locator, and wp_groups_locator. Having multiple custom tables was hard to maintain and there was no good integration/relation between the different tables. Now, in GEO my WP 3.0, there is a single locations table ( gmw_locations ) that will hold the geolocation data of the different objects. Also, this table is a global table and will be used with all the subsites of a multisite installation. This is instead of creating a custom table per subsite. Having a single table now will be easier to maintain and it can be easily used when registering a custom extension.
After the update of GEO my WP 3.0 you will need to import the existing location into the new locations table. The importing process is described at the end of this post.
Along with the new locations table, a new locations meta table ( gmw_locationsmeta ) was added. With the new GMW_Location class GEO my WP can create, update and delete location meta. This is very similar to custom fields ( post meta ) and user meta. Up until this version, GEO my WP would save custom data such as phone, fax, email, and website ( for post types ) in custom fields and some user/member data in user meta. Having its own location meta system, there is a better integration between each object and its location meta as well as between each location data to the location meta. It is also possible ( for developers ) to extend the location form with custom location meta. So data such as phone, fax, email, and website can be removed and new meta can be added.
Up to this version GEO my WP saved its forms data in the wp_options table. In version 3.0 a new database table ( gmw_forms ) was added where the forms data will be saved. Doing so make it easier to maintain the forms data.
Finally, the location form of the "Edit post" page, which is one of the more important parts of GEO my WP, was completely redone. It has a new face ( which I hope you'll like ), I believe that it is more user-friendly ( feedback is welcome ) and it is generated by a class that can be extended to work with custom extensions. It can as well be modified in many ways using action hooks and filters. The GMW_Location_Form class should make it easier for themes and plugins developer to display the location form in the back-end and front-end for better integration with GEO my WP.
Location Form
Both the "Forms" and the "Edit form" page were improved ( in my opinion. Your feedback is welcome ). The "Forms" page was slightly modified and is now better organized. The major change is in the "Edit Form" page. Now when editing a form, the editor expands to a full-screen size to give more space and to make it easier to work with. In addition to that, a new "Form Submission" tab was added. The settings in this tab already existed in different tabs. This new tab was added to better group the different form settings.
Edit Form Page
The Extensions page was as well rewritten from scratch and It is now looking more like the WordPress' plugins page, which I personally like. The page contains more information about each extension and it should take care of some issues with the activation/deactivation of the extensions and license keys.
Extensions Page
GEO my WP 3.0 has a new internal caching system. This system uses transients to save complex queries, such as WP terms, WP posts and WP users queries, which should improve the plugin's performance.
Some functions, classes, and shortcodes are now deprecated and replaced and they are now placed in a file dedicated for that. If you have WP_DEBUG enabled ( which I advise you to enable while testing a beta version ) you might see some warnings after the updated ( most likely if you use custom search form or search results template files ). You should follow the warning and replace the deprecated functions as advised.
After the activation of GEO my WP 3.0 you should see an admin notice asking if you would like GEO my WP to track its usage on your site. You can either allow or disallow tracking. You can also enable and disable it at any time from GEO my WP Settings page.
The system tracks minimal, non-sensitive information that can help me improve the plugin. Information like the theme and the plugins that are being used on the site, server, WP version, PHP version, and GEO my WP version.
Tracking Notice
You will not notice big changes in the front-end, except minimal styling improvements. There are no new search form or search results template files at the moment. I might look into it once I am done with the official release of GEO my WP 3.0 and the extensions.
After the update of the plugin ( if you are updating from an earlier version ), the first thing you should see is an admin notice asking you to import existing locations. A click on the link in the notice will take you to the "Import / Export" page, under the "GEO my WP v3.0" tab. Simply click the "Import" button to import the existing locations.
Import Locations Notice
The above are the major changes of version 3.0 and changes that you should notice. As mentioned at the beginning, many classes, functions, and hooks were added. Existing functions and classes were either improved or replaced. JavaScript and CSS files were as well improved, combined and minified. Some files and folders were renamed and organized.
One thing I still need to do is to go over and fix the description of the settings in the Settings page and the form editor.
I believe I covered almost everything. You can download GEO my WP 3.0 beta 1 from here and replace it with the current version installed on your site.
Feedback, comments, and bug reports are welcome via the comments section below.
While the beta version is being tested, I will be updating the extensions, which hopefull, will be ready by the time the official release of GEO my WP 3.0 is ready.
Your support is greatly appreciated.
Thank you.