I should add this to be clearer : - when I use LimeLM's manual activation, ActivateFromFile() returns TA_OK - when I use my manual activation on my server, ActivateFromFile() returns TA_FAIL
Hello,
I'm protecting an OSX application with LimeLM, with both online and offline system.The online system works like a charm.However, the webpage on my own server to activate offline doesn't generate a good response file. Here is my context : - of course I followed the tutorial, use the WebAPI bundle, and put my API key in the right place - if I generate the response from LimeLM website (https://wyday.com/limelm/activate/), everything is working - I didn't find the "expires_date" parameter for "limelm.pkey.manualActivation" in the WebAPI (despite it's in manual activation page on LimeLM website)
Could I simply get the PHP code from the "manual activation" page ? It's very nice because the page deals with both activation and deactivation.
Thanx for your help,Philippe
I should add this to be clearer : - when I use LimeLM's manual activation, ActivateFromFile() returns TA_OK - when I use my manual activation on my server, ActivateFromFile() returns TA_FAIL
We'll look into this.
Ok thanx Sam.By the way, "manualDeactivation" service is working correctly on my own server.
Could I simply get the PHP code from the "manual activation" page ? It's very nice because the page deals with both activation and deactivation.
Simply see if the main element is "ActivationRequest". If so, then call the manualActivation api. Otherwise call the manualDeactivation API.
I should add this to be clearer : - when I use LimeLM's manual activation, ActivateFromFile() returns TA_OK - when I use my manual activation on my server, ActivateFromFile() returns TA_FAIL
I can't reproduce this behavior. Make sure your system date, time, and timezone are correct. Then restart your computer and try the manual activation again.
In fact, I understaood my problem now : my PHP server was returning the reponse file with \" instead of simple "So I used urlencode/urldecode on PHP side, and everything is fine now.
Thanx for your time Sam.
Ah, I see. Magic quotes: the bane of every PHP developer's existence. We'll add a warning to the next version of the script telling the user to disable magic quotes if it's enabled.