EasyPopulate 4.0 Support Thread

[countrycharm]

Blank page... Error log... (Typically)

I have no issue with: PHP Version 5.5.0 and MySql 5.6.12

When you say trying to install the configurations, could you be a little clearer? Able to get to access Tools->Easy Populate 4, but once the page is displayed a selection is made and then a problem occurs? Is that correct?

Sorry about that, no I'm not able to access the page at all. When clicked on easy populate 4 link from tools I get a blank page. I don't get to the Easy Populate 4 page.

Error log
PHP Fatal error: Call to undefined function mb_internal_encoding() in /home/<admin dir>/easypopulate_4.php on line 139

[mc12345678]

Hello,

I looked this under few different search words and didn't see anything similar, so my apologies if it has been discussed.

ZC v1.5.1
EP v4.0.21

Main intention to install the module is that customer created a new store but most of the items are going to be the same. So having more than 800 items he asked if it was possible to do it through a feed or copied into the new store. I suggested EP BUT his items didn't have model numbers. Since EP works with model numbers I told him to use the spreadsheet to create all those model numbers and then we could update his active store and propagate his new one.

The problem is that on the first store EP duplicated all the items, so he had the old ones without model numbers and all the same items duplicated with model numbers.

You would say, well, then delete all the old ones and stay with new ones, but majority of old ones have attributes, also the data of those products orders relation to inventory will be deleted. Without talking about the pain of going 1 by 1 deleting because since they don't have model numbers there's no way to change that data or better put insert the '9' for deleting them.

What should I do to import to those items that don't have model numbers? Does this issue has solution?

Okay, so the short answer to this, that I can think of is to get familiar with SQL commands.

So there are number of ways to go about fixing the situation that I can think of. And yes, while I read all of the above, I can't say that I have a single magic code answer to provide, but I do have a suggested process:

1. First of all, find a way to identify what it is you want to keep/want to not worry about. I would think that a full download would make that determination easier. (These items are active, these are not, these I remember as having attributes (which you could download also), etc...) EP4 does not prevent pulling the data out of the database just because it doesn't have model numbers. Now... It is also possible to pull the product id (if it is not already included in the datadump) through the user defined field(s) of the EP4 configuration. just enter the field name that appears in the products table (Sorry for not going back to reference the table at this point, but its either product_id or products_id). This information will help when you run SQL queries later on all of the data.

2. Okay, so the next thing that could be done is to use the spreadsheet and formulas to generate a SQLl command for the product to be able to update the model number for those that do not have one to something completely unique that won't be able to clash with any other existing product. This could be a combination of things like date, time, row number, etc... So basically, for each item as you look down the list, try to identify a field that has data in every row, where that data is different in each row (ie. product_id) and use it as your WHERE portion of your SQL command. Or if necessary the combination of two or more fields as long as they are uniquely combined (no two rows have the same combination of data), and in the end would use an UPDATE type command. However, may want to test the operation with a SELECT command.

3. Once you have created all of your UPDATE commands, then you can copy and paste them into the Install SQLPatches field from the Admin Tools. And voila, every product will have a model number. Alternatively, you could do a single SQL that would do an update on all products that do not have a model number to have one assigned to it based on whatever data would make that model number unique from any other existing model#.

The last would probably be the easiest/quickest, but would need to know/understand the existing model assignment so that the provided statement would not create a duplication.

All depends on your level of experience/familiarity. Unfortunately, EP4 doesn't currently have a "magically" assign model numbers on export option (yet)...

[mc12345678]

Sorry about that, no I'm not able to access the page at all. When clicked on easy populate 4 link from tools I get a blank page. I don't get to the Easy Populate 4 page.

Error log
PHP Fatal error: Call to undefined function mb_internal_encoding() in /home/<admin dir>/easypopulate_4.php on line 139

Ahh yes, need to have the mbstring extension active in order to use that function... Typically active on a hosted site, and typically initially disabled on local computers... :) Go figure.

[mc12345678]

Ahh yes, need to have the mbstring extension active in order to use that function... Typically active on a hosted site, and typically initially disabled on local computers... :) Go figure.

BTW, sorry, would find this setting/option in your php.ini file, where you have potentially listings of extension=

It may be prepopulated/but commented out with a semicolon at the beginning. On my local version I have
extension=php_mbstring.dll and then I have a comment after php_exif.dll that says that mbstring must precede the exif extension.. I don't know if I added that comment (found in my searches) or if it existed when in the setup, but thought I would share it. I don't use exif, but I had the comment there.

[countrycharm]

Ahh yes, need to have the mbstring extension active in order to use that function... Typically active on a hosted site, and typically initially disabled on local computers... :) Go figure.

My cpanel didn't have mbstring extension active so I'm rebuilding my Easy::Apache profile now. I'll let you know if it works

[ideasgirl]

After reading your post maybe 4 times I'm a bit dizzy (well, my mind is).

1st. Option = I didn't understand much because I went to configuration and updated the "User Defined Products Fields" to products_id and I created another export and there's no column for product id, so I'm lost there.

2nd. Option = I'm also lost there because I wouldn't know how to create that "magic" formula and since I don't have a product_id column there's a lot of repeated data (unless we can solve that).

3rd Opton = If we can solve the "unique" data column, I believe we can go there.

Last and best/easier/quickest Option = Customer created just consecutive numbers 001-001, 001-002, 001-003.....001-830.... and I'm sure he doesn't mind to have a better logic on that number. He just created it that way because the easiest and fastest way to do it without breaking his head about it.

