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.
01/12/2019 at 10:54 pm #481551CarlGuest
The CSV file that I am using is just a modified copy of the example headers excel file that I downloaded from the import page. I only filled in 6 rows just to test it.01/14/2019 at 9:10 am #481618
Unexpected token < in JSONseems to indicate that something is causing a PHP error and PHP is displaying the error in the import response which breaks the process.
While in the Console tab in Chrome, after that error occurs, you can click the Network tab. near the end of the list you’ll very likely find a red line item. Clicking that line and then clicking the Preview or Responce tab will display what the server actually sent as a response. Knowing that will help to know what the source of the error is.
If this is the cause of the import failure, disabling the display of PHP notices may help with this. This is generally considered to be a best practice on live sites. Here’s a link to a tutorial which will help with that.
You can also try doing the import with all other plugins temporarily deactivated to eliminate them as the source.
Also, make sure you closely follow the CSV file requirements and tips. Using the header example Excel sheet is not enough.
Lastly, I can take a closer look if you want. Please create a temp admin account using this plugin:
Reply back, as a private reply, with the login link. Also, please attach a copy of your trest CSV file. And, attach a screenshot of the mapping you are using to apply to the import.01/17/2019 at 9:31 pm #482031CarlGuestThis reply has been marked as private.01/18/2019 at 9:49 am #482082
An even slightly older CSV Import plugin was required for the version of Connections installed on the site. I was able to import your test CSV file without issue after installing it.
You probably should delete those multiple new version of Connections that are installed but deactivated so you do not run into conflicts.
Lastly, all empty columns in the CSV, you should remove those when you do your CSV import. Even though the columns are empty, they still have to be parse and processed. Since there are empty that causes a lot of unnecessary overhead.
Hope this helps!01/21/2019 at 9:51 pm #482303CarlGuest
Awesome! It’s working. Thank you for your help!01/22/2019 at 9:06 am #482340
No problem, glad to help!
You cannot reply to this support topic. Please open your own support topic.