EasyPopulate 4.0 Support Thread

linuxguy2:

The verion I like best is EasyPopulate 4.0
Google "EasyPopulate 4.0" and go to the "EasyPopulate V4 - Zen Cart® Plugins and Addons" link.

Or search "ep4" on the plugins page.

Glad you like it and yes the search will reveal the links provided as well as some other related software. The links (or reference to the first post) are all related to the same software.

After my last posting, I confirmed that the location identified in the first post is the same version as distributed by ZC download.

Because of the observed popularity of the plugin and the reference provided in the first post, I had spoken with chadder about how to proceed with revisions. We decided to leave the known location identified as it was, to keep it up-to-date and to independently generate modifications to not disrupt either of those two.

Hey MC!

Way back on post #2800, you mentioned adding the ability to export category paths for informational purposes. Then, in the very next post, I was able to find some code on github to get that working.

It was extremely useful to me and, now that I'm building a new site, I'd really like to add that ability in to my EP4 install. Sadly, I cannot seem to find that modification on github anymore.
:(

Any chance you could remind where to find that?

Btw, I have a ZC154e with Easy Populate 4.0.36.ZC - 07-05-2016 installed.

Feznizzle:

Hey MC!

Way back on post #2800, you mentioned adding the ability to export category paths for informational purposes. Then, in the very next post, I was able to find some code on github to get that working.

It was extremely useful to me and, now that I'm building a new site, I'd really like to add that ability in to my EP4 install. Sadly, I cannot seem to find that modification on github anymore.
:(

Any chance you could remind where to find that?

Btw, I have a ZC154e with Easy Populate 4.0.36.ZC - 07-05-2016 installed.

Well, I was doing some github "cleanup". In my opinion, there were too many branches and too many side things that either were or should have been in the master thread or should have been consolidated to apply to a single change instead of a spelling change here, a thing there, etc... If you need the specific change that was incorporated into the master thread: https://github.com/mc12345678/EasyPopulate-4.0/commit/3a2dbe8be704271486d8bcc4069cd7cb277f28d0

Otherwise, there are some other feature modifications and changes being applied (take a look at the Insights->Network to see sequencing and plan for incorporating) but only into the master thread once confirmed functional/non-disfunctional. Working towards issuing a new version based on some of the things pointed out here and some always wished were present features.

First, HUGE THANKS! Awesome as always, thanks MC.

Second, I tried to check out Insights->Network but found nothing there. Thought maybe it was because I was looking at your fork, so I backed up and checked the other fork, still no dice.

Feznizzle:

First, HUGE THANKS! Awesome as always, thanks MC.

Second, I tried to check out Insights->Network but found nothing there. Thought maybe it was because I was looking at your fork, so I backed up and checked the other fork, still no dice.

Trying not to read anything into the "second". Ie. Did the direct link help get the functionality back that was desired? Perhaps - also under-expressed use of the insight->network portion. May I recommend taking your mouse cursor over areas such as the black dots on any line. Perhaps clicking on one to see what happens. Explore a little more. :) I know, have a job to finish. Be sure to stop and smell the roses once in a while. :)

Yes, your direct link to the code was enough to get the desired functionality working. I was able to export category paths, no problem. Again, thanks.

I guess I'll let the Insights->Network go? I thought you guys were working on "other feature modifications and changes being applied" and you were inviting me to take a look at the plan. To see it, I was supposed to go to the github page for Easypop, click on Insights, then click on Network.

I did that, but found nothing and/or did not understand what I was looking at.

Here are two screenshots to show you what I could see:

.
.
.
.
.
.
.

Unfortunately the "map" of the network didn't come through on those screen shots, but the previous links took me to where I expected you to be and I would guess the lack of the map image is something related to github and screen capture. Regardless, yes the thought was to offer a sort of way to see the upcoming direction(s) of the plugin. Each dot on the line represents a saved change. There is a description that displays when hovering over the dot. Clicking on the dot opens a new window and takes you to the specific commit (change) that was made where you can see both the description, any comments, and the specific code changes to support that change.

Previously I believe you had been able to find that specific change because I had created a separate branch the name of which clearly described the intended change. That branch had multiple commits in it (more than one file was modified and modifications were done online instead of from a computer where more control can be had on how the changes get saved). All of those changes were summarized into the one commit to which I directed you. It can be found in the "dots" before the end of master.

Another reason to send to the network is because there are multiple little branches that I ended up stacking into a single chain. I expect that I will be able to confirm each chain off of the master one by one and then merge that change directly into the master branch. Thus, if you were to go to the last branch, you would see how the software is expected to be configured to reflect as if all changes were incorporated. I have thought of a few changes made that I want to let up on to support how others have likely built off of EP4 and not require them to make changes in support of some upcoming export features. Plus I haven't completed the matching import changes to some of that, so they may get bumped a little. Doesn't do a lot of good if can't import what has been exported. :)

