Confusing Message from New WP Store Locator Task Steps

  • Resolved meruth101

    (@meruth101)


    2 weeks, 4 days ago

    Hello – I see there has been a major update to WP Store Locator. I am confused by a missing task step it now says we need to verify. First Question: should all our settings including Google API info have been automatically transferred/translated over to your new system? Second Question: You have 3 tasks that need to be done, it shows we have 2 of the 3 done. The missing step is “Choose a Map Service” but if we all ready had that all set up in your previous WP Store Locator why is it sparking an issue now? Also when I do click it – it does show Google Maps with our Browser and Server Key info all ready in there and a blue button to “Save and Verify”. When I clicked that I got an error message that says:
    The Google Geocode API returned the following error for the server key.
    Error code: 403

    And when I look at the reason it says this with an IP Number – I removed IP numbers for purposes of this public message but all 3 places it showed an IP number they where all the exact same IP Number:

    Reason: The provided API key has an IP address restriction. The originating IP address of the call (IP number) violates this restriction.

    You have restricted this API key to an IP address that differs from where the API call originated (IP number). If you change the IP restriction to (IP Number), the error should be resolved.

    So I am confused – if the IP Number I am supposed to change it to is the same exact IP Number from where the API call originated – why are we getting an error message and if it’s showing what we are supposed to change the IP Number to and it’s the same exact number, what is it supposed to be change to?

    Thank You for any help you can give on this very confusing task.
    Ruth

    • This topic was modified 2 weeks, 4 days ago by meruth101.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Tijmen Smit

    (@tijmensmit)

    2 weeks, 4 days ago

    From which version did you update?

    Is the IP address you are currently using to restrict the API keys in the Google Console different then from the warning? If so, then add them.

    The wording of the task should indeed improve for users who upgrade. The task is there to make sure the store locator can function, and in your case Google seems to think the keys are invalid. If the browser key does pass the test, then the map will load just fine, but without a valid server key you won’t be able to create new locations.

    Maybe no new locations have been created ( the only time a server key is used ) for a while in v2, and the ip address from the server changed, so you never noticed there was a problem with the key?

    If adding the IP from the screenshot to the api key doesn’t resolve this, then you can either use OpenStreetMap ( no key required ), or open a support ticket here.

    Plugin Author Tijmen Smit

    (@tijmensmit)

    2 weeks, 4 days ago

    “but if we all ready had that all set up in your previous WP Store Locator why is it sparking an issue now”

    I checked the v2 -> v3 migration code, and it checks in the background if the server key is valid or not during the update, and if that check fails then you’re asked to select a map provider as opposed to first task done.

    I agree this should be communicated clearer if it detects an invalid key ( or so Google says ), instead of just asking you to select a map provider.

    This will be changed very soon!

    Thread Starter meruth101

    (@meruth101)

    2 weeks, 4 days ago

    OK – so I think what I am reading in your answers is that I need to check the “Server Key” Google had supplied to us, that it is the same one we are currently using, and if it’s different – I need to take what Google shows in their portal and update it in WP Store Locator?

    Thank You,
    Ruth

    Plugin Author Tijmen Smit

    (@tijmensmit)

    2 weeks, 3 days ago

    No, try this instead.

    – Go here https://console.cloud.google.com/apis/credentials
    – You should see two api keys there, click on the one that you’re using for the server key ( show key on the right side will show you the key itself ).
    – Click on the name of the one that shows the server key that you’re using and scroll down to ‘IP address restrictions’.
    – Click on “add” provide the IP mentioned in the error, then “Done” and “save”
    – Wait a few minutes and click on “Save and verify” again on the home page in the store locator

    Thread Starter meruth101

    (@meruth101)

    2 weeks, 2 days ago

    Thank You for this directions of what to do. The person who our Google account is under is on vacation and I cannot complete these steps till he is back. When I go to the link you provided it is is saying I need to enable MFA which I can’t do as the account is under his phone number and since he is on vacation I won’t be able to continue until he is by his phone. I will continue this when he gets back.

    Thread Starter meruth101

    (@meruth101)

    2 weeks, 2 days ago

    OK we know have some new problems. I updated to your latest version 3.0.1 and when I went to view on our website – the map is gone. I rollback to 3.0.0 and when I look on Chrome I can see the map but if I look with Firefox the map does not appear. BTW after I rollback to version 3.0.0 I did clear the cache in the browsers before attempting to look.

    Plugin Author Tijmen Smit

    (@tijmensmit)

    2 weeks, 2 days ago

    It does sound like a caching problem, do you have any caching plugins active on your site? Can you flush the cache, or check in the admin site of your site if you can flush anything?

    Plugin Author Tijmen Smit

    (@tijmensmit)

    2 weeks, 2 days ago

    If flushing the cache doesn’t resolve it, then update to 3.0.3 which I just released. This adds a different hash to the loaded files, so it should break the cache and force the browser/server to always load a the newer version.

    • This reply was modified 2 weeks, 2 days ago by Tijmen Smit.
    Thread Starter meruth101

    (@meruth101)

    2 weeks, 2 days ago

    Hello – this morning I did see the map on Firefox. Later today (end of business day) I will update to the 3.0.3 version.

    Appreciate all your help that you re giving all of us.
    Ruth

    Thread Starter meruth101

    (@meruth101)

    2 weeks, 1 day ago

    Hello – I did update to the 3.0.3 version and it is displaying properly on both Firefox and Chrome.

    Now just waiting for the person to return from vacation so I can address the “Server Key” Issue. I’ll keep you updated.

    Thread Starter meruth101

    (@meruth101)

    3 days, 9 hours ago

    Hello – Wanted to give you an update – we have resolved the Issue – API key has been verified and we are good to go. Thank You so much for your clear directions on what we needed to do – it was very helpful.

    Thank You
    Ruth

    Plugin Author Tijmen Smit

    (@tijmensmit)

    3 days, 8 hours ago

    Happy to hear it’s resolved!

    If you run into any other issues, then let me know 🙂

Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.