EasyPopulate 4.0 Support Thread

[mc12345678]

I find something wired,the file name is AASHTO 2014 CSV.csv,when i change to AASHTO.csv everything works fine,can not not add any bank or other words after it,it should have something with the software itself,what should i do now to solve the problem?

Umm, so almost every reference in this forum to saving a file to the server is to not include a space in the filename. Also, it is generally suggested that filenames be all lowercase. The filenames generated by EP4 use either underscores or dashes for "space". If you are able to ftp to your site you could either rename or delete the file(s) or ask your host. Be advised though that depending on the type of import/export file the first part of the filename is important to the program and should not be renamed. The first part typically includes everything up to and including '-ep'.

[e-standard]

Umm, so almost every reference in this forum to saving a file to the server is to not include a space in the filename. Also, it is generally suggested that filenames be all lowercase. The filenames generated by EP4 use either underscores or dashes for "space". If you are able to ftp to your site you could either rename or delete the file(s) or ask your host. Be advised though that depending on the type of import/export file the first part of the filename is important to the program and should not be renamed. The first part typically includes everything up to and including '-ep'.

Thank you very much for your help,but i did not find this problem when i am using ZC 1.3.9 and EP 4.0:

[mc12345678]

Thank you very much for your help,but i did not find this problem when i am using ZC 1.3.9 and EP 4.0:

What version of EP 4 was being used when "this problem" didn't exist? The current version (4.0.35.ZC) continues to work on ZC 1.3.9 also. The significant difference in regards to the file handling of this version to some of the older is the use of $_POST more so than previous versions instead of putting the information on the url using a $_GET.

This may be the first sanitization issue to come across related to the patches that are expected to be applied to all ZC 1.5.x but come mostly standard to ZC 1.5.5.a. Since that filename format is not one that I would typically use nor suggest, no testing was applied to it.

[e-standard]

What version of EP 4 was being used when "this problem" didn't exist? The current version (4.0.35.ZC) continues to work on ZC 1.3.9 also. The significant difference in regards to the file handling of this version to some of the older is the use of $_POST more so than previous versions instead of putting the information on the url using a $_GET.

This may be the first sanitization issue to come across related to the patches that are expected to be applied to all ZC 1.5.x but come mostly standard to ZC 1.5.5.a. Since that filename format is not one that I would typically use nor suggest, no testing was applied to it.

The version i used for old zencart 1.3.9 is Easy Populate 4.0.19 - Beta 1-28-2012,everything works fine.

Expecting updating to solve the problem for zencat 1.5.5a,thank you very much.

[LittleAngell52]

Hi There,

I am using ZC 1.5.5a for my store. Someone may have had the same problem or may have posted for help but I have gone through this post and can't find anything.

I am trying to get my Attribute file on EP to work but I keep on getting the word SKIPPED every time I upload it to my store. Any help how to fix this would be a great help. You can see an image of what getting below.

[mc12345678]

Hi There,

I am using ZC 1.5.5a for my store. Someone may have had the same problem or may have posted for help but I have gone through this post and can't find anything.

I am trying to get my Attribute file on EP to work but I keep on getting the word SKIPPED every time I upload it to my store. Any help how to fix this would be a great help. You can see an image of what getting below.

If notice, not all records are skipped, just some of them. While the error reporting does not appear very helpful as is, the statement indicates that there is something wrong with the assignment/existence of applicable option values to the product in question. Has a basic attribute file been used to apply the option name/value pairs to all of the products?

BTW, while not text searchable, the admin folder of the site appears to be presented in the image. Recommendation is to rename the admin directory and not posting it again in the future. :)

[LittleAngell52]

If notice, not all records are skipped, just some of them. While the error reporting does not appear very helpful as is, the statement indicates that there is something wrong with the assignment/existence of applicable option values to the product in question. Has a basic attribute file been used to apply the option name/value pairs to all of the products?

BTW, while not text searchable, the admin folder of the site appears to be presented in the image. Recommendation is to rename the admin directory and not posting it again in the future. :)

It's the new download files that get skipped and can't work out how to add them via ep.

[mc12345678]

It's the new download files that get skipped and can't work out how to add them via ep.

The error is related to not being able to find an existing record to be updated. With the detailed attributes file, it is primarily setup to first export the file of known attributes, then to update the individual records (fields) of it and import those changes.

This is based on the following sql:

SELECT * FROM ' . TABLE_PRODUCTS_ATTRIBUTES . '
                    WHERE (
                    products_attributes_id = :products_attributes_id: AND
                    products_id = :products_id: AND
                    options_id = :options_id: AND
                    options_values_id = :options_values_id:
                    ) LIMIT 1;

If that sql comes back with no results then the error in the above image is provided.

[LittleAngell52]

The error is related to not being able to find an existing record to be updated. With the detailed attributes file, it is primarily setup to first export the file of known attributes, then to update the individual records (fields) of it and import those changes.

This is based on the following sql:

SELECT * FROM ' . TABLE_PRODUCTS_ATTRIBUTES . '
                    WHERE (
                    products_attributes_id = :products_attributes_id: AND
                    products_id = :products_id: AND
                    options_id = :options_id: AND
                    options_values_id = :options_values_id:
                    ) LIMIT 1;

If that sql comes back with no results then the error in the above image is provided.

Right so how do I add or can I add my downloadable files via EP? I always add the products to the store first and upload all my downloadable files.

[mc12345678]

Right so how do I add or can I add my downloadable files via EP? I always add the products to the store first and upload all my downloadable files.

Next would be to assign the attribute to the product using the attribute basic type file, and then the attributes detailed (current file that is only partially working) to provide refined information for the individual product.