EasyPopulate 4.0 Support Thread

[icecold]

This a sample csv I just exported from the site

v_products_price v_products_msrp
35 35
0 0
25 25
99 99
38 38
65 65
20 20
45 45
45 45

Those are the fields I am getting but for some reason my imported file didn't make any differences between the MSRP and the other price, I am having another problem, as no prices are displayed ...
please take a look at my demo store

http://www.theoutletseason.com/demostore

You will notice no prices are displayed!
I don't know if this has to do with the way I entered them into the csv and then imported them into the site, or something else ...

[mc12345678]

This a sample csv I just exported from the site



Those are the fields I am getting but for some reason my imported file didn't make any differences between the MSRP and the other price, I am having another problem, as no prices are displayed ...
please take a look at my demo store

http://www.theoutletseason.com/demostore

You will notice no prices are displayed!
I don't know if this has to do with the way I entered them into the csv and then imported them into the site, or something else ...

So, couple of questions, did the msrp work before trying to use EP4 to update it? If you either add a new product or modify an existing one, will the price appear?

Currently when viewing the source code of a page, the following is displayed:

<!--bof Product Price block -->
<h2 id="productPrices" class="productGeneral">
</h2>
<!--eof Product Price block -->

This indicates that nothing is being generated between the h2 tags. Perhaps a coding issue from installing the mod? Any error logs?

After adding a product to the cart, the cart does show a price. I was trying to look to see what, if any settings could have been changed to hide the price even on the product page, but haven't been able to validate that anyone (or combination of settings) would hide the price on all pages except the cart. There's options in the product listing. And I recall some under product type also, but...

At the moment, and without further pre_EP4 install/update information, couldn't tell you what went wrong, but generally speaking it seems that this really isn't an EP4 issue anymore at the moment. I say this because at least the one field (and there may be others) does export and am guessing will import as well, but that either bad data is being provided to the database or the module installation has an error. If it is a case tht this is not an EP4 specific issue, may I recommend posting to the thread about MSRP or starting a new thread to address this issue. Again, so far it appears that MSRP doesn't work based on the information provided.

[icecold]

That's weird because there are no error logs and I have the same conclusion as you, that's an empty h2 tag, and there's nothing there ...
As i had a pretty much test installation, I did copy the core files from the mod ... however I did fix one by myself because there was a function without an ending } ...

Other than there were no modifications to the core files ...
nothing except for the template to prevent both right and left columns from displaying and a few changes in my mega menus to add more columns ... but core files supposed to be untouched so I felt safe just replacing them ...

However I think there might be something wrong with that module, although I couldn't see anyone complaining about what I found ...

[Vix332]

Hi,
I am struggling with how to use easy populate and wondered if there are some online tutorials or a wiki like there was for the older versions of Easy Populate?
Thanks
Vix

[mc12345678]

Hi,
I am struggling with how to use easy populate and wondered if there are some online tutorials or a wiki like there was for the older versions of Easy Populate?
Thanks
Vix

There's a lot inthis thread if you work your way backwards from here. Also, from what I understand the "old" wiki's/FAQ's make reference to "instructions" for this version, though they are not highly detailed. What seems to be the issue?

[mc12345678]

Hi,
I am struggling with how to use easy populate and wondered if there are some online tutorials or a wiki like there was for the older versions of Easy Populate?
Thanks
Vix

There's a lot inthis thread if you work your way backwards from here. Also, from what I understand the "old" wiki's/FAQ's make reference to "instructions" for this version, though they are not highly detailed. What seems to be the issue?

Linuxguy2 had posted the following in this thread related to the instructions:
http://www.zen-cart.com/showthread.p...60#post1236860

[Bikerstuff]

I've read the Wiki but not sure about some things.

If I already have the products in my store and I just want to update prices and stock levels but not change anything else, what all fields are required to be used?

Item #, Price, quantity, if I just import those three fields, since the item number already exists on the site, will they be found and updated, but leave all other info as is?

Some-one mentioned I think that if the description field was empty it may delete the description from the item, what about if that field just does not exist?

I read that I can Delete items in bulk by using 9 in the status field. So 0 is inactive, 1 is active, and 9 will delete?
Is that correct?

What if I do not use a status field in the import? Will all the items remain as I have them already set, and ZC just set the status based on stock levels?

I have about 2,000 items available, but only want to deal with about 500 for now. The problem I have though is when I get a CVS from supplier I can choose what fields it contains, but ALL products will be included.

I'm trying to figure the best way to deal with with only 500 of 2,000 items.

[mc12345678]

I've read the Wiki but not sure about some things.

If I already have the products in my store and I just want to update prices and stock levels but not change anything else, what all fields are required to be used?

Item #, Price, quantity, if I just import those three fields, since the item number already exists on the site, will they be found and updated, but leave all other info as is?

Some-one mentioned I think that if the description field was empty it may delete the description from the item, what about if that field just does not exist?

I read that I can Delete items in bulk by using 9 in the status field. So 0 is inactive, 1 is active, and 9 will delete?
Is that correct?

What if I do not use a status field in the import? Will all the items remain as I have them already set, and ZC just set the status based on stock levels?

I have about 2,000 items available, but only want to deal with about 500 for now. The problem I have though is when I get a CVS from supplier I can choose what fields it contains, but ALL products will be included.

I'm trying to figure the best way to deal with with only 500 of 2,000 items.

First things first, EP4 uses the model # (not the product_id) to associate a record in the file with a record in the database. So that is one of the "mandatory" fields to be included.

Regarding the description, well the code is written so that regardless of the presence of the description field in the csv file an array field is established and then when the file is imported, if data is available to be imported to that field then it is updated to that data, if the data is not available then it is set to null. This is something that is likely to be corrected in the next release.

