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.
Premium Support
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.
Free Support
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.
Tagged: 8.5.32, csv import, extension
- This topic has 8 replies, 2 voices, and was last updated 6 years, 3 months ago by
Steven Zahm.
-
AuthorPosts
-
02/27/2017 at 1:43 pm #413072
David Hahn
ParticipantI’m using the latest Import CSV extension, v1.4.3, and I can’t get it to import more than 100 records (I have 596 in my CSV file.)
I have tried on both my localhost and on the dev server at our host; I have tried mapping all the fields and also tried mapping only the First/Middle/Last name fields; I have tried deleting the first 200 lines in the CSV file, just in case there was a “bad” entry it was hitting; and no matter what, it will only import 100 records.
It just sits on the “Please wait” blue progress bar — I have waited up to an hour on my localhost — and whenever I check the wp_connections table via phpMyAdmin, it only shows 100 records imported. So those first 100 get imported almost immediately, and it never progresses further.
The csv file looks fine, is in UTF8 format, doesn’t seem to be a “bad record” it is hitting.
Any ideas?
02/27/2017 at 1:45 pm #413073David Hahn
ParticipantThis reply has been marked as private.02/27/2017 at 2:14 pm #413082Steven Zahm
Keymaster@ David
It sounds like another plugin or possible the theme is not limiting their javascripts to their own admin pages and causing a fatal javascript error preventing the importing javascript from running. The first 100 are triggered via the Import button then javascript is used to batch import 100 at a time via javascript requests. If there are fatal javascript errors, this will prevent the batch import requests from happening.
To see if this is the issue, navigate to the Connections : Import CSV admin page and hit the F12 key. Now click the Console tab.
Import the file following the normal steps.
On the last step, with the progress bar, take note of any javascript errors being displayed? What are they? Often the error message will give clues as to the source of the error.
Hope this helps, let me know.
02/27/2017 at 2:27 pm #413086David Hahn
ParticipantOkay, here is what I got.
After hitting the “Map” button, the following shows up on console:
load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9 JQMIGRATE: Migrate is installed, version 1.4.1
admin.php?page=connections_csv&action=map:439 GET http://localhost/?ai1ec_render_js=common_backend&is_backend=true&ver=2.5.16 net::ERR_CONTENT_DECODING_FAILEDAnd then after clicking “Import” the console shows:
load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9 JQMIGRATE: Migrate is installed, version 1.4.1
admin.php?page=connections_csv&action=import:462 GET http://localhost/?ai1ec_render_js=common_backend&is_backend=true&ver=2.5.16 net::ERR_CONTENT_DECODING_FAILED
VM626:2 Uncaught SyntaxError: Unexpected token ? in JSON at position 1
at JSON.parse (<anonymous>)
at Function.n.parseJSON (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
at Function.a.parseJSON (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9)
at Object.<anonymous> (admin.php?page=connections_csv&action=import:413)
at i (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2)
at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2)
at y (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
at XMLHttpRequest.c (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
n.parseJSON @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4
a.parseJSON @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9
(anonymous) @ admin.php?page=connections_csv&action=import:413
i @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2
fireWith @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2
y @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4
c @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4The “ai1ec” referenced there is the All In One Events Calendar plugin, I’ll try disabling that and see if that makes a difference.
02/27/2017 at 2:33 pm #413087David Hahn
ParticipantDisabling the calendar plugin got rid of the ai1ec-related javascript errors, so no errors on the Map page, but still only imported the first 100 records and has these errors after clicking the “Import” button:
load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9 JQMIGRATE: Migrate is installed, version 1.4.1
VM2113:2 Uncaught SyntaxError: Unexpected token ? in JSON at position 1
at JSON.parse (<anonymous>)
at Function.n.parseJSON (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
at Function.a.parseJSON (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9)
at Object.<anonymous> (admin.php?page=connections_csv&action=import:387)
at i (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2)
at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2)
at y (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
at XMLHttpRequest.c (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4)
n.parseJSON @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4
a.parseJSON @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:9
(anonymous) @ admin.php?page=connections_csv&action=import:387
i @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2
fireWith @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:2
y @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:4
c @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.7.2:402/27/2017 at 3:03 pm #413091Steven Zahm
Keymaster@ David
The
Uncaught SyntaxError: Unexpected token ? in JSON at position 1
is likely the cause.It is hard to decipher the messages copy/pasted, but, this error looks like the response expected back from a batch import request was not what was expected. This indicates a server error response. You would find these under the Network tab in the Control panel. It would be near the bottom of the list on a line beginning with
admin-ajax.php
(you have to have the Control panel open during the import for the network request log to record requests and responses.If you can give me a temp WP admin login and attach a copy of your CSV file with a screenshot of the mapping you are using. I can do an import so I can see the responses. The login details can be posted here as a private reply.
02/27/2017 at 3:41 pm #413113David Hahn
ParticipantAh, thanks, that tip to look at the Network tab and into the admin-ajax.php revealed what seems to be an error in our functions.php file in our child theme. I saw a “?>” at the beginning of the request; temporarily removed our functions.php file completely; and the import worked correctly, with multiple admin-ajax.php firings.
So we’ll look through our functions.php file to see if we can find the error, most likely a typo somewhere.
Will let you know how it turns out.
02/27/2017 at 3:48 pm #413114David Hahn
ParticipantFound the typo in the child theme’s functions.php file, and that was indeed causing the problem, the import works correctly now.
So not a problem with Connections at all.
Thanks for your help!
02/27/2017 at 5:55 pm #413137Steven Zahm
Keymaster@ David
Great to hear you found the cause. That typo would have causes you all sorts of trouble so it’s good to find it sooner vs later.
-
AuthorPosts
You cannot reply to this support topic. Please open your own support topic.