EasyPopulate 4.0 Support Thread

fcutler4:

Thank you again mc12345678 and wmorris.
It appears you were correct in surmising that the EASYPOPULATE_4_CONFIG_TEMP_DIR is missing.
See the screenshots that I took after using the "un-install EP4" button:


I'll do as you suggest, add the file, and redo the un-install and re-install.
Where should the file be inserted, just to make sure I put it in the correct place?
Thanks again. I'm looking forward to using this great add-on once again. It's such an awesome tool!

The files from the download are arranged to go to the correct location if copied as a group from the source to your store. All files and folders in the admin directory of the download are to go into the admin directory of your site. Copying them over in that way (instead of one file at a time) minimizes the potential of misplacement or other issues.

That said, the above screen shot is expected if have only done the uninstall (as what was described above). There should be a link available to install (seen in second image) which should also change what is/was seen in the image (if the files are up-to-date).

OK, here's what I've done, but I'm still getting the same error.

1. Hit Un-Install EP4 button
2. Downloaded latest version of EP4 from the zen cart link. Loaded all files via Filezilla to my store directory following the correct file structure. Double checked it to ensure everything was in the correct place.
3. Refreshed the Zen Cart Easy Populate page.
4. Hit Install EP 4. The following screen shots show the EP4 configuration settings. Uploads Directory Admin/Catalog shows "true," and uploads directory is "temp/." As you recall, the Uploads Directory Admin/Catalog line was not showing up before, but now it is.
   
   
5. Uploaded a CVS File. A red warning came across the top of the screen saying, "File uploaded successfully: import today 6.3.2018.cvs. Import file to database or see below for more."
6. Hit "Import" There was a green bar across the top of the screen stating "File Import Completed."
7. In spite of all of that, however, there was an error at the bottom of the screen, so I'm still getting the same "Import file does not exist"error.
   What am I missing? If there is any other screenshot you need to help me troubleshoot, please let me know.

Here are a couple more screen shots.
[Attachment no longer available][Attachment no longer available]

Have you tried a file that doesn't have a space in the filename?

Thank you, mc12345678! Trying the import with a filename without spaces worked!

Greatly appreciate all you have done to help me through this!
Best wishes!
Frank

fcutler4:

Thank you, mc12345678! Trying the import with a filename without spaces worked!

Greatly appreciate all you have done to help me through this!
Best wishes!
Frank
Welcome. Remember if wanting to use an import "rule" other than what is done for importing "all" product, that the filename actually is part of the process...

I'm getting a MySQL error where categories are not being properly created. The products are being imported.

The error at the top says "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"
-- what's the best way to get the error file to the right person?

I've downloaded the latest version from GitHub & am running ZC 1.5.5.e.

I saw the post about the filename having spaces - my file upload doesn't have spaces.

DesignByKiltz:

I'm getting a MySQL error where categories are not being properly created. The products are being imported.

The error at the top says "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"
-- what's the best way to get the error file to the right person?

I've downloaded the latest version from GitHub & am running ZC 1.5.5.e.

I saw the post about the filename having spaces - my file upload doesn't have spaces.

PM sent, though there is some code that has been pushed to the development related github repository at: https://github.com/mc12345678/EasyPopulate-4.0/commit/57dda2b9f82da71c060d82acefc8a42551c6d37c#diff-b938ae506573022fee517c76b5163500

This should resolve the sql error that is reported.

Hi Zenners,

How can I use a Cron job to auto import a daily uploaded CSV file using easy populate 4 in Zen Cart 1.5.5f ?
Thanks in advance,

Cyd

Any suggestions would be greatly appreciated.
Running (Easy Populate 4.0.22 - Beta 6-10-2012) for 4 years now without any glitches.
The first thing you are going to say is "Upgrade" but that's no an option on this installation.
I am creating a new Upgraded site next month ZC 1.5.5f which works fine with "php 7.2 & Database Maria DB 10.2" but I really need for this current installation to work thru September.
Extensively researched this in the ZC forums and Googled. The only hint I got was maybe strict mode was being enforced.

