Quote Originally Posted by mc12345678 View Post
Did you happen to scroll down the screen after performing an import?

To what file(s) are you referring when stating "noting file to look at"? At the completion of each import, there is some level of information provided. If an "insert" fails, that basically is a problem with the data that has been provided which for the most part likely can not be identified as "successful" or flagged for failure... Meaning, one may have to identify what has been successful to identify what didn't work.

As far some of the processes, it is possible that a message is not provided for one or another issues, for example I know that on a product import where products_model is the primary key, if the products_model field for a row is blank, there is no notification about any issue... Is it a problem? I say no, but that's because an empty products_model in that situation is expected and supposed to be skipped... I state some of that to try to further identify the expectational differences between early and experienced users.
Thanks for your work on this. I realize this is not a paid job and these are just my suggestions for whosoever may want to update this module to make it more excellent.

Hello, yes I did scroll down the screen but this should really be spit out into a file with success and fail notices for each product.

"noting file to look at" if there was a file that contained those errors (it does not currently exists).

Hmmm... you cannot test to see if a sql insert was successful or not? Sorry, so easy to do with languages I have worked with just thought it would be easy in php also.

Thank you for having this working for us currently!