EasyPopulate 4.0 Support Thread

[nick02895]

Couple of things. You say, still uses utf8. I understand that 1.5.x does, but does 1.3.8?

Also, state unable to "install mbstring because not your server", does that mean you do not have access to the php.ini file as it shouldn't take much to activate it,and it is probably already "installed" just not active.

Thanks for following up with me.

I don't know that 1.3.8 does or doesn't. From what I've read to convert to utf8 there is a procedure which replaces charset in English.php to include utf8. Mine has that.
Also in phpadmin there is a change to the structure to utf8, my already has that. I have to assume that somewhere in the upgrade to 1.5 my charset was changed to utf8.

I cannot find the php.ini file on this server. This server is very restrictive with limited access. I guess I may be able to create one and make my own settings, but if it's working I will leave it.

Looks like the mb_internal_encoding() just checks utf8 and if not then easypopulate4.php restricts the input.

[mc12345678]

Thanks for following up with me.

I don't know that 1.3.8 does or doesn't. From what I've read to convert to utf8 there is a procedure which replaces charset in English.php to include utf8. Mine has that.
Also in phpadmin there is a change to the structure to utf8, my already has that. I have to assume that somewhere in the upgrade to 1.5 my charset was changed to utf8.

I cannot find the php.ini file on this server. This server is very restrictive with limited access. I guess I may be able to create one and make my own settings, but if it's working I will leave it.

Looks like the mb_internal_encoding() just checks utf8 and if not then easypopulate4.php restricts the input.

Certainly. Wasn't sure if it was your host, or if you were helping someone with their installation. Who are you with? The host company should be able to help. I realize all of the conditions you listed. I would have to at this time defer the discussion of that factor to chadderuski if he's still out there. :). I have not looked at that. Aspect of the code yet and what affects if any there would be of working with the plug-in without that function. I know that when I installed this locally, I chose to enable mbstring on my local install. Glad you have all of the other "upgrades". Thought it was important to discuss for others that read. The forum.

[scottj]

If this mod only adds fields to the products table, then you should be able to use the User Defined Products Fields to add these to your import sheet. After installing the MAP mod, look at the products table or sql you used to modify the table for the field names. Then add these under the Configuration > EasyPopluate 4 :: User Defined Products Fields.

Separate the fields with a comma, but do not add spaces, for example: field1,field2,field3
Do not add quotes either.

Your sheet will then export with columns for these fields as: v_field1, v_field2, v_field3

Let me know how that works for you!
-chadd

This is regards to the MAP Pricing mod. I followed your instructions by setting User Defined Field = v_map_enabled (which I confirmed in my SQL db as the correct field name). I download FULL-EP and it doesn't show up. I upload a CSV with a single record to test and I get the following output (but no change to the db or the product record):

Import Results

Filename: MAP_UL.csv

UPDATED! - Model: 806-1206 | 1 |

Finished Processing Import File

A "1" enables it, a "0" disables it. I'm trying to fully convert away from the old EP version which I had modded to do this. I've had no problems in the past uploading metatag fields with EP4.0 so I'm not sure if I'm missing something? There's no debug error found. I confirmed I can go into the product record manually and change it successfully. Any ideas? Thanks!
Scott

[mc12345678]

This is regards to the MAP Pricing mod. I followed your instructions by setting User Defined Field = v_map_enabled (which I confirmed in my SQL db as the correct field name). I download FULL-EP and it doesn't show up. I upload a CSV with a single record to test and I get the following output (but no change to the db or the product record):

Import Results

Filename: MAP_UL.csv

UPDATED! - Model: 806-1206 | 1 |

Finished Processing Import File

A "1" enables it, a "0" disables it. I'm trying to fully convert away from the old EP version which I had modded to do this. I've had no problems in the past uploading metatag fields with EP4.0 so I'm not sure if I'm missing something? There's no debug error found. I confirmed I can go into the product record manually and change it successfully. Any ideas? Thanks!
Scott

So, I left this message alone last night, because I didn't quite follow it and also thought perhaps the code author might jump in with an answer.

I haven't worked with that aspect of this plug-in (using the user defined fields; however, it may be helpful to see the "single line" data file for one thing (this would identify the fields that are being attempted to be added). That said, it seems that unless you have created a new file type to be able to upload with a filename prefix associated with MAP_UL, then there are several routines within the plugin that will not be activated. Additionally, it appears that the original code author provided direction related to the new fields being added to the products table. Were the new fields added to the products table or some different table? Also (and not to question your knowledge/understanding) the fields entered into the user defined fields, they are the actual field names that were added, not field1,field2,field3,etc... correct?

On the issue of the filename, it seems like the expectation (if the fields were added to the products table) that import to ZC should have the same prefix as the download file ("full...etc"). (Sorry at the moment have forgotten what the exact prefix is.)

Any of that help?

[scottj]

So, I left this message alone last night, because I didn't quite follow it and also thought perhaps the code author might jump in with an answer.

