EasyPopulate 4.0 Support Thread

The date looks a little odd, but it may work/go through. I try to make sure it is in the format of YYYY-MM-DD (using all numbers).

mc12345678:

Found and fixed the issue(s) with updating while not using products_model as the primary key. Haven't uploaded the fix quite yet, but will be up soon. Want to also check some of the changes made to the featured products area to address some previously pointed out issues.

Not yet sure about the 0 products updated issue... please check for any log errors in the logs directory...

Uploaded the change(s) for this as well as a few of the other 4.0.35 items to github: https://github.com/mc12345678/EasyPopulate-4.0 in the master thread... Still working on the featured import changes.

FANTASTIC! It's working. Very thankful for the timely and efficient work on this mod. Thank you mc12345678

Quite welcome.

For everyone, submitted version 4.0.35.ZC for review and eventual posting to the ZC plugins available from here.

The use of the added ZC to the version was because on github the version had been updated to 4.0.35 and wanted to be sure that those that had installed it would be notified of the available version on ZC.

Significant changes made are that the featured import now assigns a value that ZC recognizes as a blank field if the in import of the file the available and/or expiry fields are blank, 0 or 0000-00-00.
Somehow in recent updates the ability to import by products_id was disabled by lack of code to support it. All my doing, but that functionality is restored as expected and desired above.
The code has been updated to operate without further modification if a site does not have the applicable mb_ (multibyte) functions activated.
There are other changes which are documented in the changelog of the download and can be pre-reviewed on github or upon posting of the plugin to the ZC site.

In other "news" (although this message may not be seen by all because of the time since my last post), I wanted to let others know about some upcoming planned changes/expansion to EP4.

Currently the operations of EP4 are centrally controlled by the admin file easypopulate_4.php and as applicable other actions are taken during execution of that file (import, export, etc.). Those other actions are addressed in additional external files. (ie. Import is admin/easypopulate_4_import.php). As a result of these external operations but the "central processor" being an admin file, I'd like to make the operations of EP4 available to other outside code while maintaining appropriate security to prevent non-ZC code from activating the operations. This does afterall manipulate the content of the store's database.

So, the first step in this will be to pull out code that directly supports the internal operations into sensible files that could be referenced by some other non-EP4 program in such a way that it would be poised to continue operation through reference of one or more of the other external files.

The next thing, which I'm contemplating both the operation of and potential impact on the store is taking that EP4 data and/or operation structure to a class such that a variable such as $ep4 could be used/referenced from within the admin and the applicable action could take place. So something like $ep4->import($filename) would activate the import of the file. This particular modification, the extent of which remains to be determined may affect others that piggy-back on EP4 and require some code changes to work with the data structure of that new class. Don't worry, this won't be overnight (for those with concerns) and sorry this won't be overnight (for those really wanting that functionality. :) ) There are also some things to consider like in the above example of using the import function to pull in a file, what's to say that the code couldn't be adapted to pull in a variable or some other source? Sure EP4 has been successful at working with and manipulating csv files, but what's to say it couldn't be expanded to work with more in the same controlled method to minimize bloat, processing time, and memory usage.

Anyways, just some thoughts for EP4 in addition to some of the other minification that is planned say for the import operation to pull the contents of specific file processing into its own file thus easing modifications and specialization as well as program readability.

Thoughts/discussion welcome. I'll be opening an issue for each of these on github.

mc12345678:

Quite welcome.

For everyone, submitted version 4.0.35.ZC for review and eventual posting to the ZC plugins available from here.

The use of the added ZC to the version was because on github the version had been updated to 4.0.35 and wanted to be sure that those that had installed it would be notified of the available version on ZC.

Significant changes made are that the featured import now assigns a value that ZC recognizes as a blank field if the in import of the file the available and/or expiry fields are blank, 0 or 0000-00-00.
Somehow in recent updates the ability to import by products_id was disabled by lack of code to support it. All my doing, but that functionality is restored as expected and desired above.
The code has been updated to operate without further modification if a site does not have the applicable mb_ (multibyte) functions activated.
There are other changes which are documented in the changelog of the download and can be pre-reviewed on github or upon posting of the plugin to the ZC site.

Version 4.0.35.ZC is available for download. Notification should be available for those that have previously upgraded to 4.0.34 or newer.

Additional "correction" included sanitization of attribute data that is imported through easypopulate_4_attrib.php.

I updated to the version in the link, and still get the update notification:
Easy Populate 4.0.35.ZC - 04-29-2016 - NOTE: A NEW VERSION OF THIS PLUGIN IS AVAILABLE. [Details]

henry3:

I updated to the version in the link, and still get the update notification:
Easy Populate 4.0.35.ZC - 04-29-2016 - NOTE: A NEW VERSION OF THIS PLUGIN IS AVAILABLE. [Details]

Yes it would because on my latest upload I identified it as v4.0.35.ZC on the ZC website but instead in the file as 4.0.35.ZC. I have submitted a request to the ZC team to modify the version response information to report back the coded 4.0.35.ZC. When that has been performed the notification of a newer version should cease to occur until a newer version is again posted.

Thank you for pointing that out.

henry3:

I updated to the version in the link, and still get the update notification:
Easy Populate 4.0.35.ZC - 04-29-2016 - NOTE: A NEW VERSION OF THIS PLUGIN IS AVAILABLE. [Details]

mc12345678:

