If it helps, there are a few problems here:
1. Human error at Softaculous
Part of the problem is that in the past when the Pro version required the free version as a dependency, the team would sometimes release a new free version but forget to test the Pro version against the new release, and this would break the Pro version.
2. Security problems related to version incompatibility issues during plugin updates
When people update the plugins, let's say that there's a 1.10.0 free version and a 1.10.0 pro version. And if these new versions are not backwards-compatible with version 1.9.0, what happens is that if you update the free version and then the pro version, there's a window during which Loginizer will malfunction and stop working due to the incompatibility between pro and free while the different versions are briefly out of sync.
This creates a security issue, for the brief time while Loginizer is malfunctioning in this scenario.
Developers can mitigate this risk if they have a testing setup and atomic deployments, but otherwise this is a real security problem. Especially for any customers who use WordPress's automatic updates feature, which is even enforced by some popular WordPress hosting providers.
3. Added risk for customers, potential support problems for Softaculous
Adding one extra step that customers need to do -- maintaining two plugins that are supposed to accomplish one thing -- introduces a new source of potential failure, beyond what's listed above.
Please bundle the free plugin code back into the Pro version so that customers have one less plugin to maintain, and one less thing that can go wrong and cause support issues.
Thank you for considering it.
|