mapster

OK! In this latest version (1.1.1), a new option is added when creating popups. You should see a “Keep Popup Open on Hover” when you have Hover selected as the interaction for any given feature. If you turn this on, then the popup shouldn’t close when your mouse leaves the feature on the map, and will only close when leaving the popup. This is a bit of a tricky feature so please let me know any issues.

Just letting you know, the latest update is now live and you can download the Pro version (free for now) to do Mass Editing at https://wpmaps.mapster.me/pro. Hover fix coming soon.

Hello,

for the hover interaction issue — that’s typically a case, like you explained, where you’d use a click rather than hover interaction. That being said we have gotten this request before. Maybe you would like to add this to our feature requests? https://mapster.frill.co/b/kvj7njve/feature-ideas Ie, to have a hoverable popup that doesn’t disappear on mouseover of the popup. I think we could get to that next week sometime.

For the mass editing, we have a very significant update coming in the next couple of days, including a “pro” version of the plugin, which will have mass editing. The Pro version is completely free (for now) while it will be in beta testing, but it allows extensive mass editing so you would be able to change all 200 locations at once. Keep an eye out for that with the next update of the plugin.

<3 thanks!!

Hi there! I believe this problem is resolved in the latest version (1.0.4). It was not due to the extra libraries but instead due to certain fonts that weren’t present when Maplibre was loaded, but were referenced the same as in Mapbox. Give it a try and let me know if it’s all sorted now. Thanks!

Thanks for the note! I will be sure to look into this soon and let you know what I find.

Found it! Just a few characters that we missed in the rewrite. Anyway, if you update to 1.0.2 that should be back — and keep an eye out for the updated documentation coming along with much more developer features soon!

Hi Francesco! Thanks for the note. We did some major rewriting and refactoring in this last update, we tried to catch every exception but I’m sorry your custom function isn’t working! It should be a relatively simple fix, I’ll look into it later today. Do you have a link where I can see it breaking so I can double check if anything in particular is weird? Thanks again.

Hello! Thanks for the question. We haven’t built this in as a specific option, mainly because most people would like to have control of the map and place it amongst other items on a page. The best way to have the map be the front page of your site would be to make a Page, make it the Home Page of the site (in WP settings), and put the shortcode for the map you made into that Page.

Then, you could adjust the CSS of the map to fit the size of the browser window when it opens (with something like

position: absolute;
width: 100%;
height: 100vh;

However, this might not do what you’re expecting, because this will cause other elements to hide under the map. We do have an option in the “Setup” section of your map that says “Full Size”, and “Ignore Container”, which will do roughly these same things. Try turning on those options, and placing the shortcode on the “Front Page” of your site, and let me know if that works!

Hey there madkats, did you find the shortcode? It’s on the Maps page in the admin area, where you edit the maps — the shortcode is right beside the titles.

Yes. [email protected]

Hi Francesco, is this happening locally or is there a site I can visit? I believe I’ve fixed this in 0.5.13 but perhaps I was mistaken, it would be good to check the bug in action.

You will need to set the coordinates then, yes. The Fit to Features necessarily sets the center and the zoom together automatically. A useful tool to find coordinates is geojson.io, if that helps!

Hello, yes, definitely. It’s listed in the “View” section: https://wpmaps.mapster.me/documentation/maps#setup. You just change “Fit to Features” to “Manual Center and Zoom”.

Thanks, yes, actually we had that before, but in order to load the map initially on the bounds (without resizing), we had it load the bounds directly. After looking again at initialization options in Mapbox, I see there is fitBoundsOptions I can pass during initialization of the map. I’ll update this with a padding of 20 in the next update!

Thanks.