Why does fluent require 2 plugins?
If you have most or even all of fluent plugins. Then you know that you have a free plugin with limited features and the pro plugin that has all features then on top of all those double plugins then you may need a number of other plugins and before you know it, you end up with 20-40 plugins in order to run your site.
How about reducing 2 plugins into just one plugin? Member downloads 1 plugin with free features, then once they make a purchase, and enter their license then the pro features will be unlocked.
What do you guys think?
If there is only one version, anyone could download the free version and modify the code to enable the pro features without paying for a license.
Thomas Oates I understand but I have a number of paid plugins that are not doubled into 2. Im fact, I have one paid plugin that not only requires a license and I am also required to enter sms code or email verification to prove that I am the owner of the plugin, otherwise the license will not validate and and the pro features would not unlock. Besides, your theory doesn't sound right. Why not just get the pro version, hack it, then pass it around? I can see no reason or justification for having 2 plugins, in fact, it is more of a burden as the free has to be updated, then the pro has to be updated also, and this means more work for the ninja team.
David Scurlock I agree. If you have a lot of WP ManageNinja products, you have to manage twice the plugins. For security and performance reasons, I would rather the Pro versions be standalone plugins, like other developers.
Sean exactly 💯
Totally agreed, just with license activation be able to unlock pro features instead of downloading and installing a separate plugin.
Emilio L. fluent can add even more security by requiring sms code or email verification code in order to validate the license that is tied to the domain, once the code is entered, then the license validates by unlocking any pro features.
Shahjahan Jewel what's your take on this? :)
Not absolutely sure about their reasons, but from my perspective as developer, segmenting code into smaller projects(plugins) reduces size and eliminates surface for attacks at the same time per project. That might be one of their reasons.
Another reason might be to reduce overall complexity within one project by using a factory pattern or something comparable for additional features/entities.
Thirdly, remember, they ALWAYS focus on speed and clean code. It might make sense from this perspective as well.
Maybe I'm totally wrong, then plase simply ignore my thoughts.