Issue with creating and using new server API key after update to 2.2.17

  • Drew75

    (@drew75)


    5 years, 5 months ago

    I’m currently running WP Store Locator 1.2.25 and have recently installed the CSV Manager add-on that is requiring me to update to version 2.2.17 in order to use. When I updated the plugin to 2.2.17, it broke my store locator or the API key I was currently using and was displaying a development purposes message over the map area. I noticed in the settings where WP Store Locator was prompting me to add a server API key and when I went to the Google API console, created a new API key and enter it after updating to the latest version, it seems to be breaking my map. Markers do not display as they should be displaying. I set a restore point and since reverted back to the previous version of the plugin so my map will work properly.

    Any ideas what I could be doing wrong? Thanks!

    The page I need help with: [log in to see the link]

Viewing 7 replies - 16 through 22 (of 22 total)
1 2
  • Thread Starter Drew75

    (@drew75)

    5 years, 4 months ago

    That’s strange. I never got an undeliverable message. I just resent the email to you.

    It’s not that a location doesn’t display, it’s that when you go to the page itself, the map doesn’t generate properly and what you get is what is displayed in the screen shot I linked to previously.

    I have since restored the website back to the previous version of the plugin because I can’t have the locator not working for visitors to the website.

    The map should load up with many markers and be panned out to show the markers across multiple countries, such as it does right now before updating the plugin version and inputting the API keys.

    http://thegalley.com/find-a-galley-showroom/

    Max search results: (25),50,75,100,200
    Search radius options: 10,25,(50),75,100,200

    • This reply was modified 5 years, 4 months ago by Drew75.
    Plugin Author Tijmen Smit

    (@tijmensmit)

    5 years, 4 months ago

    The default values should be set between [] not ().

    When I checked the AJAX request it included NaN, so that’s why I asked about that. You didn’t modify any of the code, or are using any filters to changes used values.

    Thread Starter Drew75

    (@drew75)

    5 years, 4 months ago

    Are you saying if I change the default values to be set between [], that the problem should then be resolved?

    Plugin Author Tijmen Smit

    (@tijmensmit)

    5 years, 4 months ago

    The value shouldn’t be between () anymore after the update, the update code should fix it. But maybe moving back between the 1.x version and 2.x version the options got mixed up.

    So it won’t work with (), and that’s likely why it shows NaN in the ajax request breaking it. So yes, settings the default between [] is required for the 2.x version.

    Thread Starter Drew75

    (@drew75)

    5 years, 4 months ago

    Tijmen,

    I ran the update again, inserted my API keys for sever and browser and checked the Max search results and Search radius options and they show the following…

    Max search results: [25],50,75,100,200
    Search radius options: 10,25,[50],75,100,200

    I’m not sure why they displayed with the () last time, but they seem to display correctly now, yet I’m still getting the same result when the map loads.

    Is it possible I’m using incorrect API keys? The email with the screen shots I tried sending to you were returned undeliverable.

    Plugin Author Tijmen Smit

    (@tijmensmit)

    5 years, 4 months ago

    Are you still using the latest version now? The map loads fine for me, and searching for NY also returns results. If so, then try private mode in your browser.

    If there are any issues with browser keys, then it should show up in the browser console.

    I do see you’re using a CDN, do make sure to flush that cache as well after updating the plugin.

    tharakade

    (@tharakade)

    5 years, 4 months ago

    Hi,
    I’m posting under the same thread as I have similar but not exactly the same issue.

    I have WordPress version 5 and WP storelocator Version 2.2.19.

    I entered the browser key without any issues however when I added the server key following error is displayed –

    There’s a problem with the provided server key.

    Error message: This IP, site or mobile application is not authorized to use this API key. Request received from IP address 74.208.57.169, with referer: https://maps.googleapis.com/maps/api/geocode/json?address=Manhattan%2C+NY+10036%2C+USA&key=AIzaSyC26F8W45ZWXk9C_Jc2orCdegJFAXR_kfw.

    Make sure the IP address mentioned in the error matches with the IP set as the referrer for the server API key in the Google API Console.

    I created API for the first time, I called my service provider and reconfirmed the IP it’s hosted in a 1and1 server.

    I have tried creating the key multiple times and created again fresh after removing the old one.

    Please let me know how to fix this issue.

    Thank you.

Viewing 7 replies - 16 through 22 (of 22 total)
1 2
  • The topic ‘Issue with creating and using new server API key after update to 2.2.17’ is closed to new replies.