EasyPopulate 4.0 Support Thread

[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?

[mc12345678]

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

Not to be smart, but if you export your products list you'll have your own personal sample file... (Covered in instructions on how to use and learn to use the program)

[outeredge2]

Not to be smart, but if you export your products list you'll have your own personal sample file... (Covered in instructions on how to use and learn to use the program)

Not being smart at all..... I appreciate the response. Will look for it.

Question:
What is the difference between EasyPopulate 4.0 and Easy Populate 1.2.5.4? Which is better and easier to use?

[mc12345678]

Not being smart at all..... I appreciate the response. Will look for it.

Question:
What is the difference between EasyPopulate 4.0 and Easy Populate 1.2.5.4? Which is better and easier to use?

I humbly can not answer the question of "which is easier" as I have not used the other version in a great deal of time if at all... I think I came across the issues that have not been addressed in that version and then when seeing what features were available in this one I made my decsion and as you can see do things to keep it afloat and fnd ways to make improvements (though really little has been needed to accomplish that because of the work put nto it.)

But if not mistaken the other version doesn't support attributes, so I've heard. If a rumor, please disspell it... On the topic of attributes through the need of someone else and their permission some functionality was added to work with SBA (primarily as reworked by potteryhouse.)


So hopefully the regular users of the program will chime in as they are the ones deal with it (or the other) routinely.