I am assuming that the correct variable was used for the screen dump, would expect it to not be a "true" value because the error message is displayed. It would be more important to track backwards and see if a value was provided at all for the category and other information to see where/when it "lost" the name.
I haven't used NotePad++, I see that there are no quotes around the text in the string. This could be a problem. I'm not sure that it is causing your problem. Also, considering how much has been removed, there is little that could/would get in the way. I haven't counted the commas, but hope that the right data got to the right place. (BTW, unless you have corrected it, I think that the lack of description used in this upload will cause your description to be erased for that/those models.. )
I'm trying to help, but this is a really odd situation that it is not working for a few cases... :/ If you only have model 64636 in a file, will it add it? (I'm thinking no because the failed row is before the successful row. ) I'm trying to think how to help without having a copy of the file causing the problem. :/
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
can you tell me what the longest field length is for the "v_products_description_1" field is?
Thank you kindly in advance!
Thanks for the GREAT plugin. Seems to work ok just need to do more testing in my particular store.
This is an operational nit with oo and Excel but may save some a lot of time.
If you Creating a part name (or any other entry in zc) with a leading zero, as in "078453M" when editing in oo or Excel you must set the appropriate column to "text" .
To do this after you DOWNLOAD the *.cvs file on your local machine first rename it with a *.txt extension before opening with Excel or oo.
When opening file you have the opportunity to change the "General" type to "Text" which you must do for columns you want to retain the leading zero(s) in.
Save as a *.txt file then rename to *.cvs before uploading and Viola! you will retain the leading zero(s)
To do this when you create a NEW *.cvs file on your local machine first save it with a *.txt extension change the "General" type to "Text" for columns you want to retain the leading zero(s) in.
Save as a *.txt file then rename to *.cvs before uploading and Viola! you will retain the leading zero(s)
You can use this special naming convention to group different product lines etc.. in applications like zc and QuickBooks.
where I can download this 4.0 version?
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
After more testing I discovered easypopulate-4.0-master (configuration part) cannot be installed AFTER fec.
Something to do with the database fields not matching (Haven't narrowed it down)
My work around was to install ep-4 first and then css_js_loader & fec.
This seems to work on a fresh install (classic template).
I am loading 4 other modules so I'll report back if I have success (or failure) on my full blown site.
What tables does Fast Easy Checkout (fec) modify? The configuration script for EP4 appears to only use the default number of columns for table insertion, without directly assigning a field to a value. If EP4 fails after fec, what else will fail after fec installation? I am assuming that the failure occurs when clicking the link at the top of the screen upon first time upload. Otherwise, where in the process does it stop (error log?). What version of ZC did you try this on? EP4 should not be affected by nor affect either of those two plugins, unless one of those two changes the tables in a way that is unrecognizable...
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
I had a working installation of ep-4. (Installed ep-4 first then css_js_loader & fec) uninstalled ep-4 from the admin menu "Tools - EP - Uninstall" and then tried to reinstall it from the same screen (see graphic) and below is the error I got. Where would I look for a more detailed error report?
WARNING: An Error occurred, please refresh the page and try again.
Attachment 13509
From what I have been able to gather, there is nothing about EP4 that specifically limits the length of the field. The field is a text field in the database, the applicable editor may have some limitations or maybe a function that is called, but EP4 doesn't truncate the field length of the description, regardless of the language.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...