Hi, I’m trying to use the “Google” map type of the Map element, but when I switch over from “Embed” to “Google”, I get a “Oops something went wrong” message on the map itself. I’m providing a valid API key where prompted. I need this map embed functionality to implement a few custom map styles i.e hide POI, etc. Can someone please assist? I’ve seen a few posts of users having this same issue but haven’t found a fix that works.
In most cases, the problem is caused because of the wrong API or the possible restrictions you may apply to the API. I suggest that you start over with the API Key generation from here:
After that please follow the steps below:
- Ensure everything is up to date according to our version compatibility list here. Please follow the best practices when updating your theme and plugins. Click here for more information.
- Ideally use the new Map Element instead.
- Test for a plugin conflict. You can do this by deactivating all third-party plugins, and see if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
- Test the case in an isolated scenario by adding a new page and only adding the Map element while all 3rd party plugins are deactivated except Cornerstone.
If you still have problems kindly get back to us with the result of the steps above and URL/User/Pass of your WordPress dashboard using the Secure Note functionality of the post to follow up the case.
Updated original post. All apps deactivated. I wasn’t able to update my plugins through the dashboard and I don’t have access to the ftp at the moment, but this was an issue even when all my plugins were up to date.
Please update to the latest X and Cornerstone version. X 6.0.4 and Cornerstone 3.0.4 are now available in automatic updates! This release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/). Please do update to the latest version. After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.
You won;t be able to update to the latest since you haven’t validated X theme yet. To validate X properly, please do the following:
1] Please login to your account and assign the license. You need to assign the license to your site using this url: https://www.example.com/. You have to make sure that url you just assign is the same as the one you have in your settings, Settings > General > Site Address
2] Go back to X > Overview again, and insert the license again.
And please review the changes that we made on how you are going to validated your X theme because we made a big change in the process. Please check it out here: https://theme.co/apex/forum/t/setup-product-validation/55
And by the way, switching between Embed to Google Map, you will need to supply the API key, longitude and latitude. You might be displaying the default or invalid coordinates.
Please let us know how it goes.
Okay, thanks so much for the guidance thus far. Everything is updated to latest version. Now, when I use the “Google Map”, it is rendering a blank box in cornerstone, but when I save and go to my live site it is rendering properly. However, once I try and add any JSON custom styles (using the styling wizard, copy and paste the JSON from the page), the map container goes blank on my live site. Any ideas?
I tested the case and I could recreate the issue you are talking about the JSON styling code.
I added a report to our issue tracker. Please stay tuned for upcoming releases to have a fix regarding this.
Unfortunately we can not give any ETA at the moment for a fix, but on each release you can check the changelog for the details and see if the issue is fixed on that particular releases or not.
The Changelog link: https://theme.co/changelog/
Is there any other way I can implement custom styles on maps within the theme that are functioning?
It doesn’t work because there is an error.
Please double check your api key or try to generate a new one.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.