February though a short month, has been a busy one for GeoDirectory V2.

Our original hope was to have a beta out by the end of the month but alas the best laid plans

I spent some time earlier today going through all the outstanding tasks we need to complete before we can release the beta.

The list is much shorter now and most tasks are final checks on functionality that might have been affected by other changes.

The vast majority of core functionality is already complete.

With that being said, the majority of our development team (apart from me) are on holiday today and tomorrow, so back on Monday the 5th of March.

I have set our milestone goals as:

  1. 12th March Alpha release (mostly for internal testing, and early developer preview)
  2. 19th March Beta release (public beta)

With that out of the way, lets give you a little peek at what we have been up to in February πŸ™‚

Most of the things mentioned here deserve their own post so for some I will only provide few details in bullet points.


The Gutenberg editor will be released in WordPress v5, it will be one of the biggest changes to WordPress in recent history and we want to be ready for it!

The biggest delay we had was finding a way to make GeoDirectory V2 Gutenberg ready.

For listings, the editor can be used to build template pages for things like Details, Listing and Search pages.

It took us a while to develop this part, because in these template pages we are not pulling “real” data but giving demo data just to build the templates.

We ended up creating our own class for this which turns all the GeoDirectory output features, available as either a shortcode, widget or Gutenberg “block”.

This is done in such a way that no matter what you use, you will have consistent output.

So going from a template page of shortcodes to blocks will be very easy.

(here is a demo of how easy it is to add info to the details page template with Gutenberg)

Rating Styles

GeoDirectory V1 gives you the ability to use either a transparent image star or a FontAwesome Star icon.

These two systems had their own drawbacks, they used generic JS libraries like everyone does to make it work, but also limited the functionality.

The solution was to write our own code. We striped our 5 JS/CSS files and compressed it all down to a just a few lines of JS.

In GeoDirectory V2 you will have the ability to upload your own transparent ratings image if you want, but you can now also use ANY fontawesome icon and set the colors and rating text right from the settings πŸ™‚

Import / Export

This really deserves its own post so i’ll just list a few of the main bullet points

  • Improved error checking (ex: CSV row 216: Missing Title)
  • Improved import speed (especially for large data sets)
  • Auto fill GPS details if enough address info is provided.
  • Import / Export / Backup all GD settings
  • Import / Export reviews added

Email templates

V2 will give you greater control over email and their styling, as well as adding some new features.

  • Editable email template design
  • Edit any email template
  • Easier to translate
  • Added action tags *

* You can now decide if you would like to let the listing OWNER Approve, Reject and/or Spam new reviews.

Not in all cases will you want to allow this self moderating of reviews, that’s why each action can be added individually, maybe you only want the listing owner to be able to Approve their own reviews but not spam or delete it.

Business Hours / Opening Times

Again this deserves its own post so here i will only give the main points.

Building our own system we wanted it to be as versatile as possible:

  • Allows multiple open/close times per day
  • Live open/close status with dropdown for full times
  • Cache proof open/close status (wont be affected by server caching)
  • Live updating, if you are browsing a listing when it opens/closes the status will change without a page refresh
  • Compatible with normal import/export.

Add listing

A few little bullet points before a full post.

  • Option to allow posting without loggin in.
  • Option to remove preview page
  • Now uses Default WP preview system.
  • Auto save every few seconds
  • Start listing, return later feature.
  • Start edits, return later feature.
  • Improved category selection
  • Improved tags selection
  • Image title/description feature.

Backend Listings

You can now show more info in the backend listing screens.

We also now have a “Closed down” post status which if set a listing will not show in search or listing views but will be able to be directly accessed and show a closed down message.

Quick edit / bulk edit menus which were previously disabled now fully work.


Have it your way! πŸ™‚

The End

There are many improvements not listed here, the most significant are under the hood which will make GeoDirectory much more future proof and expandable for both developers and users.


Team GeoDirectory!