So ignore or not, can do either. I know there was a date related issue that you had identified and I at least attempted to correct, though I'm still testing import aspects (having to be sure I have a backup/restore path for the database before doing that).

Sorry for removing that branch, but like I said was getting too "busy" for my tastes and management of ensuring nothing was left off/out.

MC, I'm always supper grateful for the work you do on this mod. So no worries about killing that branch!

I now have a copy of it on my computer. If the category-path export doesn't make it into a future update, I should be able to just slip into my own install using what I now have.

Btw, I opened github in a dif browser and the info you where alluding to popped right up. Sorry about that, sometimes I forget that my dev browser is stripped down!

mc12345678:

The location shown in the first post of this thread has generally been kept up with the official current release. However, that said, there is the version that was released to/through ZC available for download here. Updates, new features, etc. Are worked on/distributed through github here. The thing about that version is that the software version tends not to be updated until near submission to ZC so database changes made in it may not appear to need installing until later.

Further, that said, some new features and modifications are being incorporated as they are identified as successful for operation. There are a few branches each with some different features to be verified and incorporated. Perhaps the most innovative is the identification of the csv delimiter and the potential use of the discovery. It is still limited to a base set of delimiters, but at least easier to work with other than the base CSV (Comma Separated Values).

Anyways, hope that helps.

Thanks for that info!

mc12345678:

Glad you like it and yes the search will reveal the links provided as well as some other related software. The links (or reference to the first post) are all related to the same software.

After my last posting, I confirmed that the location identified in the first post is the same version as distributed by ZC download.

Because of the observed popularity of the plugin and the reference provided in the first post, I had spoken with chadder about how to proceed with revisions. We decided to leave the known location identified as it was, to keep it up-to-date and to independently generate modifications to not disrupt either of those two.

Thank you both. I guess I'm not entirely sure which link to use. I will go with ep4 and look for that link in google. I just need to be able to export products from one cart and import them into another. Thanks again!

cindygordon:

Thank you both. I guess I'm not entirely sure which link to use. I will go with ep4 and look for that link in google. I just need to be able to export products from one cart and import them into another. Thanks again!

It says "beta" but I'll give it a go!

cindygordon:

Thank you both. I guess I'm not entirely sure which link to use. I will go with ep4 and look for that link in google. I just need to be able to export products from one cart and import them into another. Thanks again!
Couple things about this. Currently language specifiers are by an internal language_id instead or something "more useful" like a language code. So if the source database has previously had a language installed and then removed but the destination has only had the one language then they may have different field identifiers. I'm working on modifying that capability to import using either method with preference of one of them.

The other thing of "concern" is what makes the product unique between the two stores and what issues might pop up by merging the two databases instead of uniquely populating the "new" database.

