EasyPopulate 4.0 Support Thread

[mc12345678]

Zen Cart v1.5.4 (PHP Version: 5.6.17 - MySQL 5.6.29)
Localization -> Languages: Italian/English

Easy Populate 4.0.33a - Beta 02-29-2016
Model/Price/Qty (with Specials)

I export two "v_products_model" and two "v_products_name"
I correct the stocks ("v_products_quantity" and "v_status"

I import the file and i see: "An SQL error has occured. Please check your input data for tabs within fields and delete these. If this error continues, please forward your error log to the Easy Populate maintainer"

Debug Log: "MySQLi error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE products_id = *** AND language_id = 3' at line 1
When executing: UPDATE products_description SET WHERE products_id = *** AND language_id = 3"

*** They are different ID

Why ? Any suggestions ?

Regards

Request a little clarification and some additional information.

1) two v_products_model, does this mean two products that have a v_products_model or are there two fields along the top of the export file that have v_products_model as a field?
2) I understand two v_products_name to mean v_products_name_1 and v_products_name_2 are/might be fields though the second number could be other than 2. Please verify this is to what you were referring.

3) When exporting the product, what is/was the admin setting for the primary key, is it products_model, products_id or blank_new?
4) Same question for when importing.
5) What field(s) are in the user defined entry under admin/configuration/ep4?
6) The exported product, were there two or more rows that contained the same data in the v_products_model field? (Ie. either linked product or the same model applied to two different product?)
7) What fields are along the top of the export file?
8) What fields are along the top of the import file?

[Nightfly66]

Request a little clarification and some additional information.

1) two v_products_model, does this mean two products that have a v_products_model or are there two fields along the top of the export file that have v_products_model as a field?
2) I understand two v_products_name to mean v_products_name_1 and v_products_name_2 are/might be fields though the second number could be other than 2. Please verify this is to what you were referring.

3) When exporting the product, what is/was the admin setting for the primary key, is it products_model, products_id or blank_new?
4) Same question for when importing.
5) What field(s) are in the user defined entry under admin/configuration/ep4?
6) The exported product, were there two or more rows that contained the same data in the v_products_model field? (Ie. either linked product or the same model applied to two different product?)
7) What fields are along the top of the export file?
8) What fields are along the top of the import file?

I will try to explain better with some examples:

1) Each product has a unique code (v_products_model) but each product has a unique code but this code is duplicated for the product name in English and the name of the product in Italian language (v_products_model)
2) I have twice the same product code associated with the same product model one by the name in Italian is the second with the name in English
3/4) I do not have blank fields
5) With earlier versions, I have never had need to enter anything in the User Defined Fields Products
6) There may be some products linked in different categories
7/8) v_products_model, v_products_name, v_status, v_specials_price, v_specials_price, v_specials_date_avail, v_specials_expires_date, v_products_price, v_products_quantity.

All fields are duplicates with the same values. The problem seems to be "v_products_nam"e which is in two languages

Sorry for my English. I hope I was clear in explaining

Regards

[mc12345678]

I will try to explain better with some examples:

1) Each product has a unique code (v_products_model) but each product has a unique code but this code is duplicated for the product name in English and the name of the product in Italian language (v_products_model)
2) I have twice the same product code associated with the same product model one by the name in Italian is the second with the name in English
3/4) I do not have blank fields
5) With earlier versions, I have never had need to enter anything in the User Defined Fields Products
6) There may be some products linked in different categories
7/8) v_products_model, v_products_name, v_status, v_specials_price, v_specials_price, v_specials_date_avail, v_specials_expires_date, v_products_price, v_products_quantity.

All fields are duplicates with the same values. The problem seems to be "v_products_nam"e which is in two languages

Sorry for my English. I hope I was clear in explaining

Regards

No, your English is fine, I was however able to consider multiple ways that the information could be understood. I did not want to try to guess too much. :)

I have taken a look at the code and I have tested the changes. I have uploaded some more changes to 4.0.34 to https://github.com/mc12345678/EasyPopulate-4.0

[Nightfly66]

No, your English is fine, I was however able to consider multiple ways that the information could be understood. I did not want to try to guess too much. :)

I have taken a look at the code and I have tested the changes. I have uploaded some more changes to 4.0.34 to https://github.com/mc12345678/EasyPopulate-4.0

You are very kind: I'll try this new version

[Nightfly66]

No, your English is fine, I was however able to consider multiple ways that the information could be understood. I did not want to try to guess too much. :)

I have taken a look at the code and I have tested the changes. I have uploaded some more changes to 4.0.34 to https://github.com/mc12345678/EasyPopulate-4.0

I always see duplicate "v products_model"
Let me know if I can privately send the exported file

[mc12345678]

I always see duplicate "v products_model"
Let me know if I can privately send the exported file

I noticed this as well when I exported using both an older version and the latest... With one language and two.

The temporary solution (workaround) would be to edit the last record in the grouping of the v_product_model (ie. Sorted by v_product_model) and upload that file or take action to reduce the number of rows of a v_product_model to one.

Before making a change to the code to reduce that result to one entry per product_model, need to understand how that "feature" is used/could be of benefit to someone. Result may be that need to add another admin->configuration control in order to allow/prevent that duplication. I don't like taking away a "feature" that exists if there is a benefit to it's presence.

[Nightfly66]

No, your English is fine, I was however able to consider multiple ways that the information could be understood. I did not want to try to guess too much. :)

I have taken a look at the code and I have tested the changes. I have uploaded some more changes to 4.0.34 to https://github.com/mc12345678/EasyPopulate-4.0

Question: can I go back to an old version v4.0?
The one I was working or they might be problems with the SQL DB?

[mc12345678]

Question: can I go back to an old version v4.0?
The one I was working or they might be problems with the SQL DB?

Yes you can, the suggestion would be to first use the remove/uninstall feature in the right corner of the tools->EP4 window, then to remove the current EP4 files, load the replacement (old) EP4 files and install as normal.

There may be "compatibility" issues in that the older code may not work on the current system. May I ask why this is desired?

[Nightfly66]

Yes you can, the suggestion would be to first use the remove/uninstall feature in the right corner of the tools->EP4 window, then to remove the current EP4 files, load the replacement (old) EP4 files and install as normal.

There may be "compatibility" issues in that the older code may not work on the current system. May I ask why this is desired?

I wish that the software is functioning as previous versions. I would like that you to confirm to me that I have no problems in importing especially prices and inventories, and that these errors do not harm my database.

[mc12345678]

I wish that the software is functioning as previous versions. I would like that you to confirm to me that I have no problems in importing especially prices and inventories, and that these errors do not harm my database.

As recommended in the instructions, this code like any other including an upgrade to ZC ought to be tested for the desired condition(s) actions independent of a live server (or at least with a backup made immediately before pushing data). The countless variations possible prohibit 100% testing of every possible condition. As can be seen, issues identified are rapidly addressed.