Easy Populate enhancements

[zip1]

A few nights ago I install Easy Populate 2.72, I notice there were several things that could be improved. Listed below are several thing I have done or I am working on.

Item 3a is what I need help on I plan to set it up so that the EP files match a stock OSC then add switches to add feilds and data for various contributions.

Besides what 2.73 incorporated now. What additional common contribes should be considered? I would prefer not to add code for contributions that are not used alot.

 

List of changes/improvements I am working on or finished:

 

1. Apply froogle file fixes. Done

adds cPatch and language name to product URL since this is the way google likes them now.

 

1a.Add additional froogle fields and allow for updates streams.

 

2. move text strings to a file so easy populate admin interface can be translated to

langauges other then english. Done (There will be some addition when the configuration screen is done.)

 

3 write a configuration screen and table:

 

3a. move all configuration information to table so it can be changed in admin

rather then editing the file or so it pulls information already in tables or . Started

 

3b. set up switches so that feilds added by othere contributions can be

easly enabled/disabled if not used not in OSC, like ez_new_feild, Quantity discounts, option type feature.

 

4. When make a new EP/froogle file is put in temp, the completed screen now allows

you go to the file manager temp directory or go back to EP main screen. Done

 

5. Any additional improvement?

 

6. Prepare Easy populate for use with a open source cross platform client.

 

Tom

[devosc]

Hi Tom,

 

Today I downloaded and had a look at EP's code.

 

What time line do expect for the admin interface.

 

Could you first provide a version that does not incorporate any other contribs, or the froogle thing.

 

Can you write/restructure the easypopulate.php more like the other admin files, in particular the case structures that generally occur at the top of the page.

 

I haven't seen this contrib working but, initially I would think it better if the $default_these array is generated automatically based upon the keys in the products table rather than hard coded - for some reason I'm imagining that it would (possibly) later nice to be able to select which fields are to be used via the admin interface.

 

Moving all the ep functions into a file soley for ep functions.

 

kill the global statments where they aren't nessecary. and if needed by a particular function pass them as an argument (if at all possible - i.e. how many need to be passed)

 

I'm not sure but would/might be nice to have a class to hold the core operations of EP.

 

BTW there is a function in MS2 2.2 called tep_catalog_href_link().

 

Anything to reduce the amount of php code occuring within the actual html section.

 

Moving any of the tep files to easypopulate_functions.php if they do not already exist in the core osC 2.2 app already.

 

Maybe the use to array_map instead of $iii++, not sure at present how this comes into play if automatically defining keys.

[Romey-Rome]

I think it would be cool to be able to enter more than 1 file name to upload from temp, and have them run in sequence....I have 16,000 products with no way to overide the PHP timeout, so have to split my file into 6 3,000 line files, and then wait for each one to finish...takes about an hour.

[zip1]

Greg

What time line do expect for the admin interface.

 

1 week if all goes well. But I have a static html web site to do so it may take a little longer.

 

Could you first provide a version that does not incorporate any other contribs, or the froogle thing.

 

I plan on doing an all in one and if you have a contribution installed, you go to the config screen and click on an activate button and the code starts workin, That way someone does not need to edit the code to add code for common contributions.

 

right now pieces and parts are commented out I was planning to

 

if (multi_image == '1'){
   include code to read or write fields here;
}else{
   }

Can you write/restructure the easypopulate.php more like the other admin files, in particular the case structures that generally occur at the top of the page.

 

 

Yes but I was hoping to not have to reinvent the wheel but use as much oc the current code as possible. It may have to be with some of the changes I would like to do.

 

I haven't seen this contrib working but, initially I would think it better if the $default_these array is generated automatically based upon the keys in the products table rather than hard coded - for some reason I'm imagining that it would (possibly) later nice to be able to select which fields are to be used via the admin interface.

 

To tell the trueth I have only worked with the froogle file I guess I had better check the funcionality of an up load and see if that needs fixed. I do know that it need some more checks, It assumes that data for a field is there if not it deletes what you have in the field. some how just a change file need to be done. Or create code strange code to indicate that you want the data in a field deleted and not replaced. If its empty don't change it.

 

Moving all the ep functions into a file soley for ep functions.

 

yes that would be a good Idea, I have had really bad luck with functions and classes in a file for some reseaon. I usually have to rewrite to make the external.

 

kill the global statments where they aren't nessecary. and if needed by a particular function pass them as an argument (if at all possible - i.e. how many need to be passed)

all the globals are neede because of the way it is written. doing that many globals in a file makes it unstable. Or at least in my opion. That kind of cleanup could take a month but may be needed to make what I want to do needed.

 

 

 

Anything to reduce the amount of php code occuring within the actual html section.

 

Moving any of the tep files to easypopulate_functions.php if they do not already exist in the core osC 2.2 app already.

 

Yes I could add this to the list of things to do. I had a hard time trying to figure out what was trying to be done. Normally it isn't that hard.

 

Maybe the use to array_map instead of $iii++, not sure at present how this comes into play if automatically defining keys.

 

This requires a major rewrite which is what I was try to avoid. I see how the other things go. But considering for the long term I am looing for something to create a data stream for a client interface I will probely end up doing a rewrite in the long term.

Tom

[zip1]

Romey_Rome

I think it would be cool to be able to enter more than 1 file name to upload from temp, and have them run in sequence....I have 16,000 products with no way to overide the PHP timeout, so have to split my file into 6 3,000 line files, and then wait for each one to finish...takes about an hour.

 

yes I'll add that and see what i can do. Doing something like the filename_1 filename_2

may work then creating a loop that calls each file into EZ Pop.

 

A question:

 

Do all of your products change with each upload or just certain ones? Would

just doing a change file work better. I probely won't be able to do this now but it something for long term.

 

Tom

[Romey-Rome]

No, not all of them. But a good number of 'em do...about half I'd say.

 

That would be really cool if you could get it to call files in sequence...would be a big time saver for me...so THANKS! Even if you can't get it to work, thanks for the effort. Thats what makes OSC so great....

[JGofGFS]

Tom,

 

Just wondering if you've made any more headway on this useful set of upgrades. In particular, the compatibility with Option Type feature. I'm in the midst of setting up some cumbersome scripts to put back the Option Type feature that gets lost in a new Easy Populate upload and having easy populate add them would save me boatloads of time.

 

Thanks

 

Justin

[zip1]

My appologies, I work with of those compilations of OSC that can be mentioned on the forums.

 

I have been extremaly busy with and have never gotten back to Easy populate.

 

Hopefully in a few weeks I will be able to get back to it.

 

 

Tom

[blueline]

I think it would be cool to be able to enter more than 1 file name to upload from temp, and have them run in sequence....I have 16,000 products with no way to overide the PHP timeout, so  have to split my file into 6 3,000 line files, and then wait for each one to finish...takes about an hour.

Wow really? I just set up a shop with 10,000 products and it took about 5 minutes.

 

I also set up a shop with 70,000 products, and that took about 2-3 hours.

 

Seems like something is wrong if it's taking an hour for 16,000 products.

 

-Chris