Sitefinity Stuff Module Licensing
When you buy a module you are actually buying a license key to run it under a domain. After purchase, I will contact you to generate a license file for the domains you wish which you then add to your Sitefinity site. (Alongside your Sitefinity.lic file)
Localhost does not require a license key and will operate without restrictions. But other environments will and will apply an execution delay to the processing methods.
What does my license cover?
Your license allows you to use the module on the registered domain(s) forever. You are also entitled to any updates, fixes or improvements that I put out for it.
There is no support agreement with the license but you are encouraged to contact me with any issues as it is in my best interest to address them but I can not provide any development or environment support agreements.
The license file has the name of the module with the .lic extension. Open it up and you will see that it is in XML and easy to read. When the module loads it will look for its license in the App_Data/Sitefinity folder. The same place
you put your Sitefinity license file. When you update your license you will need to restart the site for it to be applied.
<?xml version="1.0" encoding="utf-8"?> <Module name="Pdr.Sitefinity.PaymentProcessor.Stripe"> <DateGenerated>2018-03-22 11:10:36</DateGenerated> <License> <Id>3d4c5e34-6d34-4732-8bbe-5e1f9c370a57</Id> <Type>Standard</Type> <ProductFeatures> <Feature name="Domain">sitefinity-stuff.com</Feature> <Feature name="Subdomain">sitefinity-stuff.fr</Feature> </ProductFeatures> <LicenseAttributes> <Attribute name="Module">Pdr.Sitefinity.PaymentProcessor.Stripe</Attribute> </LicenseAttributes> <Customer> <Name>Darrin Robertson</Name> <Email>firstname.lastname@example.org</Email> </Customer> <Signature>MEQCIFYzMy9y94oZZja8JDxoDp2Q5irqlgwl5TGfpSRpM2YAiAG1ZT2f88IsArHyp0nOGbEu81L9DwolrRIUkZsFPCBkw==</Signature> </License> </Module>
It is important not to edit this file. If you change a character in the <License> element then the validation will fail. If your license file does become corrupt, you will need to get a new one.
What if you don't have a license file? What if it's invalid? What if I don't have the right domains listed?
The module will still run with any of those cases but a time delay of 15 seconds will be added to the execution every time a method is used. Enough to be annoying and impracticable for production but short enough to get through your current development or testing while you sort out a valid license.
Your log files will also record the license issue details in the error and trace logs.
Found a way to cheat the license?
It would be great if you shared it with me :-).