Title: Oops! Something went wrong Last modified: March 6, 2017 --- # Oops! Something went wrong * Resolved [akacruiseman](https://wordpress.org/support/users/akacruiseman/) * (@akacruiseman) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/) * Hi, Just installed the app. I think I have my ducks in a row but the map starts to load, then the Oops message comes up. As you recommended in other posts on the forum: cache is cleared, this happens on two different browsers on two computers, deactivated and reactivated, deactivated and uninstalled and downloaded and reinstalled again with same results. I checked the footer.php and that is okay also. * Thanks, Jim Viewing 15 replies - 1 through 15 (of 15 total) * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8880853) * Hi Jim * Thank you for getting in touch with us. * Please send me a link to your map so I can look into this for you? * Thread Starter [akacruiseman](https://wordpress.org/support/users/akacruiseman/) * (@akacruiseman) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8884416) * Oh Man, I forgot that link. Sorry. [https://vfwpost12055.org](https://vfwpost12055.org) * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8885841) * Hi Jim * Not a problem 🙂 * The Google Maps API is returning the error ‘ApiNotActivatedMapError’ on the page, which results in your map receiving the ‘Oops!’ error. * Please login to your Google Developers Console, go to ‘Libraries’ and click on the ‘Google Maps JavaScript API’ service. Then click ‘Enable’. * The map should now display as expected. * I hope this helps? * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8885852) * We’re having the same issue. Just purchased the pro version last week. If we set the jQuery versioning option to ‘Yes’ for “Over-ride current jQuery with version 1.11.3” then we get the same issue as above. If we leave it turned off then the map page is unresponsive. * We’ve checked all API settings and they are setup properly(based on plugin documentation). * Link to map – [http://habershamhome.ddns.net/dealer-locator/](http://habershamhome.ddns.net/dealer-locator/) * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8885861) * Also JarryD just saw your response and we have made sure that ‘Google Maps JavaScript API’ service is enabled and still having error. In the source code the script tag that loads the maps api is missing the API key. * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8886538) * We installed this plugin [https://wordpress.org/plugins/api-key-for-google-maps/](https://wordpress.org/plugins/api-key-for-google-maps/) and it appears to fix the “Oops” message. However once we get to the map the search functionality of the map is not working with zip codes. It will work with“ Use my current location”, but it shows the user as being in the wrong location. IE we’re in GA working on this and every time we use the “Use current location” it is showing us as being in OK. * My IT guy is telling me: “It appears that isset($wpgmza_settings[‘wpgmza_settings_remove_api’]) in wp-google-maps-pro.php on line 3469 is causing wp_enqueue_script(‘wpgmza_api_call’,… etc) not to run, which is what appears to add the maps api to the web page. So for whatever reason wpgmza_settings_remove_api is false when it needs to be true. Actually, nope, short circuited the conditional and ran wp_enqueue_script(‘wpgmza_api_call’,… etc) directly, but it didn’t work.” * ~ Sorry for all the replies, trying to get this resolved and keep you guys in the loop of what we’ve tried to troubleshoot on our end. * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8886733) * So we’ve finally got something that is working. A little bit of a ghetto setup, since this will be undone on the next plugin update. So we’re hoping that you guys address this ASAP. Currently forced to use [https://wordpress.org/plugins/api-key-for-google-maps/](https://wordpress.org/plugins/api-key-for-google-maps/) plugin to get past the API issue. To resolve the Store Locator Search functionality issue we encountered we had to correct some of the code in the plugin itself. * In wp-google-maps-pro/js/core.js line 269 assigns the value of wpgm_lng = checker[ 1]; However, if a user just puts in a zip code, checker[1] is undefined. This causes the code in line 276 to malfunction calling .match() on an undefined object which throws an error and haults code execution causing the map not to update with the user’s closest stores. This can be fixed simply by changing lines 266- 269 to * ``` var wpgm_lat = checker[0] || ""; var wpgm_lng = checker[1] || ""; ``` - This reply was modified 9 years, 3 months ago by [habersham](https://wordpress.org/support/users/habersham/). * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8890536) * Hi [@habersham](https://wordpress.org/support/users/habersham/) * Unfortunately these forums only support the Basic version of our plugin. Please get in touch with us on [https://www.wpgmaps.com/contact-us/](https://www.wpgmaps.com/contact-us/) so that I can assist you further? * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8890659) * [@jarryd](https://wordpress.org/support/users/jarryd/) * Ok, I emailed Nick directly last night. I’ll get in touch via that contact page now. For the record, these issues are occurring with the Pro add-on activated and deactivated… * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8891254) * Not a problem, I’ve received your mail and will get back to you there ASAP 🙂 * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8895497) * [@jarryd](https://wordpress.org/support/users/jarryd/) * Did you get my response on the email? Code Cabin won’t let me register to login to reply there. * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 3 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8895910) * Hi there * We’ve received your ticket and will continue communication via the ticket 🙂 You can reply to our tickets above the line, via the email that gets sent to you. * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 2 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8936113) * [@jarryd](https://wordpress.org/support/users/jarryd/) * Hey Jarry, * What’s the status of our ticket. I haven’t received any further communication for this issue, the last post on the forum here is the last time I heard from you guys. As I mentioned before I’m unable to login to code cabin to see the actual ticket. Any help? * – Brandon * [Jarryd Long](https://wordpress.org/support/users/jarryd-long/) * (@jarryd-long) * [9 years, 2 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8945821) * Hi [@habersham](https://wordpress.org/support/users/habersham/) * Please send me your ticket ID so that I can address this for you ASAP? * You won’t need to login to our support desk to reply to the ticket, everything will get processed via the emails that you send us. * [habersham](https://wordpress.org/support/users/habersham/) * (@habersham) * [9 years, 2 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8945834) * [@jarryd](https://wordpress.org/support/users/jarryd/) * Ticket ID – #16815 Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘Oops! Something went wrong’ is closed to new replies. * ![](https://ps.w.org/wp-google-maps/assets/icon-256x256.png?rev=3058363) * [WP Go Maps - Google Maps, OpenStreetMap, Leaflet Map](https://wordpress.org/plugins/wp-google-maps/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-google-maps/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-google-maps/) * [Active Topics](https://wordpress.org/support/plugin/wp-google-maps/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-google-maps/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-google-maps/reviews/) * 15 replies * 3 participants * Last reply from: [habersham](https://wordpress.org/support/users/habersham/) * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-22/#post-8945834) * Status: resolved