Import error message
This topic contains 8 replies, has 3 voices, and was last updated by J C 7 years, 6 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: import csv error
-
AuthorPosts
-
September 22, 2017 at 1:15 pm #396921
I’m unable to import listings and continually get the following error message:
6 / 6 item(s) could not be added due to blank/invalid address(city, region, country, latitude, longitude).
I’ve looked through every possible help topic here in the forum and have done my very best to follow the import/export instructions (here https://wpgeodirectory.com/docs/core-export/) and the CSV tips and tricks (here https://wpgeodirectory.com/docs/csv-tips-and-tricks/), but no matter what we try, it doesn’t work.
We’ve spent hours and hours on this and are utterly baffled; would you please help out and let us know how to get this working? I’ve attached the CSV file here for you to look over, if that helps.
September 22, 2017 at 9:31 pm #397011Hi J C,
there are few illegal characters in that file. please see image attached.
Make sure to correct them. (best way to do that is using HTML codes)
Let us know how that goes,
Thanks
September 23, 2017 at 5:52 pm #397102Ah, interesting – it’s the French accents (such as é and à) that can’t be imported. When I removed them and replaced them with regular letters (e and a) on a test with just 3 listings, the import worked just fine.
But I can’t see how I can remove the accents on many listings – that would make a lot of manual labor to add them back in, one by one, once the listings have been imported.
I did try the HTML codes you suggested (such as making Québec become Québec), but that didn’t work. (The listings wouldn’t import.)
What other suggestions could I try to get those accents importing properly?
September 23, 2017 at 5:57 pm #397103What are you using now as file encoding? Did you try to change it maybe to UTF8? Please see: https://csvimproved.com/support/questions-and-answers/916-save-a-csv-file-as-utf-8
let us know,
Thx
September 24, 2017 at 12:13 pm #397153Yes, the file encoding was UTF 8, and it won’t import anything that includes an accent. Any other ideas on how to get this to work?
September 25, 2017 at 9:30 am #397208Hi JC,
I successfully imported listings from CSV that you attached.
I have first converted file encoding to UTF-8 and it worked for me.
I have done following steps:
1) Opened CSV file and chosen encoding “Western Europe(ISO-8859-1)” because it shows correct characters (see 20170925-396921-1.png)
2) Copied all data
3) Open new CSV file with encoding UTF-8
4) Paste all data into new CSV
5) Save (in case if it asks encoding choose UTF-8 during save)Now it shows correct characters with UTF-8 encoding.(see 20170925-396921-2.png)
I have attached modified file, it worked for me.Let us know.
Thanks,
KiranSeptember 25, 2017 at 5:13 pm #397269I finally managed to import some categories, so yay! Thank you for that! But now there are other issues.
I’m using WPML for translation, which lets me switch between English and French to translate categories. (See screenshot Capture)
On the new categories I imported, as a new CPT called gd_restaurants, no translation feature is available. (See screenshot Capture2)
How do I ‘activate’ this so that the categories can be properly translated?
I tried adding a new category manually, in French. It automatically created it in English also, but in the French language. Editing one edits the other. Deleting one deletes the other.
That’s not at all how things work for the gd_place categories I have, so I’m baffled. Help?
September 26, 2017 at 4:28 am #397324Hi There,
I seems you have not enabled WPML translation for place categories.
Make sure you have enabled WPML translation for Places & Place Taxonomies at WPML > Translate Management > Multilingual Content Setup > Custom posts > Places & WPML > Translate Management > Multilingual Content Setup > Custom taxonomies > Place Categories (gd_placecategory).Let us provide admin credentials if still have a problem.
Kiran
September 26, 2017 at 10:33 am #397374Ah! Perfect!! Thank you so much for all your help with this. Hopefully it should be smooth sailing from now on!
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket