• Resolved Mark Barnes

    (@mark8barnes)


    Firstly, just to say a big “Thank you” for this plugin. I’ve tried nearly all of them, but this is the most elegantly coded and best presented of them all!

    There are (inevitably) a few bugs, though I can only remember one at present:

    1. When you click “Preview a location on a map”, Google updates the Zip Code – and, in the UK at least, usually gets it wrong. It would be great if this didn’t happen, or at least it could be turned off.

    Also, some suggestions:

    1. The only feature I really miss is being able to assign categories to a store. Looking at other posts, it looks as though this might be coming soon? Is this correct?
    2. I would imagine most of us have stores in only one country. It would be great if we could set an option for a default country that would then stop asking us for the country when adding, and not display a country in the frontend.
    3. I need to style the frontend to fit with my theme, but the lack of semantic classes, particularly on paragraph tags, prevents this.
    4. Even better, is it possible to override the templates somehow? How about adding a filter to the template list, so coders can add their own templates? We might even submit templates for future inclusion.
    5. I’d like to be able to add the map/satellite/terrain buttons to the map.
    6. When adding/editing, I love being able to drag the marker to exactly the right spot. I do find the map quite small though. It is possible for it to be enlargeable?

    If you don’t have the time, but would like these features, I could perhaps code them for you. Let me know if that would be helpful.

    https://wordpress.org/plugins/wp-store-locator/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tijmen Smit

    (@tijmensmit)

    Maybe it’s better if I remove the line that updates the zipcode in general when a user clicks preview. I should trust users to know which zipcode belongs to the address they fill in.

    1) Yeah this will be added to the premium version. But this is not complete yet, I have some other features to finish before I can release it. You can if you want get access to the beta version, just email me at info at tijmensmit.com.

    2) This is a good idea, will look into adding this to a future version. I’m planning on adding a tool in a future release where you can completely customize how the store details are shown. So you can change whether the store name is a link, the country is shown, the order in which it is shown etc. And in case of the template where the store details are placed under the map spread the details out over 3 columns.

    3) There should be more then enough classes you can use to target whatever you want to style in the store locator? Which element are you having problems with?

    4) I have to look into this, there is currently no easy way to do it. But it’s a good idea to make it easier to override the existing templates.

    5) I will make this an option in the next release, but you can also change it yourself for now. Just open the wpsl-gmap.js, look for ‘mapTypeControl: false’ and change it to true

    6) You can change the height in the css file #wpsl-gmap-wrap {height:450px !important;} or so, but if you add it to the css of the plugin then it will be overwritten with a plugin. So maybe add it through the function.php?

    Thread Starter Mark Barnes

    (@mark8barnes)

    Thanks for the prompt reply. I’ve sent you an email re: beta testing :-).

    There should be more then enough classes you can use to target whatever you want to style in the store locator? Which element are you having problems with?

    The elements within wpsl-stores. Specifically, I want to be able to remove the margins from the <p> tag that’s around “More info”, without removing them from the address. In addition, the distance doesn’t have any markup at all, which means I can’t do anything with that, though I’d like to move it onto the same line as “Directions”, to save space. I also think it would be useful to add a span and class to the store name too, instead of relying on targeting the <strong> tag.

    But it’s a good idea to make it easier to override the existing templates.

    I had in mind something like holding the default templates in an array: array (array('name' => 'Default', 'file' => 'templates/default.php'), array ('name' => 'Fancy', 'file' => 'templates/fancy.php')), and then passing that through a filter so we could easily add/remove templates. But so long as it’s possible to do without editing the plugin itself, I don’t mind.

    Thanks for the advice on the other stuff. I’ll certainly by buying the Pro version.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘A few suggestions and a bug’ is closed to new replies.