Thanks for a great plugin, I've been using it for years. Recently, I've started merging my shops together and have downloaded a complete csv from "Shop S" to upload to the new "Shop B". I was getting the model number error, which I resolved by simply putting in numbers (I didn't use model numbers in Shop S but DO in the new Shop B). However, now when I import the csv file it imports nothing and there are no errors. I've been searching for an answer but have not found one.

I am using ZC 1.5.5e for Shop B (clean install of both) and 1.5.5a for Shop S (EP update from 4.0.35).
Both shops use Easy Populate 4.0.36.ZC - 07-05-2016 and run PHP Version 5.6.31.

What other information can I provide that would help you to help me? Thanks so much.

townsend2009:

Thanks for a great plugin, I've been using it for years. Recently, I've started merging my shops together and have downloaded a complete csv from "Shop S" to upload to the new "Shop B". I was getting the model number error, which I resolved by simply putting in numbers (I didn't use model numbers in Shop S but DO in the new Shop B). However, now when I import the csv file it imports nothing and there are no errors. I've been searching for an answer but have not found one.

I am using ZC 1.5.5e for Shop B (clean install of both) and 1.5.5a for Shop S (EP update from 4.0.35).
Both shops use Easy Populate 4.0.36.ZC - 07-05-2016 and run PHP Version 5.6.31.

What other information can I provide that would help you to help me? Thanks so much.
If you export a product/category (of products) from Shop B, how do the headings differ from Shop S? Ie. Wondering if the language identifier _X is a factor.

Based on the description of the issue it sounds as if the primary key remains the model # (would otherwise use blank_new to create new product in the new database).

Are you also sure that the chosen model number doesn't already exist and instead of adding product that product is being updated? After import, there should be some level of information provided at the bottom of the screen or else the debug.txt file should contain something.

Hey All!

Just a few quick question:

1. With the .htaccess file to edit for "(csv|CSV|txt|TXT)". Admin or elsewhere?

2. I have the admin .htaccess ready to edit, but unsure which portion of that file contents to add my my existing .htacess file.

3. With Custom Product Fields; the MSRP is in green text - how would I obtain any others if needed?

EG: Custom Products Fields
Product Short Descriptions: FALSE
Product Unit of Measure: FALSE
Product UPC Code: FALSE
Google Product Category: FALSE
Manufacturer's Suggested Retail Price: TRUE
Manufacturer's Advertised Price: FALSE
Group Pricing Per Item: FALSE
Exclusive Products Mod: FALSE
Stock By Attributes Mod: FALSE
CEON URI Rewriter Mod: FALSE
Dual Pricing Mod: FALSE

Any assistance would be greatly appreciated.

AnthonyEnnis:

Hey All!

Just a few quick question:

1. With the .htaccess file to edit for "(csv|CSV|txt|TXT)". Admin or elsewhere?

2. I have the admin .htaccess ready to edit, but unsure which portion of that file contents to add my my existing .htacess file.

3. With Custom Product Fields; the MSRP is in green text - how would I obtain any others if needed?

EG: Custom Products Fields
Product Short Descriptions: FALSE
Product Unit of Measure: FALSE
Product UPC Code: FALSE
Google Product Category: FALSE
Manufacturer's Suggested Retail Price: TRUE
Manufacturer's Advertised Price: FALSE
Group Pricing Per Item: FALSE
Exclusive Products Mod: FALSE
Stock By Attributes Mod: FALSE
CEON URI Rewriter Mod: FALSE
Dual Pricing Mod: FALSE

Any assistance would be greatly appreciated.

1. File for csv/txt as provided in the download is only needed to "override" an htaccess file in a folder above that does not already allow csv/txt file downloads. Basically, if you are going to store your import/export files in a sub-directory of the admin, then the file needs to be in that sub-directory.

2.unless you are putting your files directly in the admin directory (instead of as suggested above to put them in a sub-directory), there is no reason to alter the admin/.htaccess file. In fact if the files are stored on the catalog side in a sub-directory, there wouldn't be a need for an htaccess there either for a vanilla install, although would still suggest having one for security purposes. Basically, the point is, there is no reason to open all sub-directories of the admin folder to support csv/txt files when they are only to be in a specific location.

3. The fields in green have specifically been included by previous knowledge/experience. They turn green when the expected "rule" is found. To add additional products table fields, go to the configuration window for EP4 and edit the custom field data entry section. As described in the instructions provide the database field name(s) separated by a comma.

mc12345678:

1. File for csv/txt as provided in the download is only needed to "override" an htaccess file in a folder above that does not already allow csv/txt file downloads. Basically, if you are going to store your import/export files in a sub-directory of the admin, then the file needs to be in that sub-directory.

2.unless you are putting your files directly in the admin directory (instead of as suggested above to put them in a sub-directory), there is no reason to alter the admin/.htaccess file. In fact if the files are stored on the catalog side in a sub-directory, there wouldn't be a need for an htaccess there either for a vanilla install, although would still suggest having one for security purposes. Basically, the point is, there is no reason to open all sub-directories of the admin folder to support csv/txt files when they are only to be in a specific location.

3. The fields in green have specifically been included by previous knowledge/experience. They turn green when the expected "rule" is found. To add additional products table fields, go to the configuration window for EP4 and edit the custom field data entry section. As described in the instructions provide the database field name(s) separated by a comma.

Sorry, I don't follow #1 & 2.

I believe the files are in the catalog, I have replaced the htaccess file in the catalog and replaced it with the one from the installation file. This caused my admin issues.

I'm also not sure what you mean by 'above folder'.

Thanks for replying, I truly appreciate it.

AnthonyEnnis:

Sorry, I don't follow #1 & 2.

I believe the files are in the catalog, I have replaced the htaccess file in the catalog and replaced it with the one from the installation file. This caused my admin issues.

I'm also not sure what you mean by 'above folder'.

Thanks for replying, I truly appreciate it.
Ok. So let's back up and start over.

EP4 has been installed.
Where is the directory to which uploaded files and exported data is stored? Is it in the admin or off of the catalog? (there is setting in the configuration that identifies using the admin side or not. Then a separate field to be populated with the path to the storage location.)

The htaccess file that was provided in the download was for the sub-directory to be used that is/was in the admin directory.

If this path is to the import/export storage location: /my/srvr/public_html/my_folder

Then the folder above would be:
/my/srvr/public_html

ZC does not provide an htaccess file for the catalog side specifically. (sub-folders such as images, extras, etc... yes but not the catalog folder). So are you saying that all of the csv files are being exported/improted from the root of your store and not in a separate potentially protected sub-folder?

I do have a question, I see a column says "Delete" if I click delete will that remove the everything from the Database or just remove that file from the list? Need to clean out the list.

wmorris:

I do have a question, I see a column says "Delete" if I click delete will that remove the everything from the Database or just remove that file from the list? Need to clean out the list.

When looking at the tools->Easy Populate V4 admin screen, in the "lower" area showing a list of files, the delete button there relates to just the file itself and nothing about the contents. Be advised that at this time, there is no "are you sure" question when selecting that button. The file is simply deleted.

Also, because the list is generated from what is present, if you have some reason to keep the files, then taking them out of the EP4 directory will shorten the list, but will still require storage and some future review for removal. :)