I want to find out if licensing an entire module is feasible or you can only put configuration keys on class/elements that support configuration keys?
For example Assume I have created the new Module [CustomCompanyModule], I can use the guide and lock the new functionality behind a license using the guide above as long as the new functionality is strictly behind elements that support configuration keys. However I want to know if I can set up my module in a way that will allow me to configure the entire module to be based on a license, especially in order to avoid going to every single element and updating configuration keys.
Anyone have experience with this? I have same problem
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.