Forum Replies Created
-
Posts
-
Re-reading my posting, I think that this statement is unclear:
“so I changed the hook to match tribe_events_google_maps_api, and this resolved the problem, at least as far as I could test.”
In testing, I modified the plugin code, but ultimately I’m using the unmodified code with the additional wp_script_is logic.
Hi Nico,
I have included this action snippet in my functions files, and with a small modification I believe I have the error resolved:
(!wp_script_is( ‘tribe_events_google_maps_api’, ‘queue’)) && (!wp_script_is( ‘tribe-gmaps’, ‘queue’)) )
As to why I am looking at ‘tribe-gmaps’, I haven’t looked through much of the code for event calendar pro, but that was the only enqueue I found for the gmaps api (in Tribe_PRO_Template_Factory::asset_package(), in my 3.9.3 it is l.63-71), so I changed the hook to match tribe_events_google_maps_api, and this resolved the problem, at least as far as I could test.
I’m open to the idea that the problem is in the theme, but I haven’t looked around in events pro enough to know what the real issues is, but it looks like the TribeEventsGeoLoc calls the asset_package when it does geolocation-based filtering, and this pulls in the maps api, but using a different handle.
We did a clean uninstall & reinstall & all is well. Andy was right, EC Pro was not activated.
Thanks
Susan
