Ok, I *tried* to ask for information about the settings that are involved with this, I missed one setting.... Although I did not ask for one setting, I received information that is/was helpful.
The settings I was *really* interested in were:
1. Import/Export Primary Key
2. Import Language Override
3. Export Language Identifier
The default settings for these in 4.0.37.13 were:
1. products_model
2. language_code_only
3. id
The problem with some of those defaults (as discussed several times before) is that when importing data that is language dependent, trying to import only fields with the language_code means that the field likely does not exist. Because the specific field does not exist then the data does not exist for the program. Why would the field not exist? Because when exporting the data, the language dependent field(s) only ended with the language_id.
So, to more accurately state the necessary conditions:
If 3. (Export Language Identifier) is id when exporting the file, then 2. (Import Language Override) should *NOT* be language_code_only.
If 3. (Export Language Identifier) is code when exporting the file, then 2. (Import Language Override) should *NOT* be language_id_only.
The above is for the problem described. The problem described has been, when importing a product file created by export, the system response is "No category provided for this new product". Why? because, if the code is looking for categories_name_en, but it only contains categories_name_1, then it is true that the category is considered to be missing.
So, in summary, may I suggest changing the setting for Import Language Override to ANYTHING other than language_code_only. Generally speaking, I would suggest changing it to language_id_only to keep things "simple". :)
Bookmarks