30 thoughts on “GeoDirectory V2 Final Roadmap

  1. Hi Stiofan & Team – Much appreciation for the update. Your description of what you are building sounds terrific. I’m really looking forward to Geo V2. I just have to hold my breath and projcets now until 19th March.

    Some lessons of life that apply here are…..
    “Slow is Fast”
    “Measure twice cut once”
    “Do the job properly so you only have to do it once”


  2. Thanks Stiofan! Are these dates secure?

    I had taken holiday for next week in anticipation that the launch would be in Feb. but would postpone now to end of March but I need to know if we can really rely on a release in week commencing 19 Mar?

    • Hi David,

      The dates are our estimates after assessing what still needs completed if everything goes smooth.
      is is a beta release of core GD not a final release, it is meant for testing not for full on production site.

      I am not sure what that means for your holidays but i hope you have a good one πŸ™‚


  3. Hi Stiofan

    Thank you. I’m just trying to assess the firmness of the estimate, i.e. is it as before that it may slip by another few weeks or rather max. few days?

    Could you please elaborate on the purpose of the beta (and it not being for “full on production site”)`? I dont understand what you mean with that. I understand it is for testing , but my understanding is also that on the basis of the beta everyone can start with customisations of GD and that any remaining / appearing issues will be fixed with updates until final version. So the big difference will be to now that any customisations along the way will not be lost, while if I do any now with v1 they will be wiped out. I hope I’m not missunderstanding, i.e. that the beta is -only- for testing and customisations will not remaing.

    I’m fine to not go live with a v2 beta, but I really need to start making customisations and I was hoping / understanding that users can start with the beta and report any problems along the way.

    Could you please clarify of what to expect for the beta so that everyone can plan ahead?

    My holiday that I’m taking (now from 19th Mar onwards) is to start working on customisation on the basis of the beta, so fully dedicated to the release πŸ™‚

    • Ah, you are taking time off from work to work on GD, i though maybe you were a dev and wanted to take time off after your project was complete πŸ™‚

      The purpose of the beta is so users can test it and report any issues, these issues could be many things, and even some might be severe and break the site, this is why in general beta version should not be used on production sites but as you said, in a development site getting ready for production. Most things will be locked in and should not change from beta to final release but its not a 100% guarantee.
      The beta should only be used from a fresh install, the v1 to v2 conversion scripts deliberately won’t be included in the first beta release as we want tests to be recorded from fresh installs and not have to worry about conversion issue reports (that will come later)

      Setting dates in stone in the dev world rarely works, some days you finish 100 task and others it takes you a whole day just to do one. Just look at the Gutenberg original timeline πŸ™‚

  4. Thanks Stiofan ,that’s helpful information.

    No I do this (GD) as a side project next to my 60h/week office job, so using holidays to work on this is one aspect, but using them efficiently the more paramount one.

    The fact that β€œmost things should be locked in” is comforting, which means that most customisations should not get lost when updating along the way on beta versions or to final release. However, the way I understand your point is, that the beta is very isolated. So the only way to keep speed (and not loose time any further) would be to
    (i) make code + Gutenberg customisations during beta
    (ii) when the final version is released: upgrade v1 to v2 so that content is contained
    (iii) copy / apply code customisations made during beta to final version
    (iv) replicate Gutenberg customisations
    (iv) fix any code customisations that got broken because of beta vs. final code.

    Would you agree that this would be the most efficient and a possible route considering time constraint? Of course just waiting for final release would be most efficient, but it wouldnt be optimal from a timing perspective.

    Oh, and how long would you expect it would take between beta and final version? Just a rough indication would be great as I have no idea if that is 2 weeks, 8 weeks or 6 months.


    • Hi David,

      I’ll try to reply. Yes your roadmap sounds good and the best way to tackle this.

      From beta to final it really depends how many bugs you guys will find that we missed. If very few, 1 week or less.
      If they are many (but I don’t think so), it could take up to a month. I doubt it will be more than that.


    • Yes you can use post_id if you wanted, not sure why you would want to though πŸ™‚

  5. I’m really getting excited about this, guys. V2 is going to make my life so much easier. Keep up the good work!

    • Yes, when the final version of V2 will be released, we will provide a conversion script to allow you to move from one to the other. That said, if you heavily customized the design of the old version, you’ll have to do some work to get V2 to look like your customized version of V1. There is no way we can provide a seamless upgrade of customization too.

  6. Awesomeness! Sounds great guys! I can’t wait to get to dig into the Beta Release….
    Lots of customization’s on my site will be reduced with V2.
    Let the GD Testing Games V2 begin! πŸ™‚

  7. Gutenberg compatability sounds good. We really want our listings to look like our other pages and posts, and I’m hoping that Gutenberg lives up to the hype and lets us do that. Holding off from any major customisation until we know what v 2 looks like (such as using the WordPress media library, that’s a biggy for us).

    Great job, it’s good to see so much effort going into the plugin.

  8. Hello,

    Glad to hear that the V2 Beta will be released soon. Just need to know if Directory Starter theme will be continued under V2 as well.


    • Yes, right after releasing the beta of V2 we will work on adapting the themes to work with it.


  9. will Gutenberg and v2 allow designing a detail page layout for all listing details or it can only be done for individual listing

    • Hello,

      For details page you will edit a page template which ALL the listings will use, Gutenberg won’t be used for individual listings, just for the template page πŸ™‚


  10. I once read somewhere about a person describing themselves as…. “feeling like they are a Ferrari without wheels.”

    I can really identify with that comment, and I am hoping that Gutenberg together with Geodirectory V2, will be my set of wheels.


Leave a Reply

Your email address will not be published. Required fields are marked *

Share This