-
Posts
-
Hi,
I’ve recently migrated a site from a staging domain to a live domain and the Google Maps content element is now broken. I’ve updated to the latest version of Enfold and entered a Google Maps API Key and the element is still not displaying the map.
Here is a link to the page I’m working on: http://www.yourcaninephd.com/contact-us/
Any help you can offer will be greatly appreciated. Thanks!
– j
Hey BlackThundarr,
Please post us your login credentials (in the “private data” field), so we can take a look at your backend.
Login credentials include:
- The URL to the login screen.
- A valid username (with full administration capabilities).
- As well as a password for that username.
- permission to deactivate plugins if necessary.
Best regards,
YigitI’ve set up the KriesiSupport user on the site and provided the user creds. Please let me know if there’s anything else I can do on my end to help. Thank you very much!
– j
Hi!
Please take a closer look here
to understand how to register properly for the API KEY.
Thanks a lot
Regards,
BasilisI followed the steps laid out above and created a new API key. Still getting the same broken element on my live site.
Conversely, you can see the staging site is displaying the map correctly, here: http://www.caninephd.imperialwerewolfoctopus.com/contact-us/
Granted, the staging version is using an older version of Enfold as its parent theme.
Hi,
There are some errors showing up in canine.js, can you try to replace all instances of $ to jQuery. Let us know if this is changed and if the problem still persists.
There’s a lot of
Best regards,
NikkoOk, I’ve made that change, but it’s had no effect on the map element. It did fix other things, though. So thanks for that!
The map element seems to be encountering API key errors. I’ve created and entered a new API key and still no luck.
Hi!
They show up fine on my end, attached a screenshot in private content field.
Please flush browser cache and refresh your page a few times – http://wiki.scratch.mit.edu/wiki/Hard_Refresh
Cheers!
YigitI’ve done the hard refresh and still no love. I’ll try again, though.
I’ve pasted two links in the Private Data section, showing the site I’m working on. The map that is displaying is one I’ve placed using the Google Maps embed code. I’ve also pasted a sg showing the error console. Thanks!
Hi!
@blackthundarr You are currently using an older version of the theme. Please update Enfold to the latest version 3.8 – http://kriesi.at/documentation/enfold/updating-your-theme-files/ then refer to this post – http://kriesi.at/documentation/enfold/how-to-register-a-google-maps-api-key/Best regards,
YigitHi Yigit,
I’ve got v3.8 installed, though. I’ve attached a screenshot. Could the issue be arising from my child theme being based on an earlier version? That seems unlikely, but never hurts to ask, I guess. Shasta!
Hey!
It still seems like you are using 3.6.1 – http://i.imgur.com/ZByFxm6.png
You might have two Enfold parent themes installed. If that is the case, please remove the old one :)Cheers!
YigitAh, I see the confusion. That image is from the staging site, where the map is actually working, weirdly enough.
The url for the live site is yourcaninephd.com/contact-us/
Hi!
Can you please start a new thread and post temporary admin logins in private content field?
If you post them here, they will be visible to the creator of this thread as well.Regards,
YigitI’m actually the author. There’s login creds in the private data area from my post back on the 25th. Let me know if you want me to still start a new thread, though. Shasta!
– j
Hi!
Sorry about that :)
When i deactivated all active plugins, it did work fine. I suspect ” Typekit Fonts for WordPress” plugin is causing the issue. Please deactivate all active plugins one by one to find the culprit.Cheers!
YigitThanks Yigit!
I tried TypeKit and that didn’t do the trick. I don’t wanna fiddle with any plugins during the work day, as the client is actively updating the site. I’ll go through it this evening and let you know what I come up with. Shasta!
– j
- You must be logged in to reply to this topic.