Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
06/14/2016 at 9:16 am #379426
first, let me thank you for your quick help on the last issue.
After the test import, 41 of 50 contacts show up, I attached the test file. Also, utf8 option is set up.
What can I improve to fix it?
Attachments:You must be logged in to view attached files.06/14/2016 at 10:36 am #379438
I took a look at the CSV file, it does appear the file encoding was corrupt. It was not reading as UTF8 for me. I’ve corrected this and attached it. I recommend removing the last row about the “row height”. That should not effect anything, but its good to make sure the CSV file is clean.
Let me know if that helps.
Attachments:You must be logged in to view attached files.06/14/2016 at 11:36 am #379440
Thank you, it works!
Now, since I have to import the whole database, can you suggest me some useful tools/links for converting to utf8 properly? Obviously, those links/pages/tips I read are not quite precise. I would like to avoid the same mistake.
Thank you so much.06/14/2016 at 12:23 pm #379441
I guess my first question would be… what is the source of your CSV file? Excel? Something else?
The specific tool I used to fix your file was Sublime Text 2 with the EncodingHelper package. I simply opened the file the status bar had a notice about the broken encoding so I and da a “Save file with Encoding”, choosing UTF8.
I did open the file in LibreOffice Calc before fixing the file, and there were a dozen or so characters shown as question marks (?). So, if you open the file in LibreOffice Calc and fix those question marks and then save the file out as a CSV file with UTF8 encoding your import should go without a hitch.
Now, all that said, it only take me a second to open/save a file, so if you send me your whole file, I’ll fix the encoding for you.06/14/2016 at 3:27 pm #379452This reply has been marked as private.06/14/2016 at 3:48 pm #379477
I opens the CSV files, looked good. I did not get the file encoding error notice when opening and it was UTF8 encoded so it should import fine for the most part. After a quick glance at the data there seems to be the following issues:
- completely blanks rows -> they should be removed
- there are rows with no first and last name, those will be imported as “Organizations”. Not an issue, just wanted to point it out.
- I saw one row with a first name, no last name, but had and Organization name. This will either be “tossed” on import or imported as an Organization. I can not remember precisely of the top of my head.
- I saw one row with only a first name, no last name or organization name. This one will not be imported.
There could be other issues but that’s all I saw after a couple minutes.06/14/2016 at 4:48 pm #379486This reply has been marked as private.06/15/2016 at 8:05 am #379572
Looking at the
Database1.csvfile from your last reply, there are now at least two major issues that was not present before…
Part of each row is separated by commas and part of the row is separated by semicolons. Another serious issue that was not present bore is that the string (for example the Notes) are now double quoted; having two
""quotes instead of one
"quote. BAsically the file is severely corrupt is is not able to be imported.
There could be other issues, but I am unable to open the file in anything that can read CSV files properly. I can only open it in my text editor which is how I saw these issues.
I suggest going back to the
You cannot reply to this support topic. Please open your own support topic.