Search results

Strange because "Add-in 2 System Error. Code: 59" was indeed fixed in XLS Padlock 2024.3 and XLS Padlock 2025 uses the same fix.

It's normal that nothing is written because the Page not Found (404 error) is due to an incorrect NGINX rewrite rule. From the guide:

RunAProgram expects an EXE file. A batch file is not an EXE file. For batch files, you can try OpenFile: OpenFile Opens an external document or program file. function OpenFile(const Filename, Parameters: String; State: Integer): Integer; * Filename: full path to the file you want to open...

In your specific case, the customer must run the EXE and choose to deactivate (if you have deactivation enabled), or they can enter a new key by running: "MYAPP.EXE -enterkey" will ask the end user for a new activation key (useful for instance to replace an old key that is going to expire)...

You cannot access the activation URL directly in a web browser for security reasons. Only a POST method is allowed and this is done by your XLS Padlocked EXE app. Then, please also run a test to verify that the .htaccess rewrite rule works. If you are on NGINX, you have to configure rewrite...

When you release a new update, maybe you should also remove all xlspadlock_runs_xxxx_xxxx fields so that your customers can upgrade. With a SQL query, that should be possible.

Well, that's already the case if you choose the homepage in the "public" subfolder and the project source folder in the root directory of your website.

No, the compilation requires XLS Padlock GUI since cell protection can require interaction with Excel itself. However, you can automate this with automation tools such as AutoIt.

We're preparing another solution to have Selenium support.

The Activation Kit uses a configuration file (commonly config.ini or workbooks.json) to manage multiple applications. For each protected workbook, you'll need to add a corresponding entry to the json file. The config.ini is common. Here's an example structure using workbooks.json: {...

By default, in an ExeOutput app, the "public" folder is the "Data" virtual subfolder of the EXE. This explains it: https://www.exeoutput.com/help/working-with-php/accessingfiles/ And you can change "Data" if you don't want that. It's also optional to use: ExeOutput makes all PHP files available...

Thanks for the follow-up and explanation!

Actually, no, this is already the case in the current WooCommerce kit. So the problem does not lie here. Could you try to temporarily disable the "maxruns" of 2 and see if online validation occurs again?

Some ideas: 1) Use another Excel workbook file that is not compiled into XLS Padlock, and use VBA to open/save this workbook from the main compiled workbook file. 2) Instead of relying solely on Excel files, consider integrating a centralized database (e.g., Microsoft Access, SQL Server) to...

Yes, unfortunately, we don't support flush() in the way PHP is executed by our internal engine.

We replied to your ticket with your user id inside.

Verify that the workbooks.json does not generate activation keys that are configured to bypass online validation.

Maybe DropBox has some cache system? But great to know that it works after some time. Thanks!

The XLS Padlock WooCommerce Integration Kit supports several methods for controlling activation, including limiting the number of runs, days, or setting an expiration date, but it does not natively include an option to prompt for the activation token every 'x' number of times the EXE is opened...

Replied to your email with the solution.