mapster

Great catch. It looks like, on that line, I failed to do the initial check for the variable being defined. I’ve added this into the plugin for the next version, which should be released in the next day or so. Really appreciate the message and fix!

Marking as resolved since I have not heard more.

Hi, thanks for your message. You will have to implement custom code using the Developer Hooks (https://wpmaps-docs.mapster.me/for-developers/javascript-hooks) in order to create a functionality like this tied to external user choices from a dropdown or another field. Another option would be to make multiple maps, with Frankfurt locations on one and Berlin on another, and redirect the user to the right map after they make their choice.

Hope that helps!

This issue has been solved. In this case, one of the points being loaded onto the map was missing coordinates. I’m adding an alert that will show on the frontend when this is the case, which will be present in the next version, but otherwise if you have this issue, verify that all your points are correct!

Hey there! Sorry you’re having some trouble. It looks like something related to popups, but I can’t verify perfectly. To provide better support, do you mind emailing [email protected] ? Thanks.

After following up directly, this bug was resolved in 1.2.17!

Hello! First off thanks for using the plugin, hope it’s working nicely for you.

The “mwm” is defined when the Mapster scripts start up, which is basically once they are loaded onto the page (they have a dependency on jQuery and then some internal dependencies, such as loading the Mapbox library and so on). WordPress can be tough in terms of knowing exactly which scripts are loading before which other scripts, especially when you’re using plugins like you described that are inserting scripts at different places.

You’re probably safe if you wait for the jQuery loading event before calling mwm. If you’re not sure, safest to call window.mwm since it’s defined globally. However, your solution also works great — basically using some kind of setInterval to check if window.mwm is defined before doing your custom scripts. I think you probably have it figured out!

Let me know if you need any more help.

Hi there, in my local tests everything appears to be working. Can you email us at [email protected] so we can provide more specific support and a beta version? Thanks!

Hi there, thanks for the site link! Everything looks good, things look configured correctly. There was a bug with this recently that was fixed, can I ask what version of the plugin you have installed? If it’s not the latest, try updating it to the latest and reload the page. If it is the latest, then please let me know and I’ll be sure to run some more tests right away.

Did you need any more help with this issue?

Hello! Sorry that you’re having problems ?? Can you send a link of the page you’re working on, if it’s currently on the web?

Hi Fabio! I’ve removed the blue marker from appearing, and made it so that if you have a marker, it’ll open the popup for that marker when selected from the Custom Search Filter.

Hey Fabio! Try out 1.2.14 for the fix here.

• This reply was modified 2 years, 8 months ago by mapster.

Thanks for your notes! Fixes are in development now, should be out tomorrow after some testing.

Confirmed as resolved via email.