So, if all fields of the CSV file are properly formatted and included, then based on the previous post of the fields associated with the export of the database, there will be an issue.
In
post #3 at least one of the language dependent fields ends with _1 (a number) which is the language_id of 1. As can be seen above in the quote, the language_id of 1 is English: 1-en: English. But... The Import Language Override is set to be language_code_only (yes default setting at the moment), which for English would be _en, but because the import is only for language_code, then none of that language dependent information will be captured for processing... This was something mentioned multiple times over the last several pages of the easypopulate 4 forum thread. Quite literally, changing that configuration setting from language_code_only to ABSOLUTELY anything else at least will allow the software to process a language dependent field that ends with a number (language_id).
The other thing as discussed earlier, that the user Defined Products Fields: Condition says false, that means that the database table products does not contain the field: Condition, it may contain "condition" or perhaps the field is called something else but a language define is calling it "Condition".
There's a number of ways to obtain/get the list of fields that are in the products table; however, I have not incorporated any of them into EP4. With as much as EP4 is able to do with any of the provided data, I have always been concerned about what information might be made tooooo easily accessible. Sure I'm certain it is overthought, but I'd rather make it as easy to do what is needed/desired by someone that has or is able to obtain the information they need than to make it easy for anyone that happens to gain access...
Bookmarks