Search results

That’s fine. Noted. Thanks for your timely responses.

I knew that new option and put a tick on that when compiling. The *.dat file works, but the *.eula and the *.lic don’t. Please double check.

Support, Thanks for the clarification. I don’t think someone will redistribute the kit without your permission because there is a copyright notice you put into the source code. We, your XLSPadlock users, really need a clear path before we can make a decision to go with this Woo Kit, not with...

I need those files saved into the current folder of the EXE file, but the V2017 refuses to do this. Support - can you please help to check this issue? Note that this issue doesn’t happen to the V3.0.0.

That would be great if you can make it works, and it would be a good option to enhance the kit in another way. However, I doubt it will work unless you can arrange to put the provided keygen on your server and generate the keys on the fly. I request that XLSPadlock to make the online keygen...

Golfer65/Support - thanks for your kind praises. Although I’ve managed to jump over those hoops, I’m definitely not a PHP guy, it’s not my expertise, it took me 3 days to write those lines. I wish I could use that time to do something better ie. improving my app to better serve my users. I...

Alright, I’ve got my own problem solved. I would like to share this to you, my fellow XLSPadlock users. Put these below lines into both getactivation and dovalidation functions within the MainController.php at the location as shown in the screenshot, then you can have some additional features to...

You can add it anywhere after retrieving the $order_data, see screenshot for my case. I store the activation keys in the registry, not in an external file.

I found a good side effect of the code for stopping the workbook from activating when order has not been completed. If you include these line of code into both functions getactivation and dovalidation, you will no longer have to use the xlspadlock_blocked. All you have to do to block someone...

Got one checkpoint done, now I’m proceeding to the next but also the last one, I hope. I totally have no idea about what kind of information the $order_data variable can provide and how to extract it. Support - can you please give me a clue how to do this?

OK, I’ve got one checkpoint works. Just want to share it to someone in need. Put these lines somewhere into the MainController.php then you can stop the workbook before the order completed.

Oh, I’m sorry, the slug is from the categories, please see screenshot So, the workflow should be: $customer_order_id=>purchased_product=>product_categories=>slug.

Yes, the Get_Product_Slug function should retrieve the slug as a string from the purchased product.

The $customer_order_id is defined in your Woo kit MainController.php I guess it is integer type, ie 123.

This is indeed a lesson leant for all of us that there should be a clause to cover this kind of situation which is beyond our control. I hope that XLSPadlock can have a solution for you soon.

I did setup the two sets of Woo kits with different API keys. Now the complex problem has been simplified to getting the tokens entered in correct gates. I’ve improved the checking points a bit to allow more type of subscriptions, ie subscription-3year, perpetual etc as shown in the screenshots...

There is no licence key to hand over to customers when they purchase either the trial or the registered version. All keys will be generated on the fly and there is no way to enter the keys manually. The customer will activate the software via tokens. Every time the software runs the validation...

As the Woo kit is a bit clumsy, I tried to find a way to live with it. I made two versions of the kits: one for the 30-days trial workbook, the other is for the 365-day subscription. Both of them work fine with their own channel, however there is an annoying issue: the 365-day subscription users...

Try Application.ThisWorkbook.Path to see if it works. I guess the ico file must be in the same folder with the workbook, not the exe file.

ThisWorkbook.Path will point to your protected workbook extracted to a hidden temporary virtual drive. Try to put the SIGN.ico into the Add Companion Files to see if it helps. This will extract your ico file to the same virtual folder with the workbook.