Google Map Help

Hello.

Please check in your Google account that you have added Maps JavaScript API – https://screencast.com/t/dyQ31N249nY

Let me know how that goes.

Regards.

Yes, as I mentioned I already followed your instructions on the Help tab. I enabled Javascript and Geolocation APIs. Both have zero activity. Geocoding API had activity so I enabled that too and Geocoding is the only one showing any activity.

To be clear, I have all three APIs enabled now and still getting this error:

Google Maps JavaScript API warning: NoApiKeys

https://drive.google.com/open?id=1YjUC9QLExFuHO5mX3mt8b-8K3pPddKsw

• This reply was modified 6 years, 7 months ago by Steven Stern (sterndata).
• This reply was modified 6 years, 7 months ago by miclovin.

I notice in your screenshot that you have Maps Static API and Cloud Storage JSON API enabled. Should I enable them too?

Maps Static API is for PDF add-on and Cloud Storage JSON you do not need.

Just tried to set up Supermap and can’t replicate your issue, here is my test site – https://workspace.uds.io/supermap/

Not sure what else to suggest. What was done on your site when that stopped working? Did you change host provider, add/update plugins?

Regards.

I have not changed servers or made any significant changes recently. 1 plugin was updated on the 20th, User Role Editor, but I think the map problem happened before that. I’ve disabled it but there is no change to the map error.

When the map error first occurred, the message said that I needed to setup my APIs and Billing info. My APIs were already setup and working at that time so I added my credit card to Google Billing assuming that was the problem. That did not work and I tried everything else as initially mentioned.

https://drive.google.com/open?id=1IvPyw9sP-7TttnMcyrcjRKfzr87E0Gzw

Can you give me a link to your site with supermap? Also on your screenshot, I see the question “Do you own this website?” Do you? And what happens when you click OK on that pop-up?

Of course I own the website, here is a link to the supermap. But the problem also exists on all the single property pages:

https://once.ly/jtyB

No API keys error could mean only that you do not set up API keys or make some typo in your settings or some mistake in your Google account. That should be checked directly on your site. You could order paid support and we will check that. Right now I can’t replicate that on my test sites.

My original question was:

Could you please update your Help tab and walk us through a setup from start to finish?

Issue created for our roadmap for the next releases – https://github.com/wp-property/wp-property/issues/572

Thank you for your notes.

Regards.

The problem has been resolved by refreshing the permalinks. It seems every time wp-property is deactivated and reactivated, the permalinks get messed up.

My tech support guy had this suggestion to resolve plugin conflicts with wp-property:

Could you get in touch with WP Property plugin developers and ask them if ud_get_wp_property can be called only on plugin respective pages instead of on entire WP admin and that should hopefully fix the issue?

We need to know where particular that function is causing the issue to get rid of it in that particular place if possible.

Regards.

We are having almost exactly the same problem on our website. Some differences, though… we never opted to purchase Supermap, so we’re using the built-in map function in Version 2.1.4 of WP-Property. I’ve been avoiding upgrading to the current version for fear it might break something (we have a lot of custom code).

You can see the “development map” on our pages, for example, https://seadrift.com/properties/dp109/
Scroll down towards the bottom…

I did get Google Maps API key from Google today and entered it on the Property Settings page. When that didn’t fix the problem, I asked Google for help and they replied:

It seems like the issue is in your plugin. I have checked your website and can see here that the map does not have an API key even if you already added it in the plugin.

Please be informed that an API key is required to use Google Maps Platform products. Failure to use an API key will result in having the daily quota limited to 1. If you exceed this, the Javascript API will return a degraded map with “For development purposes only” error message. For server side requests, this will result to quota error.

Just to set the correct expectation, implementation through wordpress themes/plugins are out of scope for us. Although we would love to help, we lack the knowledge, access to the source code or tools to debug the issues that you encounter with that. Problems with themes/plugins are best to be reported to the ones who developed them.

To explain further on this, the plugin that you are using has a more user-friendly way of adding an API key since you will just put it in an input box and you don’t have to access the codes to add it on your map. However, since that is how the plugin is doing it, there is a possibility that it will not be added in an API key because it was programmed and not done manually.

In a normal JavaScript API implementation, we just add an API key manually in the HTML code like this (we just replace YOUR_API_KEY with our own API key):

<script async defer src="https://maps.googleapis.com/maps/api/js?key=YOUR_API_KEY&callback=initMap"
 type="text/javascript"></script>

Then it will surely work because we added the key ourselves. That’s how it’s being done in a normal way. When I checked your website, the script tag looks like this:

<script type="text/javascript" src="https://maps.google.com/maps/api/js?sensor=true&ver=4.4.2"></script>

——-

Any ideas?

Thanks.

Hello @davidbfox

The previous user reported that the issue was fixed by updating the permalinks. Also, we can’t replicate that issue on our test site where we have set up API keys.

We recommend to use the latest version of the plugin and put customization files into the child theme folder. Also, we can’t support the plugin if the code was customized directly.

Regards.

• This reply was modified 6 years, 5 months ago by MariaKravchenko.