WordPress Store Locator Plus Anniversary Sale

We are lowering the price of select add-ons to celebrate the WordPress Store Locator Plus 10 year anniversary !

Power Add-on

The Power add-on is now listed for sale at $150. This is a buy and own do it yourself add-on.

Popular features included with Power add-on

  • Import/Export your location data to csv file
  • Categorize , Tag locations
  • Reporting tools
  • Directories
  • SEO Pages
  • Location sensor

Experience Add-on

 

The Experience Add-on to our Word Press Store Locator Plus plug-in is on sale for $100! Thats a $100 savings.  This is an add-on to the Plug-in Version of Store Locator Plus

  • Change the Layout
  • Change the Look Of The Map
  • Add Location Search  buttons via Widgets
  • Add Discrete search filters by City, State more
  • Add Customize style sheets for search , map and results layouts.

Premier  Yearly Subscription

Our Premier sign up fee has been reduced as a promotional sale to celebrate the 10 year anniversary of the SLP plug-in.  Sign up fee is a low $49. The renewable annual Premier subscription remains at $275.  The total price for a limited time $324.  The Premier subscription includes both the Power and Experience add-ons as well as additional features in the layouts, search criteria, including (but not limited to)

Premier customers input for new features are always welcome.

See the Premier Description for additional information

 

 

Store Locator Plus updates and Patches

With so many changes in the wind these days about APIs and the speed  in which the Google MAP API  terms of service  in their “cloud” platform have been happening , we are always thankful when our customers point out changes that have occurred in the WPSLP functionality.  Thank you to our forum poster, Paul , for pointing  us in the right direction by deactivating Power and exposing the zoom  issue.  If you discover something isn’t working the way it used to, check for updates.  Posting in the WordPress Store Locator Plus  forums is the best way to bring issues to our attention.  Providing your Plugin environment , as Paul did, helps us the most. The more people who post the issue with a screenshot of their plug-in environment, the more likely we are to believe it really might be a bug in SLP.