EasyPopulate 4.0 Support Thread

[mc12345678]

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.