Next to discuss, keeping a field's header (column title) but emptying the contents below it is equivalent typically to importing a null or zero or blank entry. If the desire is not to import the contents of a column, then typically the column in it's entirety is to be deleted. (Note again, the description field is currently one that should stay unless it is desired to clear the description field of every imported product.)

I really wish I could tell you from here if/what the other required fields are, but basically there are those to match the entry with the database and then there is the fact that EP4 was coded to always consider the description as a part of the import (of the full product csv file). It appears that there was not a consideration that the description field would not be included, which generally speaking is a reasonable expectation.

Btw, the previous occurrence of the description issue was one where the description field was completely removed not left empty, this issue was then confirmed through a code review.

For columns that are not mandatory and are omitted the data of the field will remain as was. Regarding changing the quantity of an item and it's relationship to the active status, it is known that simply increasing the available quantity does not activate the product. So if the desire is to simultaneously increase and reactivate the product then the status must also be included.

If I understand correctly, your supplier will provide a file with approx. 2000 items, but you only want to have your store display approx 500 of those items/be updated to reflect the data of those items. Basically if you leave off the status column (provided that at some point/somehow "deleted" products are in some way inactivated).

The questions asked above, I would agree are not likely in the wiki, and in a way not likely to totally be addressed in future primary documentation. They are good questions, but in my opinion are more about day-to-day operation than limitations, capabilities, etc...

Ideally, as in so many other situations, I would recommend that you find the method of update that is quickest for you by use of a test store, backing up the data, attempt the import of your data file and verify that the operation is successful, if not then restore, make the desired changes to the import file and try again. :) once the right combination of items is identified, then try to make it so that the process can be easily/quickly repeated. :) hope that helps a little.

[Bikerstuff]

Thank you. Yes that does help allot!

I have a local test store set up now so that I can experiment.

I think I may have thought of a way to do what I want then, with your help Thanks!.

If I import all items to a category called "Everything" and that full import has status set to 0 then all items would be updated but hidden (I think)
Then if I import a second CVS of just the items I want to sell, status 1 for these, and include the description so it's not deleted, I would make active for sale only the items I want and they should be updated. I would of course need some fields like category in this second CVS so that the items are linked from the "Everything" category to the ones they belong in.

Does that sound about right and any bad side effects I may not be knowing about? Like to the database or anything?

Oh, I am using Easy Populate 4 and Zencart 1.5.1

I will go experiment some more again now.

[mc12345678]

Hey everyone, I know that there have been a few that have had problems using EP4 when it comes to not wanting to deal with the product description. So, I finally sat down and worked through the code myself and here is a solution that works with the current version (v4.022) available from the first post of this thread, and soon to be available in the fork of the code that I have made. In the mean time, if you modify the import file that is located in the admin directory:

ROOT_OF_STORE/admin/easypopulate_4_import.php

Find the code that includes:

            // BEGIN: Products Descriptions
...
...
...
            } // END: Products Descriptions End

            // BEGIN: Products Descriptions
            // the following is common in both the updating an existing product and creating a new product
            if (isset($v_products_name)) {
                foreach ($v_products_name as $key => $name) {
                    $sql = "SELECT * FROM " . TABLE_PRODUCTS_DESCRIPTION . " WHERE
                        products_id = " . $v_products_id . " AND
                        language_id = " . $key;
                    $result = ep_4_query($sql);

                    if (mysql_num_rows($result) == 0) {
                        $sql = "INSERT INTO " . TABLE_PRODUCTS_DESCRIPTION . " (
                            products_id,
                            language_id,
                            products_name, " .
                            ((isset($filelayout['v_products_description_' . $key]) || ( isset($filelayout['v_products_description_' . $key]) && $product_is_new) ) ? " products_description," : "");
                        if ($ep_supported_mods['psd'] == true) {
                            $sql .= " products_short_desc,";
                        }
                        $sql .= " products_url )
                            VALUES (
                            '" . $v_products_id . "',
                            " . $key . ",
                            '" . addslashes($name) . "', " .
                            ((isset($filelayout['v_products_description_' . $key]) || ( isset($filelayout['v_products_description_' . $key]) && $product_is_new) ) ? "'" . addslashes($v_products_description[$key]) . "'," : "");
                        if ($ep_supported_mods['psd'] == true) {
                            $sql .= "'" . addslashes($v_products_short_desc[$key]) . "',";
                        }
                        $sql .= "'" . addslashes($v_products_url[$key]) . "')";
                        $result = ep_4_query($sql);
                    } else { // already in the description, update it
                        $sql = "UPDATE ".TABLE_PRODUCTS_DESCRIPTION." SET
       products_name        ='".addslashes($name)."', " .
                            ((isset($filelayout['v_products_description_' . $key]) || ( isset($filelayout['v_products_description_' . $key]) && $product_is_new) ) ? "products_description ='" . addslashes($v_products_description[$key]) . "'," : "");
                        if ($ep_supported_mods['psd'] == true) {
                            $sql .= " products_short_desc = '" . addslashes($v_products_short_desc[$key]) . "',";
                        }
                        $sql .= " products_url='" . addslashes($v_products_url[$key]) . "'
       WHERE products_id = '" . $v_products_id . "' AND language_id = '" . $key . "'";
                        $result = ep_4_query($sql);
                    }
                }
            } // END: Products Descriptions End

I tested this with an update of a single record. Perhaps some confirmation of functionality?
The product_name is still an attribute that should remain. This targets the import of files that do not have the following prefixes: categorymeta-ep nor attrib-. If the file(s) have that prefix then the above code will not be processed.