Forum Replies Created

Viewing 15 replies - 1 through 15 (of 888 total)
  • Plugin Author Lance Cleveland

    (@charlestonsw)

    We just received our copy of the latest Salient theme from the author for testing compatibility.

    Store Locator Plus? is working perfectly with their theme.

    For others reading this review, yes, our plugin works with Salient. We can provide examples if you contact use via our contact form at storelocatorplus.com

    Plugin Author Lance Cleveland

    (@charlestonsw)

    Thanks for the positive comments!

    Yes, SLP 5 did change what happens when a user types in an address to search for on the map. This reduces your Google API costs slightly AND gives your users a bit more security (read our news post at https://www.storelocatorplus.com for details on that and what those changes mean).

    The security on pre-existing Google API key needs to be updated, which is the issue you ran into. Glad you got it sorted out.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    Thanks, Dan. Glad the support team could get you squared away!

    Plugin Author Lance Cleveland

    (@charlestonsw)

    You must submit all translations to Translate.www.ads-software.com — local .po and .mo files went by the wayside over a year ago for all plugins and may be part of the problem.

    If you have updated the Translate site at WordPress for our plugin and are using the latest release of SLP and WordPress and still have issues please follow CiCi’s recommendations above and contact us our forums. We don’t check this support forum every day but do check out on-site forum regularly.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    The “To All” button is a feature a Premier customer paid for. They have 50,000+ locations and cannot possibly check 50,000 boxes. The “select all” checkbox does not work as WordPress limits the longest table list to 999 locations — and that breaks most browsers.

    Instead they came up with a design for a “To All” button that applies to all locations. We added that and a user-confirmation to ensure someone has to confirm a delete before deleting all locations.

    The design may not be what you prefer, but it is one that someone deemed important enough to their operation to pay for the interface change. We did our best to incorporate their request without breaking prior functionality. Clicking “Apply” instead of “To All” would work exactly as you said.

    If you can come up with a great UX design that allows someone to apply any one of 20 operations to selected rows or “every row in the entire data set” please share. In the meantime we’ve put this on our dev schedule to re-visit the experience. We’re always looking for ways to improve the UX.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    It should be back now – somehow our ==changelog== tag in the readme went away.

    Not sure why the rest of the development tab was wrong.

    You’re right, the list of commits is not the same thing — was trying to get you some info on what changed while we looked into the issue.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    The changelog has been culled to the last 6 months of releases per WP.org’s request for all authors to reduce their readme.txt file sizes.

    You can always view the entire detailed change log in the git repo commits history:
    https://bitbucket.org/storelocatorplus/store-locator-plus/wiki/Home

    Or follow the news posts for version changes.
    https://www.storelocatorplus.com/news/

    Plugin Author Lance Cleveland

    (@charlestonsw)

    Here are some facts readers should consider:

    Rene’s purchases were made over 27 months ago in July 2015.

    In September 2015 we made the decision to rework the product architecture. We notified all of our users by email, newsletter, blog posts, and social media that they would need to upgrade to new add ons starting in 12 months. We set an official sunset date for the legacy architecture 12 months in the future: September 2016.

    A few seldom-used add on products did sunset in December 2016, none of which Rene purchased.

    We did not sunset most products until August 2017, 11 months after the original sunset date and 23 months after the initial notifications.

    During the entire transition period from September 2015 until June 2017 we offered discounts for all buyers of the legacy products for all or most of their original purchase price.

    Our current premium add ons are Power, Experience, and Premie. They have been online and fully supported with free email, forums, and Slack channel support since January 2016. They were offered for all new buyers while we continue to product patches for our entire legacy line of products. They contain all of the features that were offered in over a dozen of our legacy products, simplified into 3 main add ons. They will continue to be supported for the foreseeable future.

    Since Rene’s YouTube post 11 hours ago, his first attempt to contact us, we have been in communication with Rene by email. We have replied with details on how to downgrade and retain full functionality that he originally purchased back in July 2015 as well as the proper upgrade path if he chooses to upgrade WordPress and our base (free) product to the latest version.?

    Plugin Author Lance Cleveland

    (@charlestonsw)

    As we communicated multiple times you can DOWNGRADE Store Locator Plus to any one of the older releases that are compatible with your one-time $30 add on purchase you made 2 years ago. This costs you NOTHING.

    If you want to use the latest version of the FREE plugin with over 300 improvements in performance as well as new features you must replace your outdated $30 purchase with a newer product. As we noted in our readme files, blog posts, Twitter feed, Facebook feed, RSS feeds, and news articles for over 18 months some of the paid add ons would stop working within a year in order to realize the numerous performance gains in the FREE base product.

    You claim you are left in the dark but we have communicated this many times. You are leaving 1-star review because you are unhappy that your one-time $30 purchase over 2 years ago doesn’t work forever with the latest version of the product.

    The $300 stereo I bought for my car 5 years ago does not work with the latest model of the same exact car this year. Should I be mad at the car manufacturer for making a better car and making my $300 stereo useless? How dare they! Maybe I should leave them a 1-star review about their new car.

    In the meantime, downgrade your FREE Store Locator Plus product back to the version 4.4 release and do not upgrade it and you will keep the full $30 worth of functionality of your paid add on.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    Also – please post support questions on our main site. Following 2 support sites means things are going to get lost and since we have less visibility on the WP forums messages here will get far less attention.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    We run PHP7 on all of our production and development servers. That is not the issue.

    The new editor is 100% JavaScript. Check your browser that you do not have JavaScript errors from other plugins that are hijacking the admin interface on the SLP admin pages.

    There was also a CSS tweak in the 4.8.3 release. Scroll down the page and let us know if the edit form is below the table. That happens on some WP themes and the upcoming 4.8.3+ patch should help resolve that on most (all?) sites.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    Also – we do not read this forum often. Please post and follow up at https://wordpress.storelocatorplus.com/

    Plugin Author Lance Cleveland

    (@charlestonsw)

    What do you mean by “my api”?

    Either you’ve turned off Google Maps in our plugin or you’ve put your API key in the wrong section of the General Settings. It does NOT go in the “Google Business License” section (unless you paid $20k+ for an OEM business license). It goes in the Google Developers Console / Browser Key entry.

    Try moving the plugin to mu-plugins directory instead of hacking the code.

    If that doesn’t work make sure your roles and caps are set properly for your users and make opCache menus only available to site admins.

    Plugin Author Lance Cleveland

    (@charlestonsw)

    That is fixed in SLP 4.6.2 you are running WordPress < 4.4.

    As an aside, you should really be upgrading WordPress to something newer than 4.3 due to a number of security patches introduced in 4.4, 4.5, and 4.6.

Viewing 15 replies - 1 through 15 (of 888 total)