EasyPopulate 4.0 Support Thread

[chuckrey]

Thanks very much. Looking forward to its use.

[mc12345678]

Thanks very much. Looking forward to its use.

A few hours ago, uploaded modifications to address issues recently identified:
- SBA export of detailed and basic attributes caused SQL errors in the recent 4.0.39.ZC. One of them had a problem because in reformatting to ANSI style queries, an *AND* did not get moved correctly. In the other query, table relationships may have worked historically, but yes with updated server versions, needed to be reworked plus at least one table alias was incorrectly carried through.
- Also corrected the admin page headers so that if one of the menus from this plugin is the first to trigger the issue, well it won't anymore. BTW, what I'm saying is, understand the code that generates that log does so only once per session no matter how many different admin pages "deserve" the report. To me, it would seem better for the session variable to be unique for each such admin page. Maybe someone else agrees, if so, feel free to take it up with the code maintainers.
- Believe I've corrected/addressed the issues that prevented loading/executing the code to/from the zc_plugins folder, although still have a catalog type folder to load so that can use existing ajax calls rather than creating some new ajax tool.
- I haven't installed an alternate language to be able to maybe correct reported issues with categories not aligning or some similar messaging posted recently. The issue typically occurs or was expected to be reported if a single product in two different languages on a single record was pushed to two different category branch depths. In a way, this was done because it seems that ZC doesn't seem to openly support/encourage product/category trees being completely different in a multiple language store. I wanted to offer some amount of store protection in loading/working multiple languages; however, have only been working theoretically/logically.

All of my testing has been against PHP 8.3.2 and MySql 8.0.28-0ubunto0.20.04.3. to include ZC 2.0.whatever is out right now as none of that really has shown to have an impact on the code.

I would like to put it together for publication to the ZC site, but still seeking any additional feedback on issues so that can try to fix them before committing for the majorities.

I do have some changes in mind (for next sub-version):
I'm working on for import to force/ensure data type "conversion" and checks in association with default values. I haven't fully incorporated it because I'm still identifying some of the expected field default values/data types. I've also started considering how to implement default starting values across product types, though I presume "most" still use just the standard product type or if still in use the book type that was branched off of the code.

Another change to incorporate is the use of notifiers that begin with either NOTIFY_ or NOTIFIER_ so that auto loading could be used. My plan is to "duplicate" each notifier to include the additional NOTIFY_ prefix with each new one to follow the existing one. (E.g. where $zco_notifier->notify('EP4_START'); is used, it will be followed on the next line with $zco_notifier->notify('NOTIFY_EP4_START');)

[waterbender]

Hi,

Does anyone know how to export attributes (e.g sizes) based on a category/brand rather than the entire site?

Thanks

[mc12345678]

Hi,

Does anyone know how to export attributes (e.g sizes) based on a category/brand rather than the entire site?

Thanks

While there remain a couple updates to incorporate to the github.com version, the v4.0.39.ZC branch offers such filtering. One known issue to incorporate a fix for is import of a file not having the v_status field sets the status to off regardless the existing status. I have a fix for that, but need to incorporate into the fileset.