Edward Solomon
Forum Replies Created
-
AuthorPosts
-
Hi Stiofan,
We’ve made the decision to localize the GD maps API call to just the GD pages using it so that this conflict doesn’t perpetuate itself across the rest of the site. It’s unreasonable to amend the functionality of other plugins when it is GD making a global call.
Kindly provide a function or code snippet (or point to it in the documentation) we can use to
1. globally dequeue the GD maps API call
2. enqueue the GD maps API call for just the GD pages (we’ll target the pages by ID).Many thanks.
This reply has been marked as private.1. GD set to use Google Maps (to the best of my knowledge) and API key set in GD.
2. Events slug changed to ‘our-events’. API key *cannot* be removed. The API key is mandatory. If the custom API key is removed, an autogenerated key appears and is used by The Events Calendar. The problem with the Google Maps API doesn’t go away.Surely the standalone GD Maps plugin we installed should push the API key to anything that requires it?
Note that now there is no map appearing for GD either.
I’ve done that. The problem is that now GD has the Maps API key set, the Events are broken because there is an error in the console, which shows the page is calling the Maps API multiple times. This doesn’t happen when the key is not set in GD. If you view the page of any event, look at the console and you will see the resulting error. The problem manifests itself particularly on Microsoft Edge and Apple Safari, which renders many Windows and Mac users prone to this problem.
Have changed the slug for The Events Calendar, but GD is still using Open Streetmaps instead of Google Maps.
This reply has been marked as private.Better – got 14 of the 18 in with 3 not being added and 1 added but only partially. We’ll sort these out today.
This reply has been marked as private.This reply has been marked as private.Confirmed working. Thanks.
This reply has been marked as private.This reply has been marked as private.Hi Stiofan.
That definitely appears to have cleared things up. There were a couple of hurdles with updating to GDv2, as it apparently didn’t seem to like PHP 7.1, which meant downgrading the account to PHP 7.0 before the plugin would activate.
Smooth sailing after that, though.
This reply has been marked as private.This reply has been marked as private. -
AuthorPosts