Soooooooooooooo, what's next?

Okay, so the short answer to this, that I can think of is to get familiar with SQL commands.

So there are number of ways to go about fixing the situation that I can think of. And yes, while I read all of the above, I can't say that I have a single magic code answer to provide, but I do have a suggested process:

1. First of all, find a way to identify what it is you want to keep/want to not worry about. I would think that a full download would make that determination easier. (These items are active, these are not, these I remember as having attributes (which you could download also), etc...) EP4 does not prevent pulling the data out of the database just because it doesn't have model numbers. Now... It is also possible to pull the product id (if it is not already included in the datadump) through the user defined field(s) of the EP4 configuration. just enter the field name that appears in the products table (Sorry for not going back to reference the table at this point, but its either product_id or products_id). This information will help when you run SQL queries later on all of the data.

2. Okay, so the next thing that could be done is to use the spreadsheet and formulas to generate a SQLl command for the product to be able to update the model number for those that do not have one to something completely unique that won't be able to clash with any other existing product. This could be a combination of things like date, time, row number, etc... So basically, for each item as you look down the list, try to identify a field that has data in every row, where that data is different in each row (ie. product_id) and use it as your WHERE portion of your SQL command. Or if necessary the combination of two or more fields as long as they are uniquely combined (no two rows have the same combination of data), and in the end would use an UPDATE type command. However, may want to test the operation with a SELECT command.

3. Once you have created all of your UPDATE commands, then you can copy and paste them into the Install SQLPatches field from the Admin Tools. And voila, every product will have a model number. Alternatively, you could do a single SQL that would do an update on all products that do not have a model number to have one assigned to it based on whatever data would make that model number unique from any other existing model#.

The last would probably be the easiest/quickest, but would need to know/understand the existing model assignment so that the provided statement would not create a duplication.

All depends on your level of experience/familiarity. Unfortunately, EP4 doesn't currently have a "magically" assign model numbers on export option (yet)...

[mc12345678]

After reading your post maybe 4 times I'm a bit dizzy (well, my mind is).

1st. Option = I didn't understand much because I went to configuration and updated the "User Defined Products Fields" to products_id and I created another export and there's no column for product id, so I'm lost there.

2nd. Option = I'm also lost there because I wouldn't know how to create that "magic" formula and since I don't have a product_id column there's a lot of repeated data (unless we can solve that).

3rd Opton = If we can solve the "unique" data column, I believe we can go there.

Last and best/easier/quickest Option = Customer created just consecutive numbers 001-001, 001-002, 001-003.....001-830.... and I'm sure he doesn't mind to have a better logic on that number. He just created it that way because the easiest and fastest way to do it without breaking his head about it.

Soooooooooooooo, what's next?

Yeah, kinda' expected the dizziness.. :)

So, for the first thing, am I correct you entered just: products_id in the User defined fields entry of the configuration->Easy Populate 4. Not v_products_id. The code will export a products field that is provided in that user defined fields entry.

So something is wrong with that setup (not the program)

2. That's the getting used to SQL part that I was talking about.

3. So, you do not have any products that have a model number that starts with 001- correct?

Will provide an update SQL statement shortly. Need to go do something else for a few minutes...

[countrycharm]

BTW, sorry, would find this setting/option in your php.ini file, where you have potentially listings of extension=

It may be prepopulated/but commented out with a semicolon at the beginning. On my local version I have
extension=php_mbstring.dll and then I have a comment after php_exif.dll that says that mbstring must precede the exif extension.. I don't know if I added that comment (found in my searches) or if it existed when in the setup, but thought I would share it. I don't use exif, but I had the comment there.

OK this is what I have but I still get a blank page. I'm stumped.

mbstring.detect_order	no value	no value
mbstring.encoding_translation	Off	Off
mbstring.func_overload	0	0
mbstring.http_input	pass	pass
mbstring.http_output	pass	pass
mbstring.http_output_conv_mimetypes	^(text/|application/xhtml\+xml)	^(text/|application/xhtml\+xml)
mbstring.internal_encoding	no value	no value
mbstring.language	neutral	neutral
mbstring.strict_detection	Off	Off
mbstring.substitute_character	no value	no value

[countrycharm]

BTW, sorry, would find this setting/option in your php.ini file, where you have potentially listings of extension=

It may be prepopulated/but commented out with a semicolon at the beginning. On my local version I have
extension=php_mbstring.dll and then I have a comment after php_exif.dll that says that mbstring must precede the exif extension.. I don't know if I added that comment (found in my searches) or if it existed when in the setup, but thought I would share it. I don't use exif, but I had the comment there.

Does it even need that function to operate? If not what needs committing out for it to work.

[mc12345678]

OK this is what I have but I still get a blank page. I'm stumped.

mbstring.detect_order	no value	no value
mbstring.encoding_translation	Off	Off
mbstring.func_overload	0	0
mbstring.http_input	pass	pass
mbstring.http_output	pass	pass
mbstring.http_output_conv_mimetypes	^(text/|application/xhtml\+xml)	^(text/|application/xhtml\+xml)
mbstring.internal_encoding	no value	no value
mbstring.language	neutral	neutral
mbstring.strict_detection	Off	Off
mbstring.substitute_character	no value	no value

What is the source of that table?

Is the error received still the same when you are now getting a blank page? I seem to recall having to enable something else, but can't remember what it is/was.

The error message you are now receiving should shed some light. If it is the same message then probably something else was needed to implement mbstring.