Importing CSV fails and I can’t see the actual error

[thesearchjuggler]

Hi,

I’m importing a CSV file into MapPress Pro with 190 locations, but the import process itself seems to fail inconsistently – sometimes I’ll get 160 locations in the resulting map, sometimes 188, whatever. When the import has finished I briefly see something flash up on the Import page (possibly an error report?), but this then returns to the default and I get a dialog box that says “The response is not a valid JSON response.”. Sadly since I’m on a managed instance of WordPress via my ISP, I can’t see the WordPress error logs.

Any ideas? I’m happy to share the CSV file privately if that helps.

Cheers

Charlie

[Chris]

Hi,

I tried to replicate this a few times with the sample CSV file, but I didn’t get an error. Are you able to import the sample without errors?

Two other things to try:
1. There are some plugins that will display the WP logs, even if you don’t have FTP access, so it might be worth checking those out.
2. Deactivate ALL other plugins and switch to a standard theme (like twenty twenty-five). If the import works, you can reactivate one by one to find the error.

If you can share an administrator login to a staging site where I can see the problem then I can debug it there.

If you’d like to send the file, you can reach me with the contact form and I’ll reply. But from what you describe it sounds like the issue may be specific to your site.

[thesearchjuggler]

Just for reference, Chris let me know why this was happening:

“I found the error: the input file has a column ‘lon’, but it should be ‘lng’.

Because of this difference, MapPress doesn’t realize there’s already a lat/lng, and tries to geocode each POI with Nominatim. Nominatim is very slow, so this eventually exceeds the PHP maximum runtime (max_execution_time in php.ini defaults to 120 seconds). PHP then throws an error, and you see the “Invalid JSON” message from MapPress.”

He is fixing it in the next release (making ‘lon’ a synonym for ‘lng’) but for now I have renamed the column and the import works perfectly.

Charlie

[Author]

Posts