Listings in the Plugins db + Question about encapsulation

[retched]

Right now I'm releasing two versions of the same plugin in the DB each with the same ID number. Right now I submit one with the _noEPS ending and one without. I wanted to compare the versions to alert of a potential upgrade, but I just realized the last submitted/approved version is what is returned by the plugin_version_check_for_updates function.

I wanted to know if there was a problem in listing a plugin module with the same version number in the ZenCart database? (So, for example, the next version would be listed as v1.1.0 with both a "Encapsulated: Yes" and "Encapsulated: No" version but both will be listed with v1.1.0.)

Secondly, I wanted to ask exactly which versions of ZC are able to take advantage of front-side encapsulation. I know 2.1.0 is out the box, but I'm lost to which of 1.5.8, 1.5.7 can as well.

Also to add on, I'm tempted to release a zip of two zip files as well, but not sure how complicated that would be. Any suggestions would be appreciated.

[DrByte]

Instead of having 2 zips in one zip file, you could just release one zip containing both versions. And if they want the encapsulated one, they just upload the stuff under the zip's zc_plugins directory, else they upload the /includes directory.
Then you wouldn't have to be releasing separate updates either.

[DrByte]

Secondly, I wanted to ask exactly which versions of ZC are able to take advantage of front-side encapsulation. I know 2.1.0 is out the box, but I'm lost to which of 1.5.8, 1.5.7 can as well.

When it comes to installing/upgrading, the /includes/classes/PluginSupport/ScriptedInstallHelpers.php (and any Traits it incorporates or classes it extends) determine compatibility.
eg: v2.0.0 doesn't recognize executeInstallerSelectQuery() in ScriptedInstaller, because it was added in v2.1.0

https://docs.zen-cart.com/dev/plugin...lated_plugins/ mentions a github gist that delineates many things that are different between versions, including whether necessary directories are autoloaded in proper precedence ... which is the crux of compatibility challenges.