Google Maps Error in Event listings

@koolkatdesign

The console shows:
Google Maps API error: MissingKeyMapError https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error
Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys

Your current Google Maps API key may have restrictions on the URL. I recommend deleting and create a new Google Maps API to use with no restrictions:

Click here and follow the instructions provided:
https://developers.google.com/maps/documentation/javascript/get-api-key#get-an-api-key

Copy your API key once you’ve created one.

To enter your Google Maps API, navigate to your Timely Dashboard > Events > Settings > Google Maps API Key (Get an API key) > paste your API key

Then scroll down and click on the [Save Settings] button.

TY so much for the quick response. I created a new API key and that fixed the issue.

Having the same error (everything worked ok before), but the settings page is now empty; nothing to click on to re-enter the API key.

Hi @localcause,

This is due to your hosting’s PHP version. We recommend that your host use PHP version 5.6 upto 7.0 — but not 7.1 as it is currently ustable with the plugin. Please check and if you have the same problem, please log into your Timely account and open a ticket by clicking on the Get Help link, or click here: https://dashboard.time.ly/account/get-help.

Downgrading from 7.2 to 7.1 not fix the problem. Instead, it wiped out every single event that I had already published.

If the plugin doesn’t work with the current version of PHP, it would seem that it’s the plugin that isn’t stable, not the other way around.

@localcause

Downgrading your host’s PHP version doesn’t wipe out events. Deactivating, then deleting your plugin does. If you deleted our plugin without consulting us, then your events would be deleted. If we advise you to do a reinstall of the core calendar plugin, there is a specific way to do so, that will preserve your events, and we always advise making a backup of your database before proceeding.

Again, the solution to the problem you described was to downgrade 7.0 — not 7.1.

I also advised that you open a seperate for your particular issue.

PHP version 7.1 and above has caused problems with other plugins, not just ours, and our development team is currently working on making the core calendar plugin compatible with the latest and newest version of PHP, which is now pending release. The release date is TBA.

Hi Sunny,

I just updated our AccessPress Parallax theme and am now getting a fatal error that says:
Fatal error: Uncaught TypeError: Argument 1 passed to Ai1ec_Exception_Handler::handle_exception() must be an instance of Exception, instance of ParseError given in /home/nsteen5/public_html/wp-content/plugins/all-in-one-event-calendar/lib/exception/handler.php:191 Stack trace: #0 [internal function]: Ai1ec_Exception_Handler->handle_exception(Object(Parse

Our serve is running php 7.0. Please help asap

Error)) #1 {main} thrown in /home/nsteen5/public_html/wp-content/plugins/all-in-one-event-calendar/lib/exception/handler.php on line 191

FYI: We have WordPress 4.9.4 running AccessPress Parallax theme version 1.60 causing the conflict with the all-in-one-event-calendar plugin.

Hi @koolkatdesign,

As per our support ticket, it appears to be a conflict and the only way to fix this is to switch out your theme.. Howerver, try switching your PHP version to 5.6 and this may help fix the problem also.

Switching themes is not an option at all!!! Are you planning to work on a solution to resolve the conflict? I believe this happened previously (at some point in the last year or so) and you provided a free fix with a plugin update. I love your app and we can’t change our theme. If not, should I contact the theme developer? Is it an issue on their end?

It seems the error may have been due to the google font code I added to the header.php. once I removed that the error is gone now.

@koolkatdesign, thankyou for the update. In this case it was probably a duplicate API detection, and this gets blocked by Google.