EasyPopulate 4.0 Support Thread

[su35]

So, reviewed the code for this particular error message. It only appears as is if the category identified in the field does not exist as part of the existing category list. When you look at the CSV file using a basic text editor with just those two entries, do you see any displacement of the quotes? The same number of spaces between the first and the second listing? Have you tried copying the category from the successful one to the unsuccessful? Wondering if there might be some other character code that is not "visible" onscreen.

The other thought depends on the editor that you are using and whether it is saving the file as a proper CSV file and therefore if it is not, then when uploaded for import it is not understanding the line of information properly. Just some basic thoughts.

Thanks mc12345678
However, after deleted almost everything, I got the same result. I had dumped the $categories_name_exists on screen, it was null.

[mc12345678]

Thanks mc12345678
However, after deleted almost everything, I got the same result. I had dumped the $categories_name_exists on screen, it was null.

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. :/

[laquilino68]

can you tell me what the longest field length is for the "v_products_description_1" field is?

Thank you kindly in advance!

[linuxguy2]

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.

[100asa]

where I can download this 4.0 version?

[mc12345678]

where I can download this 4.0 version?

Please see the first post of the thread.

[mc12345678]

can you tell me what the longest field length is for the "v_products_description_1" field is?

Thank you kindly in advance!

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.

[chadderuski]

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.

Hi All! No, I did not fall off the planet

EP4 does NOT limit field lengths, but it does check the database to see what the size of the fields are and gives you a warning/error message if you go over that length.

I believe that non-critical data gives a warning, but something like a category name generate an error and does not add that record. This is necessary especially when creating category names, or even manufacturer names. With out it, a name the exceeds the length in the database would be truncated and added multiple times (there would be not match when comparing values). Other versions of EP don't do this unless they've fixed it recently.

Multi-byte encoded languages are a bit harder to work with, but should function correctly.

-chadd

[any_way]

no solution mc123456... relating to my post on 08/24/2013

please answer with a simple yes or no.

[mc12345678]

hello chadd,

your plugin works fine, is it possible to add "v_products_name" to export file "Model/Price/Qty"?

Output "Model/Price/Qty" like this example:

v_products_model,v_products_name,v_status,v_specials_price,v_specials_date_avail ,v_specials_expires_date,v_products_price,v_products_quantity

no solution mc123456... relating to my post on 08/24/2013

please answer with a simple yes or no.

Wow... My apologies. I can generate a solution. Not a difficult add in, at least if just want to have the data displayed on the screen. If want the program to use the data, that may take a little more. Below is the changes to show the products name (multilingual potential) for the product model being discussed when doing price quantity discounts. It does not necessarily import that data back into the database. (Haven't looked through the import code, nor did I see that it was expected to import the name.) So this is just for user benefit when updating the other fields.

In admin/includes/functions/extra_functions/easypopulate_4_functions.php

Main code section: function ep_4_set_filelayout

At the case for priceqty: (Add the foreach statement after the first $filelayout and before the next $filelayout... This forces the name to be after the model...)

 case 'priceqty':
  $filelayout[] = 'v_products_model';
  foreach ($langcode as $key => $lang) { // create variables for each language id
   $l_id = $lang['id'];
   $filelayout[] = 'v_products_name_'.$l_id;
  }   
  $filelayout[] = 'v_status'; // 11-23-2010 added product status to price quantity option 

in admin/easypopulate_4_export.php find the end of the 'full' routine as shown below, insert the text in red (oops, used php tags... There is no custom coloring for PHP tags so the code area as described) before the //BEGIN: Specials. (This just happens to be a convenient location and is not required to be at that specific point in the code. There is an area lower in the code that addresses the calculations of the priceqty discount; however, after quickly coding this, it seemed like this area still may be preferred. The lower area is heavy in math and affects of performing a discount and not so much in the other "random" data to be exported.

  } // if($ep_dltype == 'full')

  if ($ep_dltype == 'priceqty') {
   foreach ($langcode as $key => $lang) {
    $lid = $lang['id'];
    $sql2    = 'SELECT * FROM '.TABLE_PRODUCTS_DESCRIPTION.' WHERE products_id = '.$row['v_products_id'].' AND language_id = '.$lid.' LIMIT 1 ';
    $result2 = ep_4_query($sql2);
    $row2    = mysql_fetch_array($result2);
    $row['v_products_name_'.$lid]        = $row2['products_name'];
   } // end foreach $langcode
  } //end if ($ep_dltype == 'priceqty')

  // BEGIN: Specials