1900 results found
Here's the best place to start: https://stripe.com/docs/tutorials/charges. Also, see our existing examples and article for code on how to generate product keys after an order has gone through: http://wyday.com/limelm/help/how-to-generate-product-keys-after-order/
You upload to a location on your servers that can then be accessed by a read-only server (like a read-only FTP account, HTTP server, or HTTPS server). Does that make sense?
See the updated example code for how to handle this: https://wyday.com/forum/t/3013/isgenuineex-returns-an-eror-while-is-isactivated-doesnt/#post-14766 Note: the updated example code will be included with TurboActivate 4.0.
HTTP Basic Auth / Oauth 1 or 2 and the dozen or so spinoffs provide no useful benefit over an API key over HTTPS, especially for the use case of the web API.
Mapped network drives are user specific, so if the app is running under a different identity than the user that created the mapped drive letter (x:) it won't work. wyUpdate might run as a different user depending on the needs of wyUpdate (i.e. needing elevation to complete the update -- thus wyUpdate might be elevated as a different user) You will save yourself a ton of trouble just by using HTTP / HTTPS.
This was mentioned recently in another post: https://wyday.com/forum/t/4451/broken-link-tfs-manager-page/#post-20869 It's a whole new product with a new API that's part of your LimeLM subscription.
For using TurboActivate see the articles and the examples: https://wyday.com/limelm/help/using-turboactivate/ Long story short: you need to add the TurboActivate class to your app, which in turn calls the native TurboActivate.dll.
I am referring the following document, https://wyday.com/limelm/help/using-turboactivate-with-inno-setup/ Trail implementation is missing in this document.
Post by Wyatt O'Day on Aug 25, 2017So if you're determined to use trials in an InnoSetup script (which, again, I would not recommend), then you can use the Delphi example to get there: https://wyday.com/limelm/help/using-turboactivate-with-delphi/
The best place to start is here: https://wyday.com/limelm/help/getting-started/ Integrate TurboActivate and/or TurboFloat in your app following the examples.
Answered multiple times: https://wyday.com/forum/t/3906/able-to-extend-trial-days-by-changing-system-time/#post-18818 Short answer: cooked up behavior is ignored by TA 4.0.
For example, this FAQ: https://wyday.com/limelm/help/faq/#disabled-adapters Notice that 3rd sentence in it tells customers to update their drivers.
https://wyday.com/limelm/help/faq/#latest-libs If (*only after updating to the latest version*) the customer is still getting the error we have a full description of the way to debug it in TurboActivate.h.
Hey David, more information is needed: https://wyday.com/limelm/help/faq/#useful-reports 1.
See: https://wyday.com/limelm/features/why/#snake-oil
When trying to update my test appication it fails with: Error trying to save file: Error downloading https://somthing.azurewebsites.net/somthing/wyserver.wys The underlying connection was closed: An unexpected error occured on a send.
The TFS will try to re-verify with the servers every X + Y days regardless of whether the customer offline activated or not: https://wyday.com/limelm/help/turbofloat-server/#config-isgenuine The difference between offline and online activation is how it handles the failure to reverify with the servers after X + Y days.
https://wyday.com/limelm/help/faq/#useful-reports All error codes are listed in TurboActivate.h and TurboFloat.h /* MessageId: TF_E_CLIENT_IPC Message code (in Hex): 0x14 Message code (in Decimal): 20 MessageText: An error occurred while the TurboFloat client library was trying use interprocess communication facilities.
.): https://wyday.com/limelm/help/faq/#useful-reports
Don't use the web API from your app: https://wyday.com/blog/2019/when-in-conflict-security-supersedes-usability/ We warn about this everywhere the web API is mentioned.