I haven't worked with that aspect of this plug-in (using the user defined fields; however, it may be helpful to see the "single line" data file for one thing (this would identify the fields that are being attempted to be added). That said, it seems that unless you have created a new file type to be able to upload with a filename prefix associated with MAP_UL, then there are several routines within the plugin that will not be activated. Additionally, it appears that the original code author provided direction related to the new fields being added to the products table. Were the new fields added to the products table or some different table? Also (and not to question your knowledge/understanding) the fields entered into the user defined fields, they are the actual field names that were added, not field1,field2,field3,etc... correct?

On the issue of the filename, it seems like the expectation (if the fields were added to the products table) that import to ZC should have the same prefix as the download file ("full...etc"). (Sorry at the moment have forgotten what the exact prefix is.)

Any of that help?

Thanks for the reply. The user defined field I added was v_map_enabled (I had a good chuckle... would've been funny had I added "field1") and the new MAP field *is* located in the products table. As I noted, I know just enough to be dangerous having modded the old EP1.2.5.4 for the MAP field. The contents of MAP_UL.csv test file was simply:

v_products_model | v_map_enabled
806-1206 | 1

As for the file name, this may be the most promising. I don't quite understand all that. I previously attempted to add about 100 new products using the Full-EPxxxx prefix and for whatever reason it deleted all the title/descriptions for the existing 10,000 products. Luckily I had a backup but understandably I've stayed far away from that prefix!

Without any mods I successfully upload metatag data using a CSV file called metatags_UL.csv (which is why I originally added EP4.0 since the old EP doesn't support metatag stuff). Thus I made the assumption, perhaps erroneously, that any file name will work if you just want to upload product fields without "triggering" any of the EP4.0 logic... logic which I readily admit I don't understand. References to it in the instructions were a bit ambiguous for me.

Thoughts?

[mc12345678]

Thanks for the reply. The user defined field I added was v_map_enabled (I had a good chuckle... would've been funny had I added "field1") and the new MAP field *is* located in the products table. As I noted, I know just enough to be dangerous having modded the old EP1.2.5.4 for the MAP field. The contents of MAP_UL.csv test file was simply:

v_products_model | v_map_enabled
806-1206 | 1

As for the file name, this may be the most promising. I don't quite understand all that. I previously attempted to add about 100 new products using the Full-EPxxxx prefix and for whatever reason it deleted all the title/descriptions for the existing 10,000 products. Luckily I had a backup but understandably I've stayed far away from that prefix!

Without any mods I successfully upload metatag data using a CSV file called metatags_UL.csv (which is why I originally added EP4.0 since the old EP doesn't support metatag stuff). Thus I made the assumption, perhaps erroneously, that any file name will work if you just want to upload product fields without "triggering" any of the EP4.0 logic... logic which I readily admit I don't understand. References to it in the instructions were a bit ambiguous for me.

Thoughts?

So to confirm, your database has a field name that begins with a v_? Or if you were to look in mySQLadmin would it be map_enabled?

The code automatically adds v_ as part of creating the CSV file.

So, it looks like the only way to get those fields out of ZC is to do a full export. To get them back in, it looks like you don't have to do a full import. At least there is some data loaded without that type of file...

But I think the real problem is that you have already prefixed the field with v_...

[scottj]

So to confirm, your database has a field name that begins with a v_? Or if you were to look in mySQLadmin would it be map_enabled?

The code automatically adds v_ as part of creating the CSV file.

So, it looks like the only way to get those fields out of ZC is to do a full export. To get them back in, it looks like you don't have to do a full import. At least there is some data loaded without that type of file...

But I think the real problem is that you have already prefixed the field with v_...

Holy crap, that did it! Isn't it always something simple? I defined the user field in admin as v_map_enabled. I just changed it to map_enabled and it worked. Thank you very very much!

[mc12345678]

Holy crap, that did it! Isn't it always something simple? I defined the user field in admin as v_map_enabled. I just changed it to map_enabled and it worked. Thank you very very much!

Sorry couldn't help sooner, I didn't have the code available to review. Figured I'd take a quick look since I saw your message.

Regarding the logic of the program, ah it's a program. :) It does many powerful things and has a lot of capability. With regards to losing the description, I think there is a bit of misconfiguration in that it basically requires the description to be uploaded, and so if the description is not in the CSV file, it uploads NULL... NULL on existing data means bye bye.. But it's handles/addresses a lot of ZC options and processes.

[su35]

Problem with error message "No category provided for this new product"
I have installed EP4 since last year, it works well until today. Some products were inserted and others got the error message. There is no any difference in the category filed. Is anyone can help?

[mc12345678]

Problem with error message "No category provided for this new product"
I have installed EP4 since last year, it works well until today. Some products were inserted and others got the error message. There is no any difference in the category filed. Is anyone can help?

So, reviewed the code for this particular error message. It only appears as is if the category identified in the field does not exist as part of the existing category list. When you look at the CSV file using a basic text editor with just those two entries, do you see any displacement of the quotes? The same number of spaces between the first and the second listing? Have you tried copying the category from the successful one to the unsuccessful? Wondering if there might be some other character code that is not "visible" onscreen.

The other thought depends on the editor that you are using and whether it is saving the file as a proper CSV file and therefore if it is not, then when uploaded for import it is not understanding the line of information properly. Just some basic thoughts.