[Chris]

Sorry about that, I left some files out of the latest build. 2.49.3 should fix it.

[Chris]

Hi,

Thanks for reporting this! I think I’ve found the bug and fixed it in version 2.49.2. Please let me know how it works for you.

[Chris]

Hi,

Plugin version? Are you using Google or Leaflet?

[Chris]

Hi,

That doesn’t sound normal, but I’m not sure I understand. Do you mean you can’t create new maps?

If so, the FAQ has an explanation of how to fix common JavaScript errors. Or, feel free to email me with a login if you’d like to show me in the system (you can use the ‘contact form’ link on this site).

[Chris]

Hi,

MapPress uses ‘dynamic’ maps (those are the ones you can pan and zoom).

Google is requiring everyone to enter billing info. Whether or not they actually bill you depends on your usage – probably most blogs will not pay anything, and I believe you can also set usage limits to prevent surprise billing.

You can learn more here:
https://cloud.google.com/maps-platform/pricing/

If you think you’ll be paying for Google, you can try the latest (BETA) version of MapPress, 2.49. It supports Leaflet / Open Street Map maps, which are free, and MapBox maps which have a much higher free usage limit than Google.

[Chris]

For everyone following this, I’ve just released MapPress 2.49 BETA, which supports Leaflet, Open Street Map and MapBox, as well as Google Maps.

This is a new version with extensive changes. If you encounter bugs, please contact me and I’ll try to fix them as quickly as possible.

The new version is described here:
BETA Documentation

You can easily switch between Google and Leaflet in the MapPress settings screen. Most features are identical, but Leaflet has the following limitations:

— Google Traffic, bicycling and transport overlays are not available
— Inline directions are not available.  Directions are provided from Google Maps.
— Drawing tools for shapes and polygons are not provided.  If shapes are created using a Google map, they will be converted to plain markers in Leaflet

Thanks for your help and support, and I hope you enjoy the new release!

[Chris]

I’m working on adding leaflet & nominatim, but it’s quite a conversion.

If you (and anyone else) would like to volunteer to test it, please send me an email. The initial version will probably lack support for KMLs and shapes, but otherwise be fully functional.

[Chris]

Hi,

I saw Enfold’s solution, but it seems a bit paranoid to ask users to validate each video, map, etc. on the site. As they say “There are currently a lot of horror stories out there on how websites must be adapted…”

I assume your site has a privacy notice that directs users to your privacy policy. Why not just include in that privacy notice a warning that you use Google Maps, and a link to Google’s own privacy policy? Many sites state that use of the site after the notice constitutes acceptance of the privacy policy.

It seems unlikely that many people would wish to opt out of Google Maps, and redirecting them directly to Google Maps just lets Google gather their IP address information directly rather than through the API.

Anyway, if I’m missing something please let me know.

[Chris]

Hi Joe,

Sorry about that, I’ll add the form back in. I was planning to have the form go to Google Maps, but the way I did it, it skipped the form entirely.

[Chris]

Hi,

To save a map with terrain view enabled:
1. Edit the map
2. Check the ‘terrain’ box
3. Save the map

You can also set it in the shortcode:
[mappress maptypeid="terrain"]

However, if you’re looking for a way to default ALL maps to terrain (i.e. have new maps default to that mode) – that setting doesn’t exist.

[Chris]

Hi,

I’m not sure what you mean – I can see ‘terrain’ as an option in the ‘map’ dropdown where you select the map type. It still seems to be present in both the backend editor and the frontend.

Are you using a custom style? If so, those can only be applied to ‘roadmap’ maps. Google also released a new API version yesterday which seems to have a lot of internal changes (and some bugs), so it’s possibly related to that.

[Chris]

Hi,

I didn’t notice they’d changed from 25,000 free maps per day to 25,000 per month!

Static maps may help, since they have a 100,000 monthly free quota. Or, if your individual maps have only 1 POI, you could use the Google embed API (https://developers.google.com/maps/documentation/embed/guide) which seems to have virtually unlimited free usage.

I’m working on adding both of these options to MapPress as well. I’ll be out of the office until May 15, and it will take a few days after that.

[Chris]

Hi,

That message caught me by surprise as well. I assumed they were heading in that direction when they demanded the use of API keys, but I didn’t know when or if they would require billing info.

There’s unfortunately no way to reduce the API calls – MapPress already uses the API as sparingly as possible. One suggestion: if you show maps in post excerpts you might consider limiting them to just single-post detail pages.

Google does provide a ‘user guide’ that explains how to estimate your future billing:

https://cloud.google.com/maps-platform/user-guide/pricing-changes/

It looks like the first 28,000 maps are free. In months where your site gets heavy traffic and exceeds that free allowance, they show $7 per 1,000 map loads.

[Chris]

Hi,

Sorry, but I don’t know. Where does the lat and lng end up? If it’s stored in custom fields, you could use the ‘geocoding’ feature (see the docs & settings screen) to generate a MapPress map when the post is saved/published.

[Chris]

Hi,

I see the map on your site. If you’re still not seeing it, try clearing your browser cache, it may sometimes cache old javascripts.

[Author]

Posts