Yes it would because on my latest upload I identified it as v4.0.35.ZC on the ZC website but instead in the file as 4.0.35.ZC. I have submitted a request to the ZC team to modify the version response information to report back the coded 4.0.35.ZC. When that has been performed the notification of a newer version should cease to occur until a newer version is again posted.

Thank you for pointing that out.
Fixed .

DrByte:

Fixed .

Thank you!!!!

Now for anyone wondering how that happened? Moments before submitting the version to ZC I had created a version tag in github. In github they recommend the use of the v as a prefix... so, that was fresh in my mind and "seemed" correct when entering the version info to submit for ZC. The impact was not fully recognized. Immediate problem solved though.

I have a little problem. I have updated my plugin but the problem is still there. Products are disappearing.

I have a clean v155 installed. I did a backup of my shop, then imported that file in to the clean install and the products that are 'off' in my shop do not appear in the clean install. I have had a look at CSV and the product that is off is not in the database. So I think it is not being downloaded.

adb34:

I have a little problem. I have updated my plugin but the problem is still there. Products are disappearing.

I have a clean v155 installed. I did a backup of my shop, then imported that file in to the clean install and the products that are 'off' in my shop do not appear in the clean install. I have had a look at CSV and the product that is off is not in the database. So I think it is not being downloaded.

And of course I'm a little confused, but sure we can figure it out.

Clean ZC 1.5.5 installed, check.
Backup of a previous shop made... Is this an export using EP4 or one of the approved/recommended processes for backing up a database in support of say an upgrade?
The export or at least an export using EP4 of the "previous shop" (filename up to and including ep?) does appear to include the "disabled", out-of-stock, red-buttoned product, but the status is shown as 0 or disabled, correct?
Upload and then import of the EP4 file (filename at least up to and including ep?) is only populating product with status of 1 or on.
Part that also is confusing is the last statement, that think it is not being downloaded... Download is the direction of the information coming from the website to your "personal" computer. If the information is in the CSV file then it has been downloaded. If after upload and import the information in that CSV is not making it to the website, then that "could" be an issue with the upload (doubt it) but more than likely something with the import of deactivated product. Not necessarily a terrible thing because import of enabled product works, but certainly not as intended, expected, or desired. Regardless a little confused about which site shows what and what is in what file with any/all not clearly identified as what is missing where.

So, help me with the above and clarify/explain what you can and we'll get through it. :)

mc12345678:

And of course I'm a little confused, but sure we can figure it out.

Clean ZC 1.5.5 installed, check......

I think this is what you are after:

• Using the current shop;
• Using Easy Populate 4.0.35.zc -04-29-2016 for export of the file.
• Filterable Exports; download type selected ‘Complete Products’ (I have also done an export without changing any of the preferences) clicked Export.
• From the table and under title ‘This contains any other file. They will be processed like the upload of a full data file’ download the file using the ‘Download’ button.
• File name exported/Imported: Full-EP2016May05-160538.csv
• Clean install;
• Used EP4’s (same version as above) ‘upload EP File’ to upload and then imported.

Yup, certainly helps.

Now though. Does Full-EP2016May05-160538.csv contain the disabled product of the current store?

mc12345678:

Yup, certainly helps.

Now though. Does Full-EP2016May05-160538.csv contain the disabled product of the current store?

No disabled products can be found in Full-EP2016May05-160538.csv

adb34:

No disabled products can be found in Full-EP2016May05-160538.csv

Okay. I'm taking a look now through the code to see why export using the dropdowns when not selecting a specific option under the status column only provides active product. In the mean time, can envision either of two options working. Change the status dropdown to all and/or use the clickable link that is down below that row of dropdowns.

Okay, looks like the "default" setting (making no changes to the status of product to export) is to export only active product. This can be seen at:
https://github.com/mc12345678/EasyPopulate-4.0/blob/master/admin/easypopulate_4.php#L480 and related code starting at: https://github.com/mc12345678/EasyPopulate-4.0/blob/master/admin/easypopulate_4_export.php#L78

Fyi, next version will include an additional link in the upper right near the remove EP4 statement, this will be an update sql related link so that when changes are made to the install script, the process will be improved to insert ignore all of the settings and therefore the new items will be added while the existing will remain the same. As part of that script change the sort order will be addressed separately so sequencing may change slightly/new items inserted where seen "reasonable". This option will be provided based on some evaluated factors so as to only be shown "when necessary". This will of course depend on updates properly including a "flag" that will need to be changed by the submitter of the code to ZC.

OK, so here I go for another lambasting for being the thickest user.

I've uploaded EP4 and renamed the admin to match store name but not sure I have put it in the right place, when it says upload to admin I presumed that meant the zenadmin | all uploaded in its own directory EasyPopulate-4.0-master

is this the right path to use

Haggis:

OK, so here I go for another lambasting for being the thickest user.

I've uploaded EP4 and renamed the admin to match store name but not sure I have put it in the right place, when it says upload to admin I presumed that meant the zenadmin | all uploaded in its own directory EasyPopulate-4.0-master

is this the right path to use
No.

Almost all plugins (actually "all" as long as they're written consistently) have a set of directories that correspond to the existing directories in your Zen Cart site.

So the easy-populate40-master/admin folder contains the files that you would add to your /admin (or renamed admin) directory.
And likewise most of the easypopulate40-master/whatever files and folders would go in your / (main, no subdirectory) directory.