Fatal Error

I have the same issue, must be a 3.8 problem, i’ve contacted support but I think that are on holidays still ??

Any updates on this? I’m getting weird behavior with 3.8 and wp all import too.

We’re not still on holidays. Is this happening in the free version here, or the paid version available on our website?

WP All Import is fully compatible with 3.8. I suspect it might be a problem with your database… but I’m not sure.

If you’ve submitted a ticket to [email protected] and didn’t get a ticket ID back, it means we didn’t receive the ticket.

If you haven’t submitted a ticket about this, even if you’re a free version user, go ahead and submit a ticket to [email protected], and we’ll investigate it.

Louis

Soflyy,

I’m with karlbecker (above). We are on the paid version running against 3.8. I opened a ticket (#36254) about 4 days ago. Still waiting to hear back on any progress.

Joe

Just an update on this:
we determined that there was an error with our PHP code, but then we also identified that the latest version of WP All Import has some different options in Settings for some of our data. Check out the “My CSV files contain HTML code” option in case it looks like certain data is not being imported – we got stuck on data that had an ampersand “&” in the data. This was a distinct behavior change from previous versions of WP All Import!

Cheers,
Karl

Hi karlbecker and Joe,

I am sorry for late response.

We were testing our current and new releases trying to find all possible problems with WP 3.8. And looks like it works fine for us. So, any tips where we have problems with compatibility are much appreciated.

Regarding My CSV contains HTML code, after 3.3 we have implemented new strict validator to prevent all possible file with wrong formats.

Possible issue that can cause problems:

symbols like & and umlauts presented in your files – to solve you need to replace them using html symbols; https://www.ascii.cl/htmlcodes.htm – as an example;

wrong encoding – file should be presented in UTF-8 without BOM;

unneeded ” symbols inside lines and other not valid situation.

I have requested in ticket your file that you are facing troubles with. So, we will take a look, once you send it, and provide you an answer.

Regards,
Artyom

Artyom,
Thanks for the feedback.
The change in 3.3 was very unexpected and seems like it would cause major gnashing of teeth, since I would assume the “&” character is extremely common in many datasets.

The term that got hung up was
“My Dog & Cat”
This does not have HTML code, yet to get it to process, I had to check that my file contains HTML code… this seems like a sketchy choice.

Does it say anywhere that UTF-8 is required for importing? I noticed that the files I saw were encoded in Mac Western, though I will need to look again to see if that works when uploading it.

Karl,

>>Does it say anywhere that UTF-8 is required for importing?

Not sure. Probably, it is our omission. We will add this notification in next release.

Anyway, files should be in UTF-8 without BOM. Once you will encode it, you can see if it has something strange inside file what can cause an error during import. I mean, all “bad” symbols will strike the eye immediately.

Sorry, if my description is not clear enough.

>> The term that got hung up was
“My Dog & Cat”
This does not have HTML code, yet to get it to process, I had to check that my file contains HTML code… this seems like a sketchy choice.

Good point. This is a bug. We’ll fix it. Thanks for the report.

To clarify, files are not required to be UTF-8 – as long as you select the correct character set when importing if they aren’t UTF-8.

However – this problem isn’t related to that.

Louis