Kendra
Forum Replies Created
-
Posts
-
I’m still getting the same error even after creating a new API through GD while logged in to google. I double checked that the correct APIs were enabled and it’s connected to the same project which has the billing account linked. Anything else you can think of?
Is there any other reason this error would appear? Google geocode failed: REQUEST_DENIED
What is the error message if my address format is incorrect?
I gave that a shot but still got the same error. I’ll wait a half hour and try again. In the meantime, can you confirm that I should be able to import listings without latitude and longitude and have them geocoded in the import?
Perhaps this part of your V2 documentation should be completed:
https://wpgeodirectory.com/docs-v2/geodirectory/settings/import-export/
FAQ
Does GDV2 Geocode? Reverse Geocode?Geocoding is when address data is used to identify the latitude and longitude of the address.
I figured out the error – it’s the lack of latitude and longitude. (I went cell by cell on a new row changing it from the exported data to my data until I found the errors; then I confirmed by pasting in fake lat/long in my import test and they all imported fine.)
I’m a bit confused what to do now, as your documentation says I can use geocoding by google to complete the lat/long. As I’ve stated before, I have an API with billing connected to this project. I have the proper APIs enabled. The error for geocoding is this: “Google geocode failed: REQUEST_DENIED”.
Which columns are out of order? I just exported the current listings again and compared them and they look the same as my importtest file to me.
Yes, I did follow the recommended procedure. The errors I’m describing appeared when I did Step 6 of “Merge A Test Set of 5 Records into the Exported Listings file”
This reply has been marked as private.Alex,
I am not sure why you’re sending me to that link – it doesn’t have any info about invalid characters in a CSV file and I am not getting the “not a valid csv” error mentioned in that link. The only time I had a problem uploading it was to the support form. Is there some reason why a CSV file is blocked from being added to a support request? See attached screen shot.
When I upload it to import my listings to GD, I got the error described in my initial post “error: 5 / 10 item(s) could not be added due to blank title/invalid post type/invalid characters used in data.”
Kendra
This reply has been marked as private.Got an error uploading… Upload Errors:
importtest.csv: Sorry, this file type is not permitted for security reasons.This reply has been marked as private.Thank you.
Since I’m starting over on custom fields anyway, can you let me know is there any reason to bother creating a custom post type if I’m only planning on having one type of post (camps)? I could just add my custom fields to Places and even rename Places to Camps, right?
Kendra
I see the listing under Places that you added. But for my custom post type it’s still all disappearing for me as soon as I publish it. I’m adding a custom post listing, for the custom post type Camps2019. Can you try adding or editing a listing for one of those?
This reply has been marked as private.Just wanted to let you know I got it to work – it seems it was all related to trying to use an IP address instead of the domain name. Once I got the domain pointing at the IP address and changed the WP settings to the domain name, it all started working. Thanks for your advice. I’m super excited about getting my site up now!
Thank you both. I think it was related to the “coming soon” page, as now that my domain name is finally pointing to my IP address I’m getting different errors.
I can’t add a new place within the dashboard b/c of the Oops error, but when I go to my website, I get a map for Places, and I get a “no records found” for my custom post type listings. So … I think Paolo is probably right about an error with the API restriction settings. I’ll play around a bit more and see what I can figure out, but if this explanation makes it obvious to you what the problem is, let me know!
