You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
We've had a series of reports from people having problems with Geolocation when they also have NeatlineFeatures installed. The combination definitely breaks Geolocation, I'm not sure whether or not it affects NeatlineFeatures (the reality could depend on which is getting loaded first).
The problem seems to be that both plugins load the Google Maps API, and it doesn't react well to that. It'd be nice to find some way to get the two to work together, or otherwise to prevent having them running together.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've had a series of reports from people having problems with Geolocation when they also have NeatlineFeatures installed. The combination definitely breaks Geolocation, I'm not sure whether or not it affects NeatlineFeatures (the reality could depend on which is getting loaded first).
The problem seems to be that both plugins load the Google Maps API, and it doesn't react well to that. It'd be nice to find some way to get the two to work together, or otherwise to prevent having them running together.
The text was updated successfully, but these errors were encountered: