Title: oops something went wrong on localhost Last modified: September 1, 2016 --- # oops something went wrong on localhost * [toimisto](https://wordpress.org/support/users/toimisto/) * (@toimisto) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/) * I cant get the map to display or setup starting point in admin because im just getting something went wrong errors. Is this because im using localhost? * Many thanks for any help and insight! * [https://wordpress.org/plugins/wp-store-locator/](https://wordpress.org/plugins/wp-store-locator/) Viewing 15 replies - 1 through 15 (of 16 total) 1 [2](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/page/2/?output_format=md) [→](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/page/2/?output_format=md) * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509360) * It should work on your localhost. Does it also happen with a default theme, and all other plugins disabled? * Can you check the [browser console](https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis) for any errors? * Thread Starter [toimisto](https://wordpress.org/support/users/toimisto/) * (@toimisto) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509369) * I apparently had disabled the javascript api in console which fixed errors on the webpage BUT I’m still facing same error in wp-admin and unable to setup starting point. * Google Maps API error: MissingKeyMapError * Thanks for your help! * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509370) * Google Maps API error: MissingKeyMapError Isn’t necessary breaking anything, but it’s easy to fix by setting a browser key. You can create one in the Google Console. * The start point doesn’t autocomplete, or simply doesn’t remember what you entered? Can you disable all other plugins to make sure it works then? * Thread Starter [toimisto](https://wordpress.org/support/users/toimisto/) * (@toimisto) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509393) * Im getting the missingkeymap error only on wp-admin thus im not able to setup the location since the input is just showing google error there. But I realised I can override it with the shortcode tag so it’s all good. Thanks for your support and fantastic plugin! * [Marcelaerts](https://wordpress.org/support/users/marcelaerts/) * (@marcelaerts) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509446) * I have the same problem. I can’t safe any settings beacuse of this error. * js?libraries=places&language=en&ver=4.5.3:32 Google Maps API error: MissingKeyMapError [https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error](https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error) * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509465) * [@marcelaerts](https://wordpress.org/support/users/marcelaerts/) you are using the latest plugin version? * You can try and create and browser key [here](https://developers.google.com/maps/documentation/javascript/get-api-key#get-an-api-key). Let me know if that really fixes it. * Other users have reported the issue as well, I just can’t replicate it so far… The key used to be optional ( but recommended ), maybe they made it required now. * I also get the error, but it doesn’t influence anything, I can still save the page. * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509466) * So keys are required [now](http://googlegeodevelopers.blogspot.nl/2016/06/building-for-scale-updates-to-google.html). * > We no longer support keyless access (any request that doesn’t include an API > key). Future product updates are only available for requests made with an API > key. API keys allow us to contact developers when required and help us identify > misbehaving implementations. * [Marcelaerts](https://wordpress.org/support/users/marcelaerts/) * (@marcelaerts) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509484) * I do have the latest software. When I try to add a browserkey in the settings from WP Store Locator I get the following error: * Notice: Undefined index: start_name in /wp-content/plugins/wp-store-locator/admin/ class-settings.php on line 146 * Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/wp-store-locator/admin/class-settings.php:146) in /wp- includes/pluggable.php on line 1167 * After returning to the settings page the browserkey is saved but the start point field is still broken. * [Marcelaerts](https://wordpress.org/support/users/marcelaerts/) * (@marcelaerts) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509485) * Even though I entered a browser key I get the following error: js?libraries= places&language=en&ver=4.5.3:32 Google Maps API error: MissingKeyMapError * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509486) * The start field doesn’t autocomplete, or any value like ‘Amsterdam’ isn’t saved? It should save it, and geocode the value in PHP if the autocomplete function is broken when you save the settings. * I checked the code, and the browser key is included on the frontend, but because it was never required it’s not included in the backend code. I will fix this today. * [Marcelaerts](https://wordpress.org/support/users/marcelaerts/) * (@marcelaerts) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509507) * Thanks. * [webnique](https://wordpress.org/support/users/darius1983/) * (@darius1983) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509509) * *** Hot fix for those who can’t wait for the new release (will be overwritten on update) *** * **Find**: /wp-content/plugins/wp-store-locator/admin/class-admin.php * **Line**: 354 * **Replace** * `wp_enqueue_script( 'wpsl-gmap', ( '//maps.google.com/maps/api/js?libraries=places& language=' . $wpsl_settings['api_language'] ), false, '', true );` * **With** * `wp_enqueue_script( 'wpsl-gmap', ( '//maps.google.com/maps/api/js?libraries=places& language=' . $wpsl_settings['api_language'] . wpsl_get_gmap_api_params( 'browser_key')), false, '', true );` * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509510) * I’m going away for the weekend, and since I also want to include some other fixes in the update, I don’t have enough time left to test everything properly. So an official update will have to wait till Sunday / Monday. * But you can easily add the browser key in the code yourself by opening the /admin/ class-admin.php file, then look for [this](https://plugins.trac.wordpress.org/browser/wp-store-locator/tags/2.2.2/admin/class-admin.php#L354) line ( the code on line 354 ), and replace it with this. * ``` wp_enqueue_script( 'wpsl-gmap', ( '//maps.google.com/maps/api/js' . wpsl_get_gmap_api_params( 'browser_key' ) . '&libraries=places' ), false, WPSL_VERSION_NUM, true ); ``` * [webnique](https://wordpress.org/support/users/darius1983/) * (@darius1983) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509542) * When saving a new post or a post where latitude and longitude is missing we now receive the following error: * The Google Geocoding API returned REQUEST_DENIED. * Error message: This IP, site or mobile application is not authorized to use this API key. Request received from IP address XXX, with empty referer * Any suggestions? * Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/) * (@tijmensmit) * [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/#post-7509551) * You filled in both the server and browser key fields? * Are you sure the key you filled in the server key field is actually a server key and not accidentally a browser key? Can you try to generate a new one, this sometimes does fix errors like this. Viewing 15 replies - 1 through 15 (of 16 total) 1 [2](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/page/2/?output_format=md) [→](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/page/2/?output_format=md) The topic ‘oops something went wrong on localhost’ is closed to new replies. * ![](https://ps.w.org/wp-store-locator/assets/icon-256x256.jpg?rev=1007784) * [WP Store Locator](https://wordpress.org/plugins/wp-store-locator/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-store-locator/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-store-locator/) * [Active Topics](https://wordpress.org/support/plugin/wp-store-locator/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-store-locator/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-store-locator/reviews/) * 16 replies * 4 participants * Last reply from: [webnique](https://wordpress.org/support/users/darius1983/) * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/oops-something-went-wrong-on-localhost/page/2/#post-7509583) * Status: not resolved