Printable View
Please see post #3495 which refers to: https://www.zen-cart.com/showthread....28#post1392328. From there please identify what issues there are with applying the sun total of two changes (one in the software the other in the admin configuration settings) to support operation in 1.5.8 and in general, respectively.Quote:
Originally Posted by diptimoy
v1.5.8
PHP Version: 7.4.33
I am getting this error:
SQLi error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '
categories_id = 3,
language_id = 1' at line 1
Have latest version from github.
Please help.
What is the filename of the file being imported?Quote:
Originally Posted by Speak394
Filename is Full-EP2023Apr25-201651.csv.
I am trying to download my products from a previous version of zencart 1.5.4 using Easy Populate 4.0.30 - Beta 06-27-2015, into my new zencart using Easy Populate 4.0.37.13 - 05-03-2021.
OK, here's my thought, though haven't been able to test all this out.Quote:
Originally Posted by Speak394
First, I suspect that the table definition for products_description has been altered from the Zen Cart default. It is possible that it has not been altered.
Identifying the table's definition would likely help resolving this issue.
My guess is that there is a field included that doesn't have a default value and because the query described below doesn't also provide a value for that field, the query fails. As such, if a field does exist without a default value, the below suggestion won't resolve the issue either.
Second is that for whatever reason the query syntax used to insert some data, appears to not be acceptable in this instance. So, I would suggest in admin/easypopulate_4.php modifying lines 1141-1145 from:
To:Code:$sql = "INSERT INTO " . TABLE_CATEGORIES_DESCRIPTION . " SET
categories_id = :categories_id:,
language_id = :language_id:,
categories_name = :categories_name:,
categories_description = :categories_description:";
Really, some more data should be collected about what issue really is experienced in the query.Code:$sql = "INSERT INTO " . TABLE_CATEGORIES_DESCRIPTION . " (categories_id, language_id, categories_name, categories_description) VALUES (
:categories_id:,
:language_id:,
:categories_name:,
:categories_description:)";
Hello, Can EP4 create linked products? What is the best method?
Thanks
Yes.Quote:
Originally Posted by djdavedawson
In part from the instructions:
Basically, whatever is used to "uniquely" identify the product has a category different than the original or an existing category will cause a linked version to be created. Further because rows are processed sequentially, the last row of data for that "unique" product will become the primary data for the entire product wherever it is shown/stored.Quote:
Also note that if you enter the same products_model twice, the latest (last) record
entry will over-write any previous entry. The exception here is if you enter a different category; this will result in a linked
product. This means that if two rows of data have the same v_products_model data with only a difference of the category name,
then the product will appear in both categories and a change to the data in one entry will appear in the other category. See the
previous sentence about effect of two products having the same products_model identifier.
How to import or add new products via easy populate , without matching product_models? I mean I want to make the csv and it will add new products to
my store which does not have any product model
You have options. The old school way would be to run a sql query that would generate a unique model for each product, then export that file, edit it and upload any changes. Hmm, though you asked about just adding product.Quote:
Originally Posted by diptimoy
Well, generally speaking the software currently expects to have something in the field associated with the unique identifier. So if you started using a model designation with your product to be added, then if it isn't in the database it will become a new product.
A more advanced method would be to use the products_id as the unique identifier with black to allow adding product. (blank_new setting). I warn you though that incorrect use of this option could destroy your database. Test with either of these methods on a backup of your database or a store not intended to make sales.
Please also read over the last page or so of posts. There are two issues still with the default install of the software, one is only present in zencart 1.5.8 and above. I'm close to issuing an update, though still worried that I haven't tested every possible issue sufficiently. Options and capability has been expanded so much, I inky expect a problem. Anyways, there is installation assistance over the last many pages, but it just basically repeats every few.
Quote:
Originally Posted by mc12345678
You mean if the CSV has a product_model column and that product_model data if not present in the database , it will add as a new product ?
In a default install yes. Again please test on a site not making you money. Also make a database backup before first trying. It's both easy and complicated, highly rule based.Quote:
Originally Posted by diptimoy
Quote:
Originally Posted by diptimoy
To be clear though, the field name is: products_model. Thus the field column header in the csv file should be: v_products_model.Quote:
Originally Posted by mc12345678
Such information becomes more obvious when reviewing the downloaded version of the exported file.
Again, it's those little things where it's both easy and complicated.
" To be clear though, the field name is: products_model. Thus the field column header in the csv file should be: v_products_model. "
I know this but for soem reason its not happening , product is skipped and warning says file is imported with issues .
Thanks for quick reply
Again, please see the issues with default install over the last several pages. The product must also have a category assigned to it.Quote:
Originally Posted by diptimoy
Feel free to post the settings of the configuration for the plug in, there may be something obvious there.
I didn't learn English and code well like myself, so I upgraded PHP and Zencard versions (php7.8 Zencard 1.5.7 to php8.1 Zencard 1.5.8), which directly caused the plugin to be unusable. This is a very frustrating thing .
Who can provide the latest plugin package for PHP 8.1 ZENCART 1.5.8a?
Just like the previously developed plugins, simply change the name of the management folder and upload it.
Apply the change described here: https://github.com/zencart/zencart/b...min_access.phpQuote:
Originally Posted by targetmarts
Depending on other factors there may be one other post that contains a correction needed.
Quote:
Originally Posted by targetmarts
Correction. Please identify what happens when and what version of this plugin is being used.Quote:
Originally Posted by mc12345678
we used the latest version from 2023.5 with zen cart 1.5.7b php 7.8 work fine,but it don't work and many other problem with zen cart after to zen cart 1.5.8a and php 8,1,and we install zen cart 1.5.8a in php 8.1 now,but it don't work when upload the easypopulate.Quote:
Originally Posted by mc12345678
heelsbags.com
1. Login to admin. OK. Yes/ no?Quote:
Originally Posted by targetmarts
2. Tools->Easy Populate 4. OK. Yes/ no?
3. Export all product. Ok. Yes/No?
4. Upload file.ok. Yes/ no?
5. Import file. OK. Yes/ no?
If no, explain what you see.
1. Login to admin. OK.Quote:
Originally Posted by mc12345678
2. Tools->Easy Populate 4. no,blank
........
And the bugs in log as here:Quote:
Originally Posted by mc12345678
-------------------------------------------
[17-Jul-2023 10:21:19 UTC] PHP Fatal error: Uncaught Error: Undefined constant "EP4_DB_FILTER_KEY" in /....../public_html/heelsbags/admin/easypopulate_4.php:23
Stack trace:
#0 /....../public_html/heelsbags/admin/index.php(11): require()
#1 {main}
thrown in /....../public_html/heelsbags/admin/easypopulate_4.php on line 23
[17-Jul-2023 10:21:19 UTC] Request URI: /admin/index.php?cmd=easypopulate_4, IP address: 240e:381:2763:9f00:ac1a:80d:306b:e5e8
--> PHP Fatal error: Uncaught Error: Undefined constant "EP4_DB_FILTER_KEY" in /....../public_html/heelsbags/admin/easypopulate_4.php:23
Stack trace:
#0 /....../public_html/heelsbags/admin/index.php(11): require()
#1 {main}
thrown in /....../public_html/heelsbags/admin/easypopulate_4.php on line 23.
Sorry for the significant delay.Quote:
Originally Posted by targetmarts
Obtain latest copy from: GitHub - mc12345678/EasyPopulate-4.0 at CSV-delimiter-catalog-message-correct
The direct zip file download link is: https://github.com/mc12345678/EasyPo...ge-correct.zip
Then load files, Access menu and perform install.
Then, go to configuration->EasyPopulate 4
Change setting for "Import Language Override" - language_code_only
to *any* other value.
Ok,Thank you very much .Quote:
Originally Posted by mc12345678
And the code maybe too naughty，i upload a data file,and import 268 items,then display error:
SKIPPED! - v_products_model: 20230710269 - No category provided for this new product importing with: language_code_only
SKIPPED! - v_products_model: 20230710270 - No category provided for this new product importing with: language_code_only
........
sure i have tried to check the data in file,sure it right,and there imported more items with same category,but it stop and display this error now.
and i sure i have try to fix any data file,and it always display this error,and i sure i have checked the category and it in my shop.
maybe have quantitative restriction in code?:D
For your first problem:
For example, change "Import Language Override" from language_code_only *to* language_id_onlyQuote:
Originally Posted by mc12345678
For second problem: Please identify the fields in your import file. The fields are the first row of the file. For example: v_products_modelQuote:
Originally Posted by targetmarts
It is possible that the file is too large to import all at once. There is a split option to allow making multiple smaller files from a single large file. I do not believe the file size is the problem. I received a copy of your debug log. When I know the field names, I expect I can determine a solution.
yes,i have do all as you said,and update one row file also show error.Quote:
Originally Posted by mc12345678
Your upload file. Please post the first row.Quote:
Originally Posted by targetmarts
Also, please post the configuration settings of EP4.
sorry to reply so later.Quote:
Originally Posted by mc12345678
Attachment 20351Attachment 20351
Easy Populate 4
Title Value Action
Uploads Directory temp/
Uploads Directory Admin/Catalog true Info
Import/Export Primary Key products_model Info
Import Language Override language_code_only Info
Import/Export CSV Delimiter , Info
Export Language Identifier id Info
Export Price Decimals 2 Info
Upload File Date Format m-d-y Info
Default Raw Time 09:00:00 Info
Export Filename Date Y-m-d Info
Upload/Download Prices Include Tax false Info
Update Check 1 Info
Verbose Feedback true Info
Show all EP4 Filetypes with Files true Info
Replace Blank Image false Info
Activate Blank Featured true Info
Remove Blank Specials negative Info
Make Zero Qty Products Inactive false Info
Smart Tags Replacement of Newlines true Info
Advanced Smart Tags false Info
Auto-extend fields false Info
Debug Logging true Info
Maximum Quantity Discounts 0 Info
Split On Number of Records 2000 Info
Script Execution Time 60 Info
Convert Curly Quotes, etc. 0 Info
Convert Character 0x92 1 Info
Enable Products Meta Data 1 Info
Enable Products Music Data 0 Info
User Defined Products Fields Info
Export URI with Prod and or Cat 0 Info
------------------------------------------------------------------------------
Here is the first line of data in the file ：
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 v_metatags_products_name_status v_metatags_title_status v_metatags_model_status v_metatags_price_status v_metatags_title_tagline_status v_metatags_title_1 v_metatags_keywords_1 v_metatags_description_1
Change: Import Language Override language_code_only InfoQuote:
Originally Posted by targetmarts
To: Import Language Override language_id_only Info
Or any other value.
I will use the provided information to solve the other problem.
Thank you,and i have inserted it.great helpQuote:
Originally Posted by mc12345678
Another question: How to set up support for special characters? Because when there are special characters or Chinese characters in the data, the plugin automatically truncates the following characters. For example, if the title is "fashion clothing wear 《freeshipping》", the plugin will generate the product title for" fashion clothing wear".Quote:
Originally Posted by mc12345678
Thanks,hope your help again.
New again user...
Got ZC installed, EP4 installed..no hiccups.
Formatted my CSV file from source data from a Shopify workflow, and ready to imports...cant:
Filename: ZC1.csv
SKIPPED! - v_products_model: 000-043-010-00 - No category provided for this new product
SKIPPED! - v_products_model: 000-043-204-94 - No category provided for this new product
SKIPPED! - v_products_model: 000-043-306-04 - No category provided for this new product
SKIPPED! - v_products_model: 000-044-000-04 - No category provided for this new product
Man..it LOOKS good..ive used OpenOffice to save this file as well as Excel, same issue in both worlds.
The noted category does in fact exist, I sense no issues, yet..there is an issue.
Im at the end of "learning" in the thread and in google for the moment..been a few hrs digging away at it.
TY for your time.
Do your settings look something like: https://www.zen-cart.com/showthread....95#post1396195 ?Quote:
Originally Posted by gemohler
Does the issue go away when the direction of three part that followed is performed? (https://www.zen-cart.com/showthread....97#post1396197)
The values are the same except for #Records that I increased. (Ill be doing massive uploads and I have bare metal and resources)
I just made the change to "language_id_only"
And THAT works. :)
And yup, those 5 worked..and a test of 5600 more just fine.
TY
Duplicate. :(
And then this happens.
Saved from open office, no changes other than a few 100k things added to the spreadsheet.
In this example, row 1 works.
Row 2 does not work.
They are functionally identical.
General EP question.
While doing a large import, apache is taking a lot of resources...
What is the WWW server doing during an import that makes IT so busy?
One thing that is happening while importing is that basically empty characters are being sent to the browser to keep the connection alive. The historical suggestion was to split large files into snake chunks. As development of the software continued, this alternative was implemented. The quantity or load may possibly be reduced. Though to date I believe this is the first such feedback received.Quote:
Originally Posted by gemohler
I'm not sure yet what characteristic would be best to monitor to reduce that traffic, whether a time, number of iterations or start value from either would be "ideal". Of course other ideas are welcome.
Quote:
Originally Posted by mc12345678
Ya..I mean, it doesnt break anything, but 75% of a CPU for apache2 is...busy.
On the lookout for things I need to know as I relearn the ZC environment.
Im doing EP4 imports, and I have a log file getting _hammered_ with this (attached)
Is there a mistake in the above writing? The image suggests that the first does not work and the second does. As far as the csv file, I usually ensure each field's content is surrounded by double quotes when saving the csv file from the workbook. While I was able to open that CSV file in a workbook to have the data in what looks like the appropriate fields, nothing specifically stands out visually as a problem.Quote:
Originally Posted by gemohler
When I get an opportunity I'll try running that file, but may be a bit.
I may have got the text backwards, but the excel file is in the order of the import results.Quote:
Originally Posted by mc12345678
Gotcha, before suggesting what I just came up with, need to look to see if I have an existing solution on my development server. Mind me asking your specs? PHP version for example?Quote:
Originally Posted by gemohler
Was the issue always discovered on the first line of any import or was the issue random throughout the import of the file?Quote:
Originally Posted by gemohler
Right on..Quote:
Originally Posted by mc12345678
THIS file had this issue. Everything after it failed.Quote:
Originally Posted by mc12345678
I took the data from THIS spreadsheet (except the header row), and put it in another one that did work (under it's header row)...and everything was fine.
I have this defined in the config:
User Defined Products Fields v_products_qty_box_status. (I have also tried this without v_)
I have this in my CSV:
v_products_qty_box_status
0
The one product I test this one, continues to show a qty available, which I want to set to hidden.
It seems as if I've done the right things as I've seen in a few good threads.
Looks like my solution was to change the various instances of:Quote:
Originally Posted by gemohler
$categories_name_exists = false;
To an empty array:
Worked in PHP 8.2.9 for me. I had just come up with another idea, but it required writing more code.Code:$categories_name_exists = array(); // used for backwards compatibility
$categories_name_exists = []; // accomplishes the same as above via shortened code
Just change those two instances in easypopulate_4_import.php?Quote:
Originally Posted by mc12345678
Simple enough. Was this having any impact other than a massive error log file?
That was in part my question to you. :smile: Looking over changes I have made to push to github, that appears to be all that I needed to do to support complete import of the records that were formatted correctly. Haven't heard if the above resolved the earlier issue of the two records where the first was bypassed but the second imported. Further, didn't see a response to the question about any sort of consistency of report saying not imported because the category name was missing.Quote:
Originally Posted by gemohler
Look forward to hearing results so that I can maybe prioritize some of the patches/changes that have been made.
CORRECTION: Apparently there are responses above that I did not see/fully read. Maybe more to follow from me? :blink:
If you also go to the admin version of the product information page for that product, there should be an entry for a term equal to or similar to product qty maximum. Is it/has it been updated to reflect the value of 0?Quote:
Originally Posted by gemohler
If it has been updated to a value of zero and the box shows on the catalog side for the product then the issue is template related and not database/EP4 related.
Again, though the entry in the user defined Products Fields should not begin with v_ unless the field in your table also starts with v_.
The intention is to list the field designation as entered in the table.
Then, when working in the CSV file(s) that is where the v_ becomes important.
(Remember, with the desired user defined products fields entered exporting data should create a file that includes the entered field(s). Additionally, the right side of the admin screen should confirm the presence of the entered User Defined Products Field(s).)
"If it has been updated to a value of zero and the box shows on the catalog side for the product then the issue is template related and not database/EP4 related."
This is in fact the case, TY.
Still I cant find ANY reason why apache gets so wrapped up in the import process.Quote:
Originally Posted by gemohler
The file is on disk
Nothing is in the access or error logs..so..clicking "import" does nothing to apache.
I dont have the skillset to PROVE it, but I would guess that this is an IO constraint to getting database work done...but I dont know how.
All I know is when I do an import/export, any high DB activity (I deleted a large dummy category to test this) apache2 jumps in to suck up a lot of CPU...while doing nothing observable.
Quote:
Originally Posted by gemohler
Let me ask this..
Are you sending apache a running list of things imported? Im now at a point where apache is outrunning the DB un CPU use.
How about also an option to output import per-product status to a log file, as..well, it's sorta useless if you have a large # of items.
Zencart 1.5.8a
MySQL updated from 5.7 to 8.0.34
This is 100% my mistake. I am an noob and got a notification that 5.7 was no longer going to be supported after this month so I decided to upgrade MySQL. Ran into a couple of issues. First my home page no longer works. (all of the other links work though and check out seems to be fine) I am currently working with the developer of the template to help fix it (PHP Fatal error: 1525:Incorrect DATETIME value: '' ::) I tried turning off strict mode and allowing invalid dates but nothing.
But now with EasyPopulate it seems I am having issues now as well.
I uploaded 5 new products and for some reason one product keeps getting thrown into a totally different category.
I ended up using a brand new spreadsheet with just the 5 products inside and still getting the issue. I checked the logs and it doesn't make sense because it is giving me errors for products that aren't even in the new spreadsheet and as far as I can tell the products it is listing do not have the issues stated. Been kicking myself for why I decided to update in first place. Really appreciate your guys' help.
Only including some of the log as it was way too long
Code:MySQLi error 1406: Data too long for column 'products_url' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
765,
'Torque Solution Genesis Coupe 2.0T Tial Blow Off Valve Adapter 2010 – 2014', 'Torque Solution Tial Blow off Valve Adapter\n\nApplication: Hyundai Genesis Coupe 2.0T 2010+\n\n\nReplace your oem diverter valve using Torque Solution\'s Billet Tial Blow off Valve Adapter. This allows you to direct fit your Tial Q or QR blow off valve to your Hyundai Genesis Coupe 2.0T without any welding or modifications at all. \n\n- CNC machined 6061-T6 billet aluminum\n- Installs in under 30 minutes\n- Direct Fitment\n- Includes mounting bolts & o-rings\n- Limited Lifetime Warranty', 'TorqueSolutionTialBlowoffValveAdapterApplication:HyundaiGenesisCoupe2.0T2010+TorqueSolutionBilletTialBlowoffValveAdapterallowsyoutodirectfityourTialQorQRblowoffvalvetoyourHyundaiGenesisCoupe2.0Twithoutanyweldingormodificationsatall.-CNCmachined6061-T6billetaluminum-Installsinunder30minutes-DirectFitment-Includesmountingbolts&o-rings-LifetimeWarranty',
1)
MySQLi error 1406: Data too long for column 'products_url' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
766,
'Torque Solution Genesis Coupe 2.0T Greddy BOVAdapter 2010 – 2014', 'Torque Solution Greddy Blow off Valve Adapter\n\nApplication: Hyundai Genesis Coupe 2.0T 2010+\n\n\nReplace your oem diverter valve using Torque Solution\'s Billet Greddy Blow off Valve Adapter. This allows you to direct fit your Greddy blow off valve to your Hyundai Genesis Coupe 2.0T without any welding or modifications at all. \n\n- CNC machined 6061-T6 billet aluminum\n- Installs in under 30 minutes\n- Direct Fitment\n- Includes mounting bolts & o-rings\n- Limited Lifetime Warranty', 'TorqueSolutionGreddyBlowoffValveAdapterApplication:HyundaiGenesisCoupe2.0T2010+TorqueSolutionBilletGreddyBlowoffValveAdapterallowsyoutodirectfityourblowoffvalvetoyourHyundaiGenesisCoupeTurbowithoutanyweldingormodificationsatall.-Cncmachined6061-T6billetaluminum-Installsinunder30minutes-DirectFitment-LifetimeWarranty',
1)
MySQLi error 1366: Incorrect decimal value: '' for column 'products_price' at row 1
When executing:
INSERT INTO products SET
products_model = '10HYGEN2DOE-030C',
products_type = 1,
products_price = '', products_image = 'Genesis Coupe/10HYGEN2DOE-030C.jpg',
products_weight = 125,
products_discount_type = 0,
products_discount_type_from = 0,
product_is_call = 0,
products_sort_order = 0,
products_quantity_order_min = 1,
products_quantity_order_units = 1,
products_priced_by_attribute = 0,
product_is_always_free_shipping = 0,
products_tax_class_id = 1,
products_date_available = NULL,
products_date_added = '2023-09-04 00:00:00',
products_last_modified = CURRENT_TIMESTAMP,
products_quantity = 10,
master_categories_id = 280,
manufacturers_id = 57,
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
MySQLi error 1366: Incorrect string value: '\xEF\xBE's s...' for column 'products_description' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
1191,
'Riaction Genesis Coupe GP-1 TRUE REAR Digressive Coilover Set 2010 - 2016', 'The GP-1 Digressive Coilover is different than the linear valved system in terms of damper valving. This means the damper has much more low speed control in comparison to a Linear valve. This is due to the low flow rate at low shaft speeds. The resistance rate increases as shaft speeds increase, but only to a pre-determined level, whereas the Linear variant continues to increase. The digressive valving then has resistance that tapers off and as the shaft speed continues to increase, the resistance remains constant. This eliminates unnecessary resistance and provides more control as the vehicle encounters irregularities in the roadï¾\'s surface. This setup will do a better job of managing unwanted body motions while also still providing a comfortable ride.\n\nThe digressive coilover system is great for street use, canyon carving, and track days.\n\n\nRiaction sports coilover kits are designed for street cars which are looking for lower ride height, better handling, and greater comfort. Each set of Riaction USA coilovers are made from high quality materials with precision design, to ensure a reliable and durable product that performs. We proudly stand by all of our products, and each Riaction USA sports coilover kit comes with a standard 2 year factory warranty against any factory defects.\n\nCOILOVER FEATURES\n\n-Full Length Ride Height Adjustment\n-32 Damping Adjustment Levels\n-Mono-Tube Damper Design\n-Seamless 52mm Electroplated Carbon Steel Shock Body\n-O.D. 20mm Piston Rod For McPherson Suspension\n-O.D. 14mm Piston Rod For Non-McPherson Suspension\n-Unique 44mm High-Flow CNC 6061 Aluminum Piston\n-Unique Thinned CNC 6061 Aluminum Floating Piston\n-Polyurethane Oil Seal\n-SAE9254 Cold-Wound Spring\n-Multi-Thickness Valving Shims\n-Unique Low-Gas Pressure Design\n-7.5w Compounded Suspension Fluid\n-Fully Rebuild-able-Wound Spring\n-Multi-Thickness Valving Shims\n-Unique Low-Gas Pressure Design\n-7.5w Compounded Suspension Fluid\n-Fully Rebuild-able\n\nFACTORY SPRING RATES: 8K (Front) - 6K (Rear)', '',
1)
MySQLi error 1366: Incorrect string value: '\xEF\xBE's s...' for column 'products_description' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
1192,
'Riaction Genesis Coupe GP-1 DIGRESSIVE Coilover Set 2010 - 2016', 'The GP-1 Digressive Coilover is different than the linear valved system in terms of damper valving. This means the damper has much more low speed control in comparison to a Linear valve. This is due to the low flow rate at low shaft speeds. The resistance rate increases as shaft speeds increase, but only to a pre-determined level, whereas the Linear variant continues to increase. The digressive valving then has resistance that tapers off and as the shaft speed continues to increase, the resistance remains constant. This eliminates unnecessary resistance and provides more control as the vehicle encounters irregularities in the roadï¾\'s surface. This setup will do a better job of managing unwanted body motions while also still providing a comfortable ride.\n\nThe digressive coilover system is great for street use, canyon carving, and track days.\n\n\nRiaction sports coilover kits are designed for street cars which are looking for lower ride height, better handling, and greater comfort. Each set of Riaction USA coilovers are made from high quality materials with precision design, to ensure a reliable and durable product that performs. We proudly stand by all of our products, and each Riaction USA sports coilover kit comes with a standard 2 year factory warranty against any factory defects.\n\n\nCOILOVER FEATURES\n\n-Full Length Ride Height Adjustment\n-32 Damping Adjustment Levels\n-Mono-Tube Damper Design\n-Seamless 52mm Electroplated Carbon Steel Shock Body\n-O.D. 20mm Piston Rod For McPherson Suspension\n-O.D. 14mm Piston Rod For Non-McPherson Suspension\n-Unique 44mm High-Flow CNC 6061 Aluminum Piston\n-Unique Thinned CNC 6061 Aluminum Floating Piston\n-Polyurethane Oil Seal\n-SAE9254 Cold-Wound Spring\n-Multi-Thickness Valving Shims\n-Unique Low-Gas Pressure Design\n-7.5w Compounded Suspension Fluid\n-Fully Rebuild-able-Wound Spring\n-Multi-Thickness Valving Shims\n-Unique Low-Gas Pressure Design\n-7.5w Compounded Suspension Fluid\n-Fully Rebuild-able', '',
1)
MySQLi error 1406: Data too long for column 'products_url' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
1385,
'IRP GENESIS COUPE RACING SHIFTER FOR MANUAL TRANSMISSION 2010 – 2016', '', '<p>IRPRacingShifter(IndividualRacingProducts)isfinallyhereintheUSA!TheseshiftersarethetoplineracingqualityfortheGenesisCoupeManualtransmissions2010-2016.Thisdesignisadirectdrivesystemthatremovesallyourfactorylinkageandbushings.Bydoingthisdesign,yougetasharp,crispshiftingfeelthatallowsextremelyfastshiftingonthetrack.Wepersonallytestedtheseonourracecarsaregaveitfivestarsforperformance!Wellworthit'svalue.Thesidesetscrewsallowsforadjustmentonleftandrightthrow.Evenbetter,theunithasabuiltinreverselockoutbuttonthatallowsreverseonlytobeusedwhenthedriverpushesthebuttonontopoftheshifter.Thismakesforlessmistakeswhenquicklygoingintofirstgear. </p><p> </p><p>CNCAluminumlightweightdesign<br/>ReverseLockOutButton<br/>Adjustableleftandrightmaxthrow<br/>Bearingdesignforzeroplay<br/>Precisegearengagement<br/>Allowsdrivertoshiftmuchfaster<br/>Crispracefeelshifting<br/>DesignedforRacingPurposes </p><p> </p><p><iframeallowfullscreen=\"\"frameborder=\"0\"height=\"360\"src=\"//www.youtube.com/embed/8fEMSLk2bQ4\"width=\"640\"></iframe></p>',
1)
MySQLi error 1406: Data too long for column 'products_url' at row 1
When executing:
INSERT INTO products_description (
products_id,
products_name, products_description, products_url,
language_id )
VALUES (
1520,
'Prosport Premium Evo Digital Boost Gauge', '', '<p>Ifyourvehicleissuperchargedorturbochargedthenthisgaugeissimplyamusthave.ForpeakperformanceyouneedtoknowhowmuchboostyouaremakingatmaximumRPM's.Nowyoucanaccuratelymonitoryourboostasyoumodifyyourride!</p><p>Saveyourturbo-Setthewarningfeaturetoalertyoubeforeyouoverboost.Fullyprogrammabletoanylevelyouwant.Makechangeswithinsecondsusingthebuttonsonthefrontofthegauge.</p><p>Features:</p><ol><li>PeakRecall</li><li>FullyprogrammableWarningfeature</li><li>Dimmable</li><li>Daisychain</li><li>Premiumwaterproofsender</li><li>Wireharness(gaugetosender-plugandplay)</li><li>4colorchoices</li><li>Mountingcup</li><li>Visor</li><li>Freetechsupport<br/> </li></ol><p>ThisElectricBoostGaugewillperformadigitalsweep/selfcheckonStart-up.</p><p>(-30vacto35PSI)</p><p>Includes:</p><ol><li>Mountinghardware</li><li>TubingKit</li><li>T-Adaptor</li><li>WaterproofElectricalsender</li><li>Wiringharness</li><li>Visor</li><li>Prosportdecal</li><li>Instructions</li></ol><p> </p><p><iframeallowfullscreen=\"\"frameborder=\"0\"height=\"360\"src=\"//www.youtube.com/embed/Lk5xXoOPmHg\"width=\"640\"></iframe></p>',
1)
MySQLi error 1062: Duplicate entry '512' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
512, '', 222, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '512-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 512,
language_id = 1,
categories_name = 'Accessories',
categories_description = ''
MySQLi error 1062: Duplicate entry '512' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
512, '', 222, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '512-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 512,
language_id = 1,
categories_name = 'Accessories',
categories_description = ''
MySQLi error 1062: Duplicate entry '512' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
512, '', 222, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '512-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 512,
language_id = 1,
categories_name = 'Accessories',
categories_description = ''
Not exactly sure what the creator of the template did but when he fixed the issue with the homepage for some reason it also fixed the easypopulate issue as far as I can tell :smile:
Quote:
Originally Posted by project jayden
URL: kdmracer.com
Zencart Version 1.5.8a
Latest EasyPopulate version
PHP Version: 8.0.30
Issue started when MySQL updated from 5.7 to 8.0.34
Finally was able to generate an error log through easypopulate. This was after I tried creating new main category & sub categories. Products ended up being placed in the main category instead of where they were supposed to go.
Code:MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Engine',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Air Intake',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Suspension',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Lowering Springs',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Engine',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Air Intake',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Suspension',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Lowering Springs',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Engine',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Air Intake',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Brakes',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Rotors',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Brakes',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Rotors',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Brakes',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Rotors',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Brakes',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Rotors',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Brakes',
categories_description = ''
MySQLi error 1062: Duplicate entry '514' for key 'categories.PRIMARY'
When executing:
INSERT INTO categories(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
) VALUES (
514, '', 514, 0, CURRENT_TIMESTAMP, CURRENT_TIMESTAMP
)
MySQLi error 1062: Duplicate entry '514-1' for key 'categories_description.PRIMARY'
When executing:
INSERT INTO categories_description SET
categories_id = 514,
language_id = 1,
categories_name = 'Rotors',
categories_description = ''
Try undoing (reversing) the following commit: New category_id based on auto_number · mc12345678/EasyPopulate-4.0@c870394 (github.com)Quote:
Originally Posted by project jayden
Thank you for the reply! Unfortunately ran into the same issue. Products ended up in the main category instead of the subcategories and now also included errors in regards to MySQLi error 1062: Duplicate entry '515' instead of just 514.
Code:[24-Oct-2023 23:03:08 UTC] Request URI: /************/index.php?cmd=easypopulate_4, IP address: 107.193.59.101, Language id 1
#1 ep_4_get_tax_title_class_id() called at [/home/************/public_html/kdmracer/************/easypopulate_4_import.php:651]
#2 include_once(/home/************/public_html/kdmracer/************/easypopulate_4_import.php) called at [/home/************/public_html/kdmracer/************/easypopulate_4.php:565]
#3 require(/home/************/public_html/kdmracer/************/easypopulate_4.php) called at [/home/************/public_html/kdmracer/************/index.php:11]
--> PHP Warning: Trying to access array offset on value of type null in /home/************/public_html/kdmracer/************/includes/functions/extra_functions/easypopulate_4_functions.php on line 407.
Just a quick update.
So easypopulate would work fine If a category already existed it.
Issue seemed to be when creating new categories.
One work around was to create the categories manually and then uploading the spreadsheet...twice.
For some reason the first time would generate errors and only do a partial upload of new products. The second time it would be fine and upload everything correctly.
Anyways we are going to try and downgrade MySQL server later tonight back to 5.7 since we can't figure out what was going on. crossing fingers everything works after.
Deleted. Hadn't seen previous reply.
Quote:
Originally Posted by project jayden
I'm going to try to reproduce this situation using a similar mySQL server version. I believe I came across it and that is why my development code went back to restore the code in this area. Specifically I have this:Quote:
Originally Posted by mc12345678
Code:// get next available categoies_id (though could replace the last deleted category id..// $sql = "SHOW TABLE STATUS LIKE '" . TABLE_CATEGORIES . "'"; $sql = "SELECT MAX(categories_id) + 1 max FROM " . TABLE_CATEGORIES; $result = ep_4_query($sql); unset($sql); $row = $ep_4_fetch_array($result); unset($result);// $max_category_id = $row['Auto_increment']; $max_category_id = $row['max']; // if database is empty, start at 1 if (!isset($max_category_id) || !is_numeric($max_category_id) || $max_category_id == 0) { $max_category_id = 1; }
There are two things reported here. One, by the text at the beginning of this message, it looks like yes inserting a new category doesn't establish a parent/child relationship which causes the duplicate entry (child being inserted as if it is the parent also. The value 515 represents the category_id value that already exists but is attempted to be used again. The second issue is in relation to not having a tax_class_id for the given tax class title, this is a different issue than previously reported. I have a fix for this second one, but no idea the state of the code on your system because it seems things change so quickly and possibly drastically.For this second issue, I have the following in my development site at what is reported above as line 407 in admin/includes/functions/extra_functions/easypopulate_4_functions.php:instead of:Quote:
Originally Posted by project jayden
modify it to:Code:$tax_class_id = $tax_class_array['tax_class_id'];
Code:$tax_class_id = !empty($tax_class_array['tax_class_id']) ? $tax_class_array['tax_class_id'] : 0;
Yes, it is this adding new category aspect that is to be corrected and is causing problems.Basically, a different method was attempted which is intended to use the categories table auto number field to support inserting the next set of data. The problem is though that until some other action occurs, that number is held while operations continue. I had changed the process so that the next number to be used would have come from the highest value the database had seen which would also increase on each insert. The problem is that the auto_number doesn't increase while still within the same "run". The alternative "original" method looks for the highest value currently used and adds one. This is a problem because if a category exists in the database and it is the current highest value and that gets deleted (purposefully), pulling the highest value plus one results in a number that was previously used instead of the next unused number.Would be nice to know what these "some" errors are so that can either show what is to be done to correct or develop something new.I'm near issuing a new version that has A LOT of changes, improvements and compatibility with ZC 1.5.8x to not need any changes to that code. I have to do some testing though before I feel comfortable even offering it to others to do some testing. One of the things I am last working on is code that ensures default table values are retrieved and of the applicable database type and gets handled through the rest of the php code in the expected converted data type.Quote:
Originally Posted by project jayden
Well, unfortunately when I posted my previous message with a code block, all of the code got squished into a single line instead of broken out to rows and then when I went to edit the post all I have is a blank text box to "edit".
The first code block should look like:
Code:} else { // otherwise add new category
// get next available categoies_id (though could replace the last deleted category id..
// $sql = "SHOW TABLE STATUS LIKE '" . TABLE_CATEGORIES . "'";
$sql = "SELECT MAX(categories_id) + 1 max FROM " . TABLE_CATEGORIES;
$result = ep_4_query($sql);
unset($sql);
$row = $ep_4_fetch_array($result);
unset($result);
// $max_category_id = $row['Auto_increment'];
$max_category_id = $row['max'];
// if database is empty, start at 1
if (!isset($max_category_id) || !is_numeric($max_category_id) || $max_category_id == 0) {
$max_category_id = 1;
}
// TABLE_CATEGORIES has 1 entry per categories_id
$sql = "INSERT INTO " . TABLE_CATEGORIES . "(categories_id, categories_image, parent_id, sort_order, date_added, last_modified
Just putting it out there. I've posted on github an update to this module. I haven't made it the master code yet as I would appreciate some feedback on its use before committing it as the next release.
Generally, the software has been put together to work with the zc_plugins directory, though some limitations of Zen Cart's implementation of that process have required a usual some tricks to be incorporated into installation.
I haven't yet seen what I might consider good instruction for this possibility, but the code can be installed in the same places as it usually is or it can be placed in a version folder.
There are some limitations and issues that might occur if both are done on the one site. May not be an issue now, but may be in the future.
Anyways, I may still add a little to the github branch, but in my testing, neither of the previous main two issues exist.
Branch link to version 4.0.39.ZC: https://github.com/mc12345678/EasyPo...ree/v4.0.39.ZC
Tested on zencart 1.5.8a with latest github updates applied and php 8.3.
I just wanted to reach out as I saw that you had some updates on the easy populate plug-in. Initially we had fixed this issue by downgrading our MySQL to I believe my SQL to 5.7 which fixed all the issues with the creation of new categories and data input but now our server got automatically updated to the new version of MySQL again which I believe was a forced update as no one on our end made any changes.
Unfortunately I am back to square one on this. The link you provided for the newest version does it fix these issues?
Thank you for your time.
Quote:
Originally Posted by mc12345678
Sorry for the delay in responding. Yes, that issue is expected to be resolved with the root of the problem further discussed here: Duplicate entry when trying to add product with two level category neither existing · Issue #67 · mc12345678/EasyPopulate-4.0 (github.com)Quote:
Originally Posted by project jayden
Ok, so root of the problem may be how I had modified the code; however, that was based on conversations from several years ago. Thought was that the database record of what the next record was supposed to be would remain up-to-date. True if that value isn't cached... Newer versions of mySql cache the value making it unreliable during a database access. On the next query it gets updated.
dear EP4, I met some problem when i populate our product.
EP4+ZC1.5.8a
firstly, I exported CVS via "Filterable Exports" function.
then I edited my new product in this CVS file.
leave the same value on column "v_categories_name_1", it's not blank
then I got the error:No category provided for this new product.
attachment is my EP4 setting and circumstance, cvs file.
Attachment 20456
Attachment 20457
Attachment 20458
who can help me ?
In fact, I'm having trouble understanding the operating logic of ep4:
When I upload a new product, but its v_products_model already exists, after performing the upload, it is treated as an old product, and the upload action is regarded as a modification to the old product.
If you change the record's v_categories_name_1, it will generate a copy of the old product under the new category.
I think there should be a column to mark that this record is for uploading a new product, rather than modifying an old product.
Or is it possible that the CSV I'm using to upload new products is incorrect in the first place? I got it from the Filterable Exports of ep4.
Thank you, I would greatly appreciate it if someone could help me solve this problem with uploading new products.
If using the version downloaded from the zen cart site, then please read back over any of the recent pages of this thread about how to resolve the missing category issue.Quote:
Originally Posted by chens19
Regarding the linking of product described for using a single product model to describe two or more different product, may I suggest reading the instructions about using the products id instead of the products model as the primary key.
If you have downloaded the version referenced about two posts ago, then please identify the history of versions on the server. The version recently posted about should not initially have the problem described about a missing category. Unfortunately, as the version on the zen cart site appears to have been installed, upgrading to the above version will still have it. To correct one the new above version is installed, remove or uninstall the database settings and then reinstall the plugin to apply the correct default settings. Otherwise follow the guidance discussed on nearly every page of this thread for several, several pages back.
thank you for your reply.Quote:
Originally Posted by mc12345678
in this thread , there are more than 350 pages, I have read first 80 pages, and didn't find solution.
it's really too long thread.
Quote:
Originally Posted by mc12345678
thank you so much.
I found the solution.
EP4+ZC1.5.8a
EasyPopulate-4.0-4.0.37.13
When I go to Tools and click on Easy Populate 4, all I get is a blank screen. Have used this program on 4 or 5 other sites and never had any problems.
There are two known issues with that arrangement with a potential third depending on the mySql configuration. The two problems are addressed by review of almost any of the recent pages of this thread. An updated version not having those problems is referenced a few posts ago, available from github.Quote:
Originally Posted by Jeffg23
For clarity, I expect when stating that have a blank page that mean entirely blank, not just blank below the menu bar?
I tried both versions, the one in ZC Plugins, and the one from github.
Page is completely blank. Even tried to look at the page source, shows nothing.
The url listed in the browser for the blank page is: index.php?cmd=easypopulate_4
What was the attempted file placement for the one on github? If solely placed in the zc_plugins directory, then the previous version located in the admin directory must be removed. Also with it in the zc_plugins directory, it would need to be installed using the plugin manager.Quote:
Originally Posted by Jeffg23
If all of the admin files were placed in the admin (overwriting the older version) then that's something to work out because I have tried installing both ways with success on php 8.3.
Side note, generally speaking I would expect some sort of admin side debug log to be generated in the logs directory because of the blank screen. The contents of that (minus specific identification of the admin directory) would be helpful to us both. :)
here is the admin log file:
[09-Feb-2024 09:37:11 America/Chicago] Request URI: /store/xxxxxxxxxxxxxx/index.php?cmd=easypopulate_4, IP address: 135.129.209.218, Language id 1
#1 fopen() called at [/home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php:166]
#2 require(/home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php) called at [/home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/index.php:11]
--> PHP Warning: fopen(/home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/EASYPOPULATE_4_CONFIG_TEMP_DIR/ep_debug_log.txt): Failed to open stream: No such file or directory in /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php on line 166.
[09-Feb-2024 09:37:11 America/Chicago] PHP Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php:167
Stack trace:
#0 /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php(167): fclose(false)
#1 /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/index.php(11): require('/home1/alternb0...')
#2 {main}
thrown in /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php on line 167
[09-Feb-2024 09:37:11 America/Chicago] Request URI: /store/xxxxxxxxxxxxxx/index.php?cmd=easypopulate_4, IP address: 135.129.209.218
--> PHP Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php:167
Stack trace:
#0 /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php(167): fclose(false)
#1 /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/index.php(11): require('/home1/alternb0...')
#2 {main}
thrown in /home1/alternb0/public_html/rcgstore.com/store/xxxxxxxxxxxxxx/easypopulate_4.php on line 167.
=================================Quote:
Originally Posted by Jeffg23
It was the missing: EASYPOPULATE_4_CONFIG_TEMP_DIR. I created it and refreshed the admin page and now it works. From the install.txt file, I thought if the directory was not there it would give me an error. Still learning ZC at 78 !! :wacko:
So, I might have expected the same and in my testing I didn't come across that hard stop error. I see what can be changed to prevent that response. It is to change the if statement in line 165 to first check if logging should happen and then validate the folder exists before entering that area. I'll also look further downstream for similar issue...Quote:
Originally Posted by Jeffg23
Thank you for your reporting!!!
Greetings!
I am having a small problem installing easy pop
All files have been installed and I created a "temp" folder in my admin where I put the .htaccess file. Easy populate 4 shows up in my tools but when I click on it I get an http error 500 so I'm unable to install ep4 configuration data
Attachment 20521
Attachment 20522
Can anyone help?
There should be a log generated. I personally would expect it to be in your ZC logs folder, but it may be in your temp directory where EP4 files are accessed.Quote:
Originally Posted by Fenomenal7
Is this a new install, an upgrade, something else?
It's a new install. Yes, there was a generated log:Quote:
Originally Posted by mc12345678
Quote:
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EP4_DB_FILTER_KEY - assumed 'EP4_DB_FILTER_KEY' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 23.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_TEMP_DIR - assumed 'EASYPOPULATE_4_CONFIG_TEMP_DIR' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 41.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_FILE_DATE_FORMAT - assumed 'EASYPOPULATE_4_CONFIG_FILE_DATE_FORMAT' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 42.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_DEFAULT_RAW_TIME - assumed 'EASYPOPULATE_4_CONFIG_DEFAULT_RAW_TIME' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 43.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_DEBUG_LOGGING - assumed 'EASYPOPULATE_4_CONFIG_DEBUG_LOGGING' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 44.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_SPLIT_RECORDS - assumed 'EASYPOPULATE_4_CONFIG_SPLIT_RECORDS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 45.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_PRICE_INC_TAX - assumed 'EASYPOPULATE_4_CONFIG_PRICE_INC_TAX' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 46.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_SMART_TAGS - assumed 'EASYPOPULATE_4_CONFIG_SMART_TAGS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 47.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_MAX_QTY_DISCOUNTS - assumed 'EASYPOPULATE_4_CONFIG_MAX_QTY_DISCOUNTS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 48.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_VERBOSE - assumed 'EASYPOPULATE_4_CONFIG_VERBOSE' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 49.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_EXECUTION_TIME - assumed 'EASYPOPULATE_4_CONFIG_EXECUTION_TIME' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 50.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_CURLY_QUOTES - assumed 'EASYPOPULATE_4_CONFIG_CURLY_QUOTES' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 51.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_CHAR_92 - assumed 'EASYPOPULATE_4_CONFIG_CHAR_92' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 52.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_META_DATA - assumed 'EASYPOPULATE_4_CONFIG_META_DATA' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 53.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_MUSIC_DATA - assumed 'EASYPOPULATE_4_CONFIG_MUSIC_DATA' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 54.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_TEMP_DIR - assumed 'EASYPOPULATE_4_CONFIG_TEMP_DIR' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php on line 156.
[17-Mar-2024 10:48:29 America/Boise] PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php:625
Stack trace:
#0 /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php(469): ep_4_query('SHOW COLUMNS FR...')
#1 /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php(173): ep_4_check_table_column('products_descri...', 'products_short_...')
#2 /home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php(11): require('/home2/cedargr4...')
#3 {main}
thrown in /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php on line 625
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/franK-jLN-Sunny/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
--> PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php:625
Stack trace:
#0 /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php(469): ep_4_query('SHOW COLUMNS FR...')
#1 /home2/cedargr4/public_html/new/franK-jLN-Sunny/easypopulate_4.php(173): ep_4_check_table_column('products_descri...', 'products_short_...')
#2 /home2/cedargr4/public_html/new/franK-jLN-Sunny/index.php(11): require('/home2/cedargr4...')
#3 {main}
thrown in /home2/cedargr4/public_html/new/franK-jLN-Sunny/includes/functions/extra_functions/easypopulate_4_functions.php on line 625.
Its a new install. Yes, I found the log. Should I send it to you in a private message?Quote:
Originally Posted by mc12345678
It's generally better to post it on the forum as others may also be able to assist. When posting any file contents don't forget to remove or change any sensitive information from the log file such as name of the admin folder/passwords/etc.Quote:
Originally Posted by Fenomenal7
okQuote:
Originally Posted by simon1066
Attachment 20524Attachment 20525Attachment 20526Attachment 20527
last 1Quote:
Originally Posted by Fenomenal7
Attachment 20528
Quote:
Originally Posted by Fenomenal7
It is/ was a fair question and an appropriate response had also been given. I can also appreciate the desire to privately address an issue perhaps considered embarrassing to either party.Quote:
Originally Posted by simon1066
That said, the general idea of the forum is to allow others to see the issues and potential resolutions after all there are many that are helpful, many that wish to improve code and many that may have a similar issue.
That all said, I see that photos were published. Photos remain one of the difficult items to fully address. Screen readers can't see the text, and at least in this case the image doesn't expand well. Posting the text, with say the admin directory called just admin, or the site called mysite, those sort of things.
Sorry. Here's what the log says:Quote:
Originally Posted by mc12345678
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EP4_DB_FILTER_KEY - assumed 'EP4_DB_FILTER_KEY' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 23.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_TEMP_DIR - assumed 'EASYPOPULATE_4_CONFIG_TEMP_DIR' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 41.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_FILE_DATE_FORMAT - assumed 'EASYPOPULATE_4_CONFIG_FILE_DATE_FORMAT' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 42.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_DEFAULT_RAW_TIME - assumed 'EASYPOPULATE_4_CONFIG_DEFAULT_RAW_TIME' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 43.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/SSs/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_DEBUG_LOGGING - assumed 'EASYPOPULATE_4_CONFIG_DEBUG_LOGGING' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 44.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_SPLIT_RECORDS - assumed 'EASYPOPULATE_4_CONFIG_SPLIT_RECORDS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 45.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_PRICE_INC_TAX - assumed 'EASYPOPULATE_4_CONFIG_PRICE_INC_TAX' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 46.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_SMART_TAGS - assumed 'EASYPOPULATE_4_CONFIG_SMART_TAGS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 47.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_MAX_QTY_DISCOUNTS - assumed 'EASYPOPULATE_4_CONFIG_MAX_QTY_DISCOUNTS' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 48.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_VERBOSE - assumed 'EASYPOPULATE_4_CONFIG_VERBOSE' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 49.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_EXECUTION_TIME - assumed 'EASYPOPULATE_4_CONFIG_EXECUTION_TIME' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 50.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_CURLY_QUOTES - assumed 'EASYPOPULATE_4_CONFIG_CURLY_QUOTES' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 51.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_CHAR_92 - assumed 'EASYPOPULATE_4_CONFIG_CHAR_92' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 52.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_META_DATA - assumed 'EASYPOPULATE_4_CONFIG_META_DATA' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 53.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_MUSIC_DATA - assumed 'EASYPOPULATE_4_CONFIG_MUSIC_DATA' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 54.
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
#1 require(/home2/cedargr4/public_html/new/admin/easypopulate_4.php) called at [/home2/cedargr4/public_html/new/admin/index.php:11]
--> PHP Warning: Use of undefined constant EASYPOPULATE_4_CONFIG_TEMP_DIR - assumed 'EASYPOPULATE_4_CONFIG_TEMP_DIR' (this will throw an Error in a future version of PHP) in /home2/cedargr4/public_html/new/admin/easypopulate_4.php on line 156.
[17-Mar-2024 10:48:29 America/Boise] PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php:625
Stack trace:
#0 /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php(469): ep_4_query('SHOW COLUMNS FR...')
#1 /home2/cedargr4/public_html/new/admin/easypopulate_4.php(173): ep_4_check_table_column('products_descri...', 'products_short_...')
#2 /home2/cedargr4/public_html/new/admin/index.php(11): require('/home2/cedargr4...')
#3 {main}
thrown in /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php on line 625
[17-Mar-2024 10:48:29 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
--> PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php:625
Stack trace:
#0 /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php(469): ep_4_query('SHOW COLUMNS FR...')
#1 /home2/cedargr4/public_html/new/admin/easypopulate_4.php(173): ep_4_check_table_column('products_descri...', 'products_short_...')
#2 /home2/cedargr4/public_html/new/admin/index.php(11): require('/home2/cedargr4...')
#3 {main}
thrown in /home2/cedargr4/public_html/new/admin/includes/functions/extra_functions/easypopulate_4_functions.php on line 625.
Thanks. I posted the text with the admin directory changed to admin. The post hasn't posted - it said administrators have to approve it first, so I'm just waitingQuote:
Originally Posted by mc12345678
They still haven't let the post thru. If anyone can read the log pics please help.
Well, the copy that came through to me had your admin directory throughout the post. At any rate, the last message of the log indicates that you are using a version that is not fully compatible with Zahn cart 1.5.8. There are two ways to at least get really close.Quote:
Originally Posted by Fenomenal7
Either, make the two edits described over the last 15 pages or so (pretty much at least once on each page) or use the github.com version referenced within the last two pages or so.
I've been trying to get a little time to update the files associated with installing the software for the case of the temporary directory not yet existing; however, keep getting interrupted with other things. Generally speaking the updated version should work.
Unfortunately I must also figure out what the best instructions are because the new version also works as a zc_install style plugin even though there is an Ajax related file that appears must be loaded to the catalog even though the zc_install process seems to ignore catalog related code. Don't have to have the added feature, but helps those that care about attributes.
ok great, I will use use the github.com version you referenced and let ya'll know how it went. Thank you!Quote:
Originally Posted by mc12345678
Quote:
Originally Posted by mc12345678
For information, the github.com site was updated about 22 hours ago to correct the other issue that was recently identified. About an error logged when debugging is on (default) and the directory not yet existing.Quote:
Originally Posted by Fenomenal7
Besides possibly the addition of additional notifier s, in all working on a change in the way of establishing default values. Feedback, good or bad, is sordid.
Quote:
Originally Posted by mc12345678
ok. after installing I see easy pop on my tools but once again, when I click on it it says http 500 error and I can't configure or do anything with it. The error log is as follows:
[20-Mar-2024 11:37:42 America/Boise] PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/admin/includes/classes/class.query_factory_ep4.php:62
Stack trace:
#0 /home2/cedargr4/public_html/new/admin/easypopulate_4.php(28): queryFactoryEP4->getLink()
#1 /home2/cedargr4/public_html/new/admin/index.php(11): require('/home2/cedargr4...')
#2 {main}
thrown in /home2/cedargr4/public_html/new/admin/includes/classes/class.query_factory_ep4.php on line 62
[20-Mar-2024 11:37:42 America/Boise] Request URI: /new/admin/index.php?cmd=easypopulate_4, IP address: 47.219.208.101
--> PHP Fatal error: Uncaught Error: Cannot access private property queryFactory::$link in /home2/cedargr4/public_html/new/admin/includes/classes/class.query_factory_ep4.php:62
Stack trace:
#0 /home2/cedargr4/public_html/new/admin/easypopulate_4.php(28): queryFactoryEP4->getLink()
#1 /home2/cedargr4/public_html/new/admin/index.php(11): require('/home2/cedargr4...')
#2 {main}
thrown in /home2/cedargr4/public_html/new/admin/includes/classes/class.query_factory_ep4.php on line 62.
I really need to get this fixed today - been working on this for 2 weeks. I'm a novice. Can you help me 1 on 1 in the inbox?
I mean a beginner smh
I should have updated the date associated with the version but about five hours ago or less I made a change to the class file reported as the issue: admin/includes/classes/class.query_factory_ep4.phpQuote:
Originally Posted by Fenomenal7
Quote:
Originally Posted by mc12345678
That did it! Thank you :)
Zen Cart 1.5.7d
Easy Populate 4.0.36.ZC - 07-05-2016
Import/Export Primary Key set to products_id
We're trying to delete a bunch of products. The csv file consists of only'
v_products_id v_products_type v_products_name_1 v_categories_name_1 v_status
219273 1 Product Name 9
On import, I'm getting
NOT FOUND! - Model: 219273 - cant delete...
This site does not use model numbers for any products. I assumed setting the import/export key to products_id would have the import use the products_id and not model.
Interesting condition. I too would expect the deletion even though I know there are some changes in the latest version that might address/relate; however, when trying to review the 4.0.36ZC code:Quote:
Originally Posted by jeking
The appearance to me is that the result of the while condition is "falsey" causing that internal deletion to be skipped and leading to the message after the while loop indicating the product could not be found.Code:while ($row = ($ep_uses_mysqli ? mysqli_fetch_array($result) : mysql_fetch_array($result) )) { // chadd - this executes once?? why use while-loop?? $product_is_new = false; // we found products_model in database
// Get current products descriptions and categories for this model from database
// $row at present consists of current product data for above fields only (in $sql)
// since we have a row, the item already exists.
// let's check and delete it if requested
// v_status == 9 is a delete request
$continueNextRow = false;
if ($items[$filelayout['v_status']] == 9) {
$chosen_key = '';
switch (EP4_DB_FILTER_KEY) {
case 'products_model':
$chosen_key = 'v_products_model';
break;
case 'blank_new':
case 'products_id':
$chosen_key = 'v_products_id';
break;
default:
$chosen_key = 'v_products_model';
break;
}
$display_output .= sprintf(EASYPOPULATE_4_DISPLAY_RESULT_DELETED, $items[$filelayout[$chosen_key]]);
ep_4_remove_product($items[$filelayout[$chosen_key]]);
$continueNextRow = true;
}
$zco_notifier->notify('EP4_IMPORT_FILE_EARLY_ROW_PROCESSING');
if ($continueNextRow == true) {
continue 2; // short circuit - loop to next record
}
That said also, the above "file" data doesn't present what might be expected. It appears that there are only four pieces of data below the five column headers. I suspect this displayed condition is because the spreadsheet data was directly copied into this chat instead of the csv file contents. Because you are getting the error that you are, it seems one of the columns is made of non-problematic "empty" data.
It could be that the product does not have data fully across all necessary tables: Note the query.
the products_to_categories table, categories and products tables are effectively all inner joined requiring a record in all three that give at least one result when queried on the products_id. So if that product isn't in the products_to_categories table or if the categories table doesn't have a match to the products_to_categories table, then the query doesn't find any results and we get the falsey value that bypasses the attempt to delete.Code:$sql = 'SELECT p.products_id as v_products_id,
p.products_type as v_products_type,
p.products_model as v_products_model,
p.products_image as v_products_image,
p.products_price as v_products_price,';
if ($ep_supported_mods['uom'] == true) { // price UOM mod - chadd
$sql .= 'p.products_price_uom as v_products_price_uom,';
}
if ($ep_supported_mods['upc'] == true) { // UPC Code mod- chadd
$sql .= 'p.products_upc as v_products_upc,';
}
if ($ep_supported_mods['gpc'] == true) { // Google Product Category for Google Merhant Center - chadd 10-1-2011
$sql .= 'p.products_gpc as v_products_gpc,';
}
if ($ep_supported_mods['msrp'] == true) { // Manufacturer's Suggested Retail Price
$sql .= 'p.products_msrp as v_products_msrp,';
}
if ($ep_supported_mods['map'] == true) { // Manufacturer's Advertised Price
$sql .= 'p.map_enabled as v_map_enabled,';
$sql .= 'p.map_price as v_map_price,';
}
if ($ep_supported_mods['gppi'] == true) { // Group Pricing Per Item
$sql .= 'p.products_group_a_price as v_products_group_a_price,';
$sql .= 'p.products_group_b_price as v_products_group_b_price,';
$sql .= 'p.products_group_c_price as v_products_group_c_price,';
$sql .= 'p.products_group_d_price as v_products_group_d_price,';
}
if ($ep_supported_mods['excl'] == true) { // Exclusive Product Custom Mod
$sql .= 'p.products_exclusive as v_products_exclusive,';
}
$zco_notifier->notify('EP4_IMPORT_PRODUCT_DEFAULT_SELECT_FIELDS');
if (count($custom_fields) > 0) {
foreach ($custom_fields as $field) {
$sql .= 'p.' . $field . ' as v_' . $field . ',';
}
}
$sql .= 'p.products_weight as v_products_weight,
p.products_discount_type as v_products_discount_type,
p.products_discount_type_from as v_products_discount_type_from,
p.product_is_call as v_product_is_call,
p.products_sort_order as v_products_sort_order,
p.products_quantity_order_min as v_products_quantity_order_min,
p.products_quantity_order_units as v_products_quantity_order_units,
p.products_priced_by_attribute as v_products_priced_by_attribute,
p.product_is_always_free_shipping as v_product_is_always_free_shipping,
p.products_date_added as v_date_added,
p.products_date_available as v_date_avail,
p.products_tax_class_id as v_tax_class_id,
p.products_quantity as v_products_quantity,
p.products_status as v_products_status,
p.manufacturers_id as v_manufacturers_id,
p.metatags_products_name_status as v_metatags_products_name_status,
p.metatags_title_status as v_metatags_title_status,
p.metatags_model_status as v_metatags_model_status,
p.metatags_price_status as v_metatags_price_status,
p.metatags_title_tagline_status as v_metatags_title_tagline_status,
subc.categories_id as v_categories_id
FROM ' .
TABLE_PRODUCTS_TO_CATEGORIES . ' as ptoc,' .
TABLE_CATEGORIES . ' as subc,' .
TABLE_PRODUCTS . " as p ";
$zco_notifier->notify('EP4_IMPORT_PRODUCT_DEFAULT_SELECT_TABLES');
$sql .= "WHERE
p.products_id = ptoc.products_id AND
ptoc.categories_id = subc.categories_id AND ";
switch (EP4_DB_FILTER_KEY){
case 'products_model':
$sql .= "
p.products_model = :products_model:";
break;
case 'blank_new':
case 'products_id':
$sql .= "
p.products_id = :products_id:";
break;
default:
$sql .= "
p.products_model = :products_model:";
break;
}
$sql = $db->bindVars($sql, ':products_model:', $items[$filelayout['v_products_model']], 'string');
$sql = $db->bindVars($sql, ':products_id:', $items[$filelayout['v_products_id']], 'integer');
Can it, will it delete with that minimal amount of information, I would say yes and suggest reviewing the results of that query. May I suggest trying phpMyAdmin to run that query substituting the necessary data where it would be coded into the query. Again I suspect the result is 0 values returned and then need to figure out why.
Originally and only for information, I was going to question what filename is used; however, the response received indicates the file is being processed as an "everything else" file.
Thank you for the details trouble shooting and explanation.Quote:
Originally Posted by mc12345678
This is the issue, the product_id does not exist in the products_to_categories table. I can't say how the products were added, probably with Apsona. I'll write a custom query to delete the products for this client.
Much appreciated!
Alternatively the query in EP4 could be modified to support let joins for each of the tables instead of one joins. I would expect that to at least in part resolve the issue of being able to delete the product.Quote:
Originally Posted by jeking
There are multiple possible reasons of the loss of product to category relationship. Glad that were able to confirm or identify the problem with that configuration.
Please help.
Easy Populate 4.0.39.ZC, Zen Cart v1.5.7d, PHP Version 7.4
I can't import products that are in a subcategory.
Import Results
"Error: Unbalanced Categories defined in:"
Thanks.
Attachment 20556