EasyPopulate 4.0 Support Thread

[mc12345678]

I'm thinking that I could create a file that could be commonly pulled from outside software as well as EP4 to provide the version information instead of a database or always loaded define. That way there is no additional burden to the remainder of the site other than the existence of an additional file. Would likely place as a module file. Consider the use of

admin/includes/modules/easypopulate_4_version.php

With the processing contents of something like the existing line in the base module:

<?php
/**
 * Header related information to describe the relationship to EasyPopulate 4
 * @author mc12345678 https://mc12345678.com
 **/

$curver_detail = '4.0.36';

And then the easypopulate_4.php file where that line exists to be changed to:

require DIR_WS_MODULES . 'easypopulate_4_version.php';

[mesnitu]

Yeap, that would be nice, Thanks.
Like I said, I actually haven't dig into how or if other modules declared that they are present, but I think it's nice.
No need to add extra info all over the place, but saying: module x.x.x is present.
ok thanks.

[mc12345678]

Yeap, that would be nice, Thanks.
Like I said, I actually haven't dig into how or if other modules declared that they are present, but I think it's nice.
No need to add extra info all over the place, but saying: module x.x.x is present.
ok thanks.

No problem.

Note though that the simple string like '4.0.36' is not the same as the github title of: EasyPopulate V4 4.0.36 ZC Release, or the tag of: v4.0.36.ZC

Will have to account for those differences in your comparison if using the github information...

[GoldBuckle]

Does Easy Populate have the function to toggle an attribute on/off based on the selection value of another option?

[mc12345678]

Does Easy Populate have the function to toggle an attribute on/off based on the selection value of another option?

May have to read this response a few times.

EP4 or any variation of such does not itself offer catalog side control of options. It interacts with the database to provide information (on import) to populate the database information. If there is a plugin that uses such data to control customer selection, then in that case the data imported will affect the customer's ability to select the product's attributes.

Such a plugin may be Stock By Attributes, available from https://github.com/mc12345678/Stock_...butes_Combined

Using that plugin (or a similar commercial option) it is possible to indicate what attribute(s) become available based on selection of a previous attribute. In that regards, this plugin does support stocking attribute variants that are already defined. This population is currently supported for SBA. It is unknown if other such modules are supported as they have not been tested by me nor reported by others as supported.‎

[swguy]

Does Easy Populate have the function to toggle an attribute on/off based on the selection value of another option?

Bear in mind that the selection of options occurs in the catalog when the customer is buying an item - this is completely separate from easy populate, which is an admin function that populates/updates the database.

[GoldBuckle]

Bear in mind that the selection of options occurs in the catalog when the customer is buying an item - this is completely separate from easy populate, which is an admin function that populates/updates the database.

Okay I will check out Stock by Attributes, thanks!