EasyPopulate 4.0 Support Thread

[mc12345678]

All of what you said has happened. I have browsed for the correctly set up test csv file. Uploaded it with the upload button.
The browsed for file then appeared next to the browse button. Next to the browse button is the upload button. I then click that. Momentarily after that.... A message appears at the top of the page saying file uploaded successfully. THEN... I did see the import button at the bottom of the screen. I click that. A message immediately appears at the top of the page stating - file imported successfully. I then go to "online catalog" and nothing is there!

Are you saying that I should download one of the default data files that EP puts out....put my data in it and then re-up load it.... Then it will populate. I know..... you are allowed to scream at me if you want.... But I don't get it... Could someone just look at it for me please.....

Humbly submitted,
Brenda

No hootin' and hollarin' going on over here, except for the typical Saturday shenanigans. Your second paragraph sums it up exactly. You can add more to the filename if you wish to not replace the previous file and still have it available if a mistake is made.

Additionally, for the first one or two, recommend not adding fields to the file(s) until seems to work. (Ie. One step at a time. )

[jrobbo]

I've been using EP4 for a while now, great utility.

I've just uploaded a new line of products where the quantity is implied, and so I want to turn the off the Quantity box in the product listing. Is there a way to toggle the Products Quantity Box Shows option in the products listing using EP4?

Many thanks for any suggestions

John

[mc12345678]

I've been using EP4 for a while now, great utility.

I've just uploaded a new line of products where the quantity is implied, and so I want to turn the off the Quantity box in the product listing. Is there a way to toggle the Products Quantity Box Shows option in the products listing using EP4?

Many thanks for any suggestions

John

Not by default, but it is easy to add...

In the admin->configuration->Easy Populate 4 there is a field (User defined products fields) to add additional fields for export/import. Fields associated with the products table can be added into this list. The fields should be identified as they appear in the products table separated by commas only (for more than one field). So for this case, if the products_qty_box_status field is listed then when it is set to zero (0) it appears that the option to choose a quantity for a product will be prevented.

One of those things that not everyone uses, so it seems that it was left off as a default like option, but is something still possible.

[jrobbo]

Well that turned out to be a whole lot easier than I thought it was going to be! Thanks very much @mc123456578 for the excellent reply, works like a charm.

Cheers

John

[mc12345678]

Well that turned out to be a whole lot easier than I thought it was going to be! Thanks very much @mc123456578 for the excellent reply, works like a charm.

Cheers

John

Quite welcome, wouldn't have been possible without the rework done by chadderuski, all of the feedback of the users and the work of those leading up to this. :)

[johnniejetski]

looking at installing this, hoping to bring 1.3.9 products into a 1.5.3 store. Is there a summary of the steps or do I need to read 169 pages ?

[mc12345678]

looking at installing this, hoping to bring 1.3.9 products into a 1.5.3 store. Is there a summary of the steps or do I need to read 169 pages ?

On a quick search, this is something I found, but if you still have the 1.3.9 database, then there is a zc process to import products other than using EP4 to import. It will work, but may not be the preferred method. http://www.zen-cart.com/showthread.p...47#post1251347

There's other occurrences of such a summary; however, I have not given the search time to find it...

[citapinc]

One of those things that not everyone uses, so it seems that it was left off as a default like option, but is something still possible.

I've always written my import routines to show all fields and let the user determine which field they don't want to import. Most users who use import tools like this are your more advanced users who have an understanding of what fields are and how to remove them off the CSV file if not needed.

Therefore I'd rather see ALL fields in the CSV file than MOST USED fields.

[mc12345678]

I've always written my import routines to show all fields and let the user determine which field they don't want to import. Most users who use import tools like this are your more advanced users who have an understanding of what fields are and how to remove them off the CSV file if not needed.

Therefore I'd rather see ALL fields in the CSV file than MOST USED fields.

So I believe that it was this aspect that was considered by the original author/rewriter (chadder) in that the option to add fields was made available through the configuration menu... It has also been identified by some that export (well seems to have been more of an import issue) of all fields regardless of "desire" takes additional time, space, and effort to remove the undesired option(s)...

There is also the level of support aspect to be provided when/if all fields are exported and the issues involved with making changes and then importing them again... For example, while I'm about to release a version that will work off of products_id, there is little that can be offered as error buffers to prevent someone from mangling their database... Backup before uploading... That's about the most that can be offered... Or at least at the moment the most that I can offer on a volunteer basis...

Yes, up front the products table could be evaluated on each export and all fields added to the export file... The entire database could be so processed, but is that what is needed? Or are things like that needed by the few that either can modify the code to accomplish the desired task or seek assistance to make it happen? As I said more than 2 years ago, EP4 is so adaptable and compartmentalized enough that either one compartment can be modified to obtain the desired results or duplicated to provide the modified results... There are still a few minor things to work out, but it is quite a power house... I've also been thinking about how chadder and I can work the instructions a little more in favor of a "I want to do this" type style rather than a this is how this feature works style... Reason? Well look at the number of times that the filename has been an issue in the last several pages... It's in the instructions (limited that they are), but I have refrained from going that short of a response...

Afterall, someone identified that there was an issue with specials when this code was run on PHP 5.6 I think it was because of the way dates were handled on import... That was good feedback and would like to see issues like that identified more publicly as I had to dig to find that someone had identified that problem... There have been things added based on others needs and inquiries, but I do have a concern of adding too many/too many more switches to support "branches"... I'm beginning to consider adding notifiers and observers so that various "features" can be added through file uploads instead... More to contemplate on that one though..

[outeredge2]

Is there a sample file floating around that I could use to start putting together my products list?