HISTORY:
1:
Running (Easy Populate 4.0.22 - Beta 6-10-2012) for 4 years now without any glitches.
2:
Upgraded to PHP 5.6 and Database Maria DB 10.2 (I'm told same as MySQL 5.7) engines.
3:
Began experiencing a glitch including this EP4 issue.
Enabling site wide SSL fixed the other glitch.
4:
I export all products with EP4 and then never touching the csv file immediately import it
5:
Don't understand why I get the "Tabs" warning which I never got before and then the SQL error which I never got before. (see step 7)
6:
Was hoping for a work around..... Like maybe just delete that field from the code?
Is the "products_tax_class_id" mapped to the "v_tax_class_title" column?
7:
ERROR MESSAGES:
Warning File Import Completed with issues. (NOTE: Does not complete because of SQL error)
Warning 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
(You are presently using: v1.5.1) (PHP version 5.6)
++++++++++++++++++++++++++++++++++++++
MySQL error 1366: Incorrect integer value: '' for column 'products_tax_class_id' at row 1
When executing:
UPDATE products SET
products_price = '2.8',products_image = 'K3202.jpg',
products_weight = '0',
products_discount_type = '0',
products_discount_type_from = '0',
product_is_call = '0',
products_sort_order = '0',
products_quantity_order_min = '12',
products_quantity_order_units = '12',
products_priced_by_attribute = '0',
product_is_always_free_shipping = '0',
products_tax_class_id = '',
products_date_available = NULL,
products_date_added = '2016-02-03 00:00:00',
products_last_modified = CURRENT_TIMESTAMP,
products_quantity = '88822',
manufacturers_id = '0',
products_status = '1',
metatags_title_status = '0',
metatags_products_name_status = '0',
metatags_model_status = '0',
metatags_price_status = '0',
metatags_title_tagline_status = '0' WHERE (products_id = '3401')

++++++++++++++++++++++++++++++++++++
EXPORTED FILE: Full-EP2018Aug13-041014.csv
v_products_model v_products_type v_products_image v_products_name_1 v_products_description_1 v_products_url_1 v_specials_price v_specials_date_avail v_specials_expires_date
v_products_price v_products_weight v_product_is_call v_products_sort_order v_products_quantity_order_min v_products_quantity_order_units v_products_priced_by_attribute
v_product_is_always_free_shipping v_date_avail v_date_added v_products_quantity v_manufacturers_name v_categories_name_1 v_tax_class_title v_status
1100 1 01101.jpg 1101 MAGNET 2 0 0 1 12 12 0 0 1/1/2014 22:22 0 Magnets --none-- 1

linuxguy2:

Any suggestions would be greatly appreciated.
Running (Easy Populate 4.0.22 - Beta 6-10-2012) for 4 years now without any glitches.
The first thing you are going to say is "Upgrade" but that's no an option on this installation.
I am creating a new Upgraded site next month ZC 1.5.5f which works fine with "php 7.2 & Database Maria DB 10.2" but I really need for this current installation to work thru September.
Extensively researched this in the ZC forums and Googled. The only hint I got was maybe strict mode was being enforced.

HISTORY:
1:
Running (Easy Populate 4.0.22 - Beta 6-10-2012) for 4 years now without any glitches.
2:
Upgraded to PHP 5.6 and Database Maria DB 10.2 (I'm told same as MySQL 5.7) engines.
3:
Began experiencing a glitch including this EP4 issue.
Enabling site wide SSL fixed the other glitch.
4:
I export all products with EP4 and then never touching the csv file immediately import it
5:
Don't understand why I get the "Tabs" warning which I never got before and then the SQL error which I never got before. (see step 7)
6:
Was hoping for a work around..... Like maybe just delete that field from the code?
Is the "products_tax_class_id" mapped to the "v_tax_class_title" column?
7:
ERROR MESSAGES:
Warning File Import Completed with issues. (NOTE: Does not complete because of SQL error)
Warning 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
(You are presently using: v1.5.1) (PHP version 5.6)
++++++++++++++++++++++++++++++++++++++
MySQL error 1366: Incorrect integer value: '' for column 'products_tax_class_id' at row 1
When executing:
UPDATE products SET
products_price = '2.8',products_image = 'K3202.jpg',
products_weight = '0',
products_discount_type = '0',
products_discount_type_from = '0',
product_is_call = '0',
products_sort_order = '0',
products_quantity_order_min = '12',
products_quantity_order_units = '12',
products_priced_by_attribute = '0',
product_is_always_free_shipping = '0',
products_tax_class_id = '',
products_date_available = NULL,
products_date_added = '2016-02-03 00:00:00',
products_last_modified = CURRENT_TIMESTAMP,
products_quantity = '88822',
manufacturers_id = '0',
products_status = '1',
metatags_title_status = '0',
metatags_products_name_status = '0',
metatags_model_status = '0',
metatags_price_status = '0',
metatags_title_tagline_status = '0' WHERE (products_id = '3401')

++++++++++++++++++++++++++++++++++++
EXPORTED FILE: Full-EP2018Aug13-041014.csv
v_products_model v_products_type v_products_image v_products_name_1 v_products_description_1 v_products_url_1 v_specials_price v_specials_date_avail v_specials_expires_date
v_products_price v_products_weight v_product_is_call v_products_sort_order v_products_quantity_order_min v_products_quantity_order_units v_products_priced_by_attribute
v_product_is_always_free_shipping v_date_avail v_date_added v_products_quantity v_manufacturers_name v_categories_name_1 v_tax_class_title v_status
1100 1 01101.jpg 1101 MAGNET 2 0 0 1 12 12 0 0 1/1/2014 22:22 0 Magnets --none-- 1
Ummm, not sure which upgrade is considered to not be "possible", but that is one of the reasons that upgrades were performed to the EP4 software.

With the more recent support software, things like providing an empty quote when a number is expected no longer are considered acceptable practice.

Further, performing the upgrade of EP4 is relatively easy: upload new files, access the EP4 admin screen, select the update option on the top right corner. If there becomes a time to return to a previous version (not recommended) then selecting the uninstall in the upper right corner, followed by removal of the EP4 files and reinstall of the old files with reinstall would put things back to how they are/were.

To answer at least one of the questions:

Is the "products_tax_class_id" mapped to the "v_tax_class_title" column?

If the v_tax_class_title is provided, then the associated tax_class_id is pulled from ZC using the EP4 function: ep_4_get_tax_title_class_id. But, the reason that an issue is being seen is that the 0 or empty quotes from the export is not converted to an integer on import. So, if wanted to try to "patch" the software instead of using an up-to-date version, could cast that and any other data expected to be an integer (ie. Those typically ending with _id). So instead of the inline ```
='" . $v_tax_class_id ."'

Could instead use:

='" . (int)$v_tax_class_id ."'

Though, even then the single quote wouldn't be necessary because the content to be stored is a number not a string, so would use:

=" . (int)$v_tax_class_id ."

mc12345678:

To answer at least one of the questions:

If the v_tax_class_title is provided, then the associated tax_class_id is pulled from ZC using the EP4 function: ep_4_get_tax_title_class_id. But, the reason that an issue is being seen is that the 0 or empty quotes from the export is not converted to an integer on import. So, if wanted to try to "patch" the software instead of using an up-to-date version, could cast that and any other data expected to be an integer (ie. Those typically ending with _id). So instead of the inline ```
='" . $v_tax_class_id ."'

> Could instead use:
> ```
='" . (int)$v_tax_class_id ."'

Though, even then the single quote wouldn't be necessary because the content to be stored is a number not a string, so would use:

=" . (int)$v_tax_class_id ."

I had previously setup the tax options but hadn't been using it when entering products.
If I change the "--none--" to "Taxable Goods" EP4 works as advertised.
I'll need to test and see it that steps on anything in the rest of the ordering process.

THANKS for pointing me in the right direction.
I got so used to leaving that field set to "--none--" I did not see the trees for the forest. :blush:

Hi, A lot rusty on all fronts. Just installed Easypopulate 4 on v1.5.1 . On trying to run from Tools/Easy Populate 4 I get "This page isn’t working
blah blah is currently unable to handle this request.
HTTP ERROR 500"

Anyone have any ideas what might be happening. Have created a /temp in the admin area. Cheers

Gippo:

Hi, A lot rusty on all fronts. Just installed Easypopulate 4 on v1.5.1 . On trying to run from Tools/Easy Populate 4 I get "This page isn’t working
blah blah is currently unable to handle this request.
HTTP ERROR 500"

Anyone have any ideas what might be happening. Have created a /temp in the admin area. Cheers
Error log in the logs directory? (format of: myDebug-xxx) note that the log may contain admin directory information so if posted, recommend obscuring.)

mc12345678:

Error log in the logs directory? (format of: myDebug-xxx) note that the log may contain admin directory information so if posted, recommend obscuring.)

If there is nothing interesting in the ZC logs folder you might check the system logs folder in root. i.e. /
In my experiences with EP4 if the temp directory isn't correct it will throw a warning that no temp folder is available.
In addition to the logs can you post a screen shot of the screen that fails?
Do all the other Admin functions still work? If so carefully go back through your EP4 installation. Probably just a misstep.
Also what version of PHP is running.

Today products_sort_order failed with:

Stock Zen Cart 1.55f installed Easy Populate v4 on Linux with SQL 5.7 and php 7.1

Error:
MySQLi error 1366: Incorrect integer value: '' for column 'products_sort_order' at row 1
When executing:
INSERT INTO zen_products SET
...
product_is_call = 0,
products_sort_order = '',
products_quantity_order_min = 0,
...

Found in:
admin/easypopulate_4_import.php

Line 1039 and again 1190
$query = $db->bindVars($query, ':products_sort_order:', $v_products_sort_order, 'string');

And the fix:
$query = $db->bindVars($query, ':products_sort_order:', $v_products_sort_order, 'integer');

• Be sure to correct both lines/instances.

**

Also:
products_sort_order** in the db table is already set for **int(11) **NULL - NoDefault - 0

Hi

Maybe this as been answered hundreds of time, but by search it's not easy to find.
I've started working in a different way. Now the a lot products are already online in a "general" category.
So, I'll be updating and not inserting.
This process will create a linked category. Is there a way around it ?

Thanks

mesnitu:

Hi

Maybe this as been answered hundreds of time, but by search it's not easy to find.
I've started working in a different way. Now the a lot products are already online in a "general" category.
So, I'll be updating and not inserting.
This process will create a linked category. Is there a way around it ?

Thanks
Yes and no. Can't recall someone indicating that just because they "updated" the record(s) (submitted the same file exported as an import where each record has a unique primary key) that the product became linked.

So, here's how a linked product can be generated when using just EP4 (I can't at the moment speak for the bookx addition you've made) when reviewing the import file:
If a record has a primary key that matches an existing primary key in the database but the category is different, a linked product will be created/updated.
Note, if at import the database doesn't contain the associated primary key, but the file has two entries in it where each has a different category, then when the second record is encountered, that second record will cause the product to be linked to the new category and all associated data will be updated to match the most recent occurrence.

That's really all that will create a linked product.

So to avoid generating linked product, always use a unique primary key for each individual product. EP4 has two types of primary key available with the possibility to code additional: products_model and products_id.

To remove linked product, I suggest rereading the instructions, but by setting a row's status to 7, then the category identified on that row will become the master_categories_id. The current master_categories_id will be unlinked from the product. If there are multiple linked categories for a single product then it may be advisable to use this process for all records and then to "add" those desired to be linked after the linkages have been reduced down to a single master_categories_id. There are a number of ways to work through this situation, but that particular method would resolve the situation for all cases.

If you are getting linked product on import, either the primary_key data already exists or is duplicated in the import or there is something wrong with the bookx addition.

mc12345678:

To remove linked product, I suggest rereading the instructions, but by setting a row's status to 7

Wonderful!
Status 7 works perfectly!
Thanks!