Posted on

Updates for 2017 WordPress Store Locator Plus plugin and Add-ons: Power, Experience, Premier

2016 , bye bye bye…  Here’s to you 2017! : We are looking forward to a productive and prosperous  year.  Last of the year updates for the WordPress Store Locator Plus plug-in as well as updated versions for the  featured Power, and Experience add-ons as well as new  Premier functionality and features.

Before updating the add-ons, you will be required to update the base Store Locator Plus plugin to 4.7 or higher.  Note:  If you have bookmarks and/or “auto-  form fill”  to your WordPress Store Locator Plus account you will need to change  the  WP-SLP url to the  new url .

You can review the WordPress Store Locator Plus change log here.

Store Locator Plus version updates thru 4.7.2  


  • As of 2017, the  WordPress Store Locator Plus plugin site is now 
  • Interactive settings,  if you check a box, the corresponding features that are effected will be highlighted.
  • An Updated JavaScript engine (See Video)
  • Faster DB loading of options.
  • Added support for CRON hooks in smart options.
  • Update admin CSS menus for narrow displays.
  • Dismiss Notifications 
  • Gracefully capture invalid REST API requests for smart options that do not exist.

Premier 4.7. and 4.7.1

  • Results Interactions mode (See  Video)
  • Scheduling your  geocode locations process via CRON (See Video)

Power 4.7.1 

  • Slightly faster scheduled imports.
  • Better messaging for Premier Scheduled Geocoding tasks.
  • Bulk geocode all uncoded has been fixed and now geocodes ALL records not every-other one.
  • Schedule messages moved to General / Schedule tab.
  • Log import messages checkbox and Log schedule messages checkbox are on the General tab so Premier can play too.

Experience 4.7.1

  • Admin UI hints on related settings.



Posted on

Cleaner Git Log With Merges

In some of our repositories now, Panhandler in particular, there are a lot of merge commits.  As the master branch containing the API definition gets updated, each driver branch merges in master so that it can be updated to target the latest API.  This results in the driver branches having various merge commits that bring in master, and that can make the output of a simple ‘git log’ more verbose than you may want.

One useful option for git-log is ‘–no-merges’, which will omit any merge commits.  If we have a repo like this

O---O---A---B---C---D---E---F    [master]
         \           \
  O---O---G---H---I---J---K      [driver]

and we run
$ git checkout driver
$ git log --no-merges
then we won’t see commits G or J, since those are points where master was merged into the driver branch.

But one issue is that we will still see the commits from the master branch.  That can be annoying if all we want to see are the driver commits.  So what we can do is tell Git that we want to exclude them, like so:
$ git log driver ^master
This should be read as, “Display all commits in ‘driver’ that are not in ‘master’”.  Which in this case shows all of the driver branch.

You have probably used the ‘..’ syntax before, writing something like
$ git log driver..origin/driver
to see all of the commits in the ‘origin/driver’ that are not in ‘driver’.  That ‘..’ syntax is actually a short-cut for the first example.  It is entirely equivalent to
$ git log ^driver origin/driver
“All of the commits which are not in ‘driver’ but that are in ‘origin/driver’”.

There are a lot of options for controlling which commits are displayed by git-log.  Ultimately those options stem from git-rev-list, which is the plumbing command used by git-log and many other parts of Git to produce a list of commits.  The documentation for git-rev-list has all the details about ‘History Simplification’, which can help you narrow down your focus when working in a repository that has a lot of merges.