Supermap grayed out with “For Development Purposes Only”

Did you add a billing option in Google?

The Maps api is no longer free, so they ask you for a billing information to charge once you exceed a certain amount of data (for big sites mostly). You may need to generate a new API key as well.

With that said, it is not a problem from WP-Property side (I suppose)

Hi Eric: Thanks for the reply. Yes, I did add the billing info in Google and generated a new API key. I entered it into WP Property in both the “server” and “browser” locations with the same result. I’m wondering why my WP-Property installation is not showing just one location for the API Key, but rather two (server and browser keys) as was done years ago when I set this site up.

Hello, All.

You could find In Settings/top Help tab tutorial about API keys set up. You could use the same key in both fields.

To check if your API key is working try to click on Revalidate button in Settings/Help tab. You will get some notice there, which will describe the situation.

Also in some topic was mentioned that resaving permalinks helped.

Regards.

I believe I found the culprit in the Denali theme. I was having the same issue and noticed JS console was showing a Google Maps warning saying “NoApiKeys”. I could see in the source that there was a call to the following address without any API Key added:

https://maps.google.com/maps/api/js
?sensor=true

I wondered if there’s an old deprecated duplicate call to the maps API without the Key that is tripping the map’s developer mode. The fact that the script path above is setting “sensor=true” indicated to me it’s an old forgotten reference from years past since sensor is no longer required according to Google’s documentation.

So I started looking in the Denali theme (as I see @tomstep is running it like us). I found the reference at line 170 of /themes/denali/lib/classes/class-denali-theme.php

I commented out the following line (class-denali-theme.php:170):
$remote_assets[ 'script' ][ 'google-maps' ] = 'maps.google.com/maps/api/js?sensor=true';

Saved and force refreshed and shazam, both my supermap and listing maps load properly again.

Since the problematic line is in the parent theme, it will be reverted in the next theme update if it’s not corrected on UD’s side before then.

https://actionproperty.ca/rental/map-overview/
https://actionproperty.ca/properties/jackson-3-house-2/

Hopefully this can be corrected and pushed out in the next Denali update.

Thanks.

Hello @nhwp

Thank you for investigating and pointing us to the issue. That will be added to the next release.

Regards.

@tomstep
As Maria said you can use same key in both server and browser field.
But we recommend you use separate key for server and browser for security reason. To avoid unauthorized access with your API key you need to restrict the server key with your server IP and your browser key with your domain.

Do you currently have API key in both fields?

Hello, All.

Denali theme new release is preparing, while you could download latest version from DropBox – https://www.dropbox.com/s/yux6js1i4rup7hw/wp-denali.zip?dl=0

Regards.