Cyber Sprocket Labs

You cannot have store-locator installed and activated alongside our product Store Locator Plus (or Store Locator LE).

Deactivate the other plugin you tried (Store Locator) and it will work.

We’ve added some new API calls in the CafePress standard edition that may help. There are some bugs in the CafePress API on the CafePress die of things but we cannot get CafePress to respond to any of our questions or requests for help to fix them.

Go to our forums and send a private message with your API key and store name and we can try to see if we can get it going with a workaround.

We are forked from Store Locator, but they are a good bit different now.

We do not offer support for the free plugins. You can try other users @ the forums on our site at https://www.cybersprocket.com.

Odd — you should not see any license messages with the LE version.

The JavaScript error can happen if you are not running PHP5 or have the server configured to prevent PHP applets from running as javascript includes.

We forked our copy from Store Locator & have been upfront about it. In fact that was the lead description up until the last few releases where we clearly stated we had based our work on Viadat’s Store Locator and the product was a fork. Due to repeated requests to assist with the original Store Locator and the fact that we have diverged on 50% of the code (or more) at this point we recently removed that notice.

The only reason we started a fork in the first place was we needed fixes & features on the original Store Locator plugin and couldn’t get a response to our email pings last winter. Given the tight deadline we were under we patched & extended the product to the point we thought some other Store Locator users may have found it useful.

Since then we’ve diverged further from Store Locator not in an attempt to gain market share (or take it from the original concept) but solely due to client and/or customer input. We also keep all of our code open source including the commercial Store Locator Plus edition even though significant portions of that code are original, the commercial product is no listed in the directory at WordPress, and thus does not need to be GPL.

We prefer to support open source and let people build on the work of others that led the way. Sometimes that means people are building on our work, sometimes we build on theirs.

Thanks Viadat for starting a solid foundation on which to build.

Mark –

We have requested another namespace for a plugin that was pulled from the listings & has been re-engineered in a free version.

MoneyPress : Amazon LE
(moneypress-amazon-le)

I’m not quite sure how this process works, but someone asked for a zip file of the plugin before we published. Doesn’t the WordPress svn repo interface do that for us? This is unusual. Nobody has ever asked for a zip file before and it seems like extra overhead and completely unnecessary. Is this standard operating procedure or are we on some sort of probation now?

Please advise so we can rectify this situation & get on the WordPress “good guys” list.

TIA,
Lance

We do that with our Store Locator Plus product:
https://www.cybersprocket.com/products/store-locator-plus/

We have not looked at SimpleMap yet so we can’t comment on what is different. It is NOT a fork of that and we did not borrow heavily from their description pages. We started as a fork of the original Store Locator when that author went on haitus and we needed some patches. We’ve since modified the system heavily based on user feedback of our original post.

Store Locator Plus offers a lot of features not in the LE version. Our Plus version is here:
https://www.cybersprocket.com/products/store-locator-plus/

There is one negative side effect for the users that is bad for everyone involved. The few-hundred users that have already purchased the plugin now must go through a manual process to:

a) determine there is a new release of their premium plugin available

b) install & activate the upgraded version

Being able to have premium plugins hook directly into the available upgrades system built into WordPress makes life a lot easier for everyone. A seemingly simple solution would be to allow premium plugins in the directory and come up with an obvious, yet simplistic way of denoting premium (commercial) v. free plugins… could be as simple as a text demarcation for “FREE” or “Paid” and possibly even a graphic denoting each on the listing details.

While we may find a way to “hack into” the built-in WordPress upgrades system it is going to be a good amount of extra work on our end in order to make the lives of our premium users a bit easier when it comes time to upgrade. Sadly, there does not appear to be a readily documented and accessible way to do this. That means it will be a hack and may break in future WP releases.

The new LE version is posted in the new namespace.

Please let us know if there are any issues. No license fee, no key required (other than Google Maps keys to make it work).

We fixed this and a lot of other issues with our reworked version:
https://www.cybersprocket.com/products/store-locator-plus/

We fixed that along with a lot of other issues with our modified version:
https://www.cybersprocket.com/products/store-locator-plus/

https://www.cybersprocket.com/products/store-locator-plus/

Tagging and that added shortcode qualifiers will let you do this.

https://www.cybersprocket.com/products/store-locator-plus/

https://www.cybersprocket.com/products/store-locator-plus/