James Barker

Ah phooey, scratch that last comment. It worked for a few minutes, now it doesn’t – back to the REQUEST_DENIED when trying to enter a zip code or street address. I’m at a loss…

Following up: I created the additional locations and noticed I have a few places that have URL’s with -1 on them (see the screenshot), yet the location in the neighborhood doesn’t. It doesn’t appear to be a problem other than on this particular page there are no icons shown for matches like there are on others, yet when clicking the search button, matches show up.

Is this anything to be concerned about and/or is there a way to change the page url (I’m guessing not as there doesn’t appear to be a wp “page,” per se.) I don’t plan on using the location page (shown) as all my searches are done from individual pages, but I am considering tagging the page I just created with the [gd_location_switcher] for users information and it leads to it when any of the neighborhoods are clicked.

Last but not least, I was able to search by street and zip code last night but it seemed to be working intermittently and I’ve been getting “Search was not successful for the following reason :REQUEST_DENIED” errors.

Thanks.

Ok, just to follow up – I noticed late yesterday that some tests added as new places, despite showing NV as the state instead of Nevada on the address when filling it out, did indeed create a separate location with “Nevada” in the multilocations management section (as noted previously noted, the few thousand I uploaded via CVS were all NV.) To prevent this from becoming a headache for those searching, I should, in theory, be able to resolve this by creating a new location for each city with “Nevada” instead of NV and then merge them, setting the “Nevada” one as the default. From thereon, any new listing manually added that Google maps tags as Nevada will simply fall into an existing location (unless the city doesn’t exist), correct?

@#!$@#$!!!

Ok, this can be closed. I found the problem – it’s all on Yelp.

For those having the same problem, this is the message I was getting when I went to copy the client secret (see attachment). Unfortunately, what they tell you to do doesn’t work and you have to use the client secret anyway instead of the suggested API Key. Why oh why they will tell you to do this and then not have it work… I need a beer. Make that six.

Thanks, I had missed that one having assumed unchecking test payment in gateway payments would disable it. Fixed!

Ok, if that’s the case then something still isn’t working correctly based on my previous response.

I must be missing a setting somewhere, Guust – this is what I have (see attachments). Where else would it need to be changed?