Quote Originally Posted by Pingfah View Post
I am unable to edit the post now, but I should add that if I switch to Product ID as the primary key, all these problems go away.

All CSV files have been created in Open Office with recommended settings.
Well, a couple of things.

First, apologies that 4.0.36 did not include some of the "error" checking that would likely have helped identify that using the products_id as a primary key may have been necessary (as compared to desired?).

There have been newer versions generated to address/correct the lack of the primary key value/data being present along with some other notifications so that do not have a false positive of success.

One thing that I didn't ask for was, what field headers were present in the file having an issue as compared to one that didn't. Then another was if the new file had unescaped special characters that possibly could have affected the import evaluation.

That it seems that no changes what-so-ever were made in the underlying code or the import file (meaning same ZC version, same EP4 version, same previous import file) seems to mean that either MySQL version and/or PHP version changed to a value affecting the code operation. Suggestion might be to compare two CSV files, the working and not working one(s) to see what other differences might exist causing the issue of basically the product table data getting imported to the correct area(s), but the products description table seems to only take the description (and therefore things like products_name) only were imported basically against the last product. To me, that aligns more with the issue of missing data associated with the chosen primary key or that all those affected have the same primary_key value.

Glad though that it seems a fix was found. As far as a log, generally, if EP4 logging is turned on, then a log that might get generated assuming a loggable event occurred would be in the debug log in the EP4 import/export file directory or added to it if it already existed.