• Resolved ChrisHPZ

    (@chrishpz)


    After having gone through the API Key setup 3 times, I was about to give up and move on. But the “Aries / Italian” in me just wouldn’t have it. If the google map isn’t showing up in the backend, try recreating an API Key via the usual steps, but leave the referrer blank. That’s what worked for me. I wasn’t sure where to post this, so I put it in the support tab for anyone else having problems. Big thanks for the plugin Google Maps Builder plugin team.

    https://wordpress.org/plugins/google-maps-builder/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Glad to hear you got it working. These are our docs on creating your key, note that you’ll need BOTH the Maps API and the Google Places Web Service API enabled to get all the features of Maps Builder:
    https://wordimpress.com/documentation/google-places-reviews/creating-your-google-places-api-key/

    If you’re enjoying Maps Builder and appreciate our support, we’d love a kind review from you here:
    https://wordpress.org/support/view/plugin-reviews/google-maps-builder

    Thanks!

    This post helped me a lot. I was a day into this and I couldn’t see maps on the Map Builder, the Edit Map page, and definitely not on a WP page.
    I regenerated the API key to get a new number, which got the Maps Builder to connect properly. I got a momentary flash of one map on the edit page so I figured things would work.
    The other thing I discovered was that Maps Builder does not seem to like latitude and longitude in degree/minutes.seconds format. As soon as I switched to decimal format the maps and the markers appeared.
    I think this should be documented clearly somewhere, since it could (and did!) cause a lot of user frustration. Or you guys could simply change it to read both formats.
    Thanks!

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Hi @wolfung were you entering long/lat manually into the fields? If so, why? We have so many tools built in to create markers without having to think about the long/lat fields on purpose to avoid those kinds of frustrations.

    But the frustration with the Google API keys is persistent. We continue to update our docs to be as explicit as we can because we know it’s a major pain-point that we don’t have a lot of control over.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Finally got this to work’ is closed to new replies.