The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Just thought I should add … there no guarantee updating will fix the issue. It could simply be a setting within Maps Marker causing the conflict or maybe it’s a combination of other factors. At this point there is no way to know for sure until variables such as versions being the same are eliminated.
I was investigating this further…
Look what I found in the Maps Marker changelog for version 3.12 released on 3/25/2014:
“improved option “Deregister Google Maps API scripts enqueued by third parties” to prevent re-enqueuing of scripts by also deregistering them”
This option when enabled, if I read it correctly, actually deregisters the scripts the template requires to run when enabled because it uses the Google Maps API.
This option appears to be off by default. I suggest turning it back off since there was no conflict prior to their latest update.
Their setting can be found on their plugin settings page. Search for “Deregister Google Maps API scripts enqueued by third parties”
After you turn this off I suspect the two plugins will work together again.
Hope this helps! Let me know.
You cannot reply to this support topic. Please open your own support topic.