EasyPopulate 4.0 Support Thread

[salvo72]

hi

i want upload a description data with easy populate

i can use i file whit simple file csv with fileds: v_products_model and v_products_description_2 ???


i have a error and dont possible atachement csv file!!! where is the error log of easy populATE4 ??

THANKS

[mc12345678]

hi

i want upload a description data with easy populate

i can use i file whit simple file csv with fileds: v_products_model and v_products_description_2 ???


i have a error and dont possible atachement csv file!!! where is the error log of easy populATE4 ??

THANKS

Errors captured/documented by EP4 are in an errorlog listed in the files to be imported/downloaded. New errors are added to the end of the file. If this file has been in the file list for a long time it may contain multiple errors that do not relate to the current issue.

Btw, I am not entirely sure that the code currently supports only a total of two columns being in the upload file. I would have to look to see what changes might be necessary to support that.

[izzysoup]

Hi, I have installed EP4 on a 1.5.3 zencart site. I have noticed I get the following when using this add-on

"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"

When I check my logs folder, the error is as follows.
"[29-Nov-2014 16:01:47 Europe/London] PHP Warning: mysqli_fetch_array() expects parameter 1 to be mysqli_result, boolean given in /home/izzy/public_html/ZC153-test5/renamedaddy/easypopulate_4_import.php on line 881"

I don't know what I have done wrong
I do not get this error on a 1.5.1 site.

All help appreciated!

[mc12345678]

Hi, I have installed EP4 on a 1.5.3 zencart site. I have noticed I get the following when using this add-on

"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"

When I check my logs folder, the error is as follows.
"[29-Nov-2014 16:01:47 Europe/London] PHP Warning: mysqli_fetch_array() expects parameter 1 to be mysqli_result, boolean given in /home/izzy/public_html/ZC153-test5/renamedaddy/easypopulate_4_import.php on line 881"

I don't know what I have done wrong
I do not get this error on a 1.5.1 site.

All help appreciated!

Which ver of EP4 was installed on ZC 1.53 and what plugins are also installed on the ZC site?

[salvo72]

how modified the file php for this...

you can give me a support or customize the file?

[salvo72]

Errors captured/documented by EP4 are in an errorlog listed in the files to be imported/downloaded. New errors are added to the end of the file. If this file has been in the file list for a long time it may contain multiple errors that do not relate to the current issue.

Btw, I am not entirely sure that the code currently supports only a total of two columns being in the upload file. I would have to look to see what changes might be necessary to support that.

how modified the file for this

how delete the control

you can give me a support or customize?

[mc12345678]

how modified the file for this

how delete the control

you can give me a support or customize?

Definitely the easypopulate4_import.php file in the admin directory would need revision. The extra_functions file may need some revision as well as possibly the main admin file... There are a few fields that were considered to be always present and were to be loaded at the start of processing. (The description field was one of them, but thtgot modified to preload, but ignore if not present in the data.) There were a few others that made sense and were a good practice to keep in the upload file because they made the line understandable to someone reviewing the file in the future. I think product name was one of them. Can that be coded out? Yes, but to include as an always situation leading to muliple users of the software being confused about the data that is maintained in the file, well that may cause more confusion for the masses instead of the few that would like to only upload two columns...

That may be more of a "one" site item to address instead of something to distribute for all. The description field was made not required because of the problems that were experienced by trying to upload very large amounts of information that wasn't changing each time. That was seen as a problem, not as an inconvenience. I would think that a strong case of removing the few required fields that are currently identified wouuld be appropriate to make that change.

Afterall, it seems that the data was there before, otherwise what was the process used to identify the rows that needed to be revised with the new data?

[salvo72]

Definitely the easypopulate4_import.php file in the admin directory would need revision. The extra_functions file may need some revision as well as possibly the main admin file... There are a few fields that were considered to be always present and were to be loaded at the start of processing. (The description field was one of them, but thtgot modified to preload, but ignore if not present in the data.) There were a few others that made sense and were a good practice to keep in the upload file because they made the line understandable to someone reviewing the file in the future. I think product name was one of them. Can that be coded out? Yes, but to include as an always situation leading to muliple users of the software being confused about the data that is maintained in the file, well that may cause more confusion for the masses instead of the few that would like to only upload two columns...

That may be more of a "one" site item to address instead of something to distribute for all. The description field was made not required because of the problems that were experienced by trying to upload very large amounts of information that wasn't changing each time. That was seen as a problem, not as an inconvenience. I would think that a strong case of removing the few required fields that are currently identified wouuld be appropriate to make that change.

Afterall, it seems that the data was there before, otherwise what was the process used to identify the rows that needed to be revised with the new data?

yes
the data you have loaded a year ago

you can change the fiel import and delete the control that requires me to have more fields validated?

we need to import files for certain products of which we have the description

if you give me your email and if I can give you support sending the file to upload

thanks

[Kevin205]

For some reason the Model/Price/Qty does not import data, quantity or price!

I exported the PriceQty-EP2014Dec10-103644.csv, modified and imported it via PriceQty-EP2014Dec10-103644-TEST.csv. As you can see it did not update anything.
Where can I start to find out what is causing this?

Import Results

Filename: PriceQty-EP2014Dec10-103644-TEST.csv
Finished Processing Import File

Updated records: 0
New Imported records: 0
Errors Detected: 0
Warnings Detected: 0
Memory Usage: 6688720
Memory Peak: 6938216
Execution Time: 0.00019407272338867 seconds.

ps. I am using Easy Populate 4.0.22 - Beta 6-10-2012 version.

[mc12345678]

For some reason the Model/Price/Qty does not import data, quantity or price!

I exported the PriceQty-EP2014Dec10-103644.csv, modified and imported it via PriceQty-EP2014Dec10-103644-TEST.csv. As you can see it did not update anything.
Where can I start to find out what is causing this?



ps. I am using Easy Populate 4.0.22 - Beta 6-10-2012 version.

My suggestion would be to review the csv file that is being provided to EP4/ZC using a plain text editor. Extra spaces before/after a column header, extra row from the top, etc... These types of things can cause the code to bail out. The code does not specifically look for that filename (yes was looking at the version described), but does have some fields that are expected as well. So could maybe provide a line or two from your file captured between code tags that are made by clicking the # symbol in the posting toolbar.