Recent content by gdgsupport

What you saw is the normal behavior of the Full Save mode. An .xlsc file is a complete snapshot of the workbook, including its sheets, formulas and VBA code. Loading it replaces the workbook embedded in the EXE, so after a Web Update an old .xlsc brings back the old version of your application...

Thank you for running the script and posting its output. It answers the question: the older copy of Monolog comes from the Hostinger AI Assistant plugin (wp-content/plugins/hostinger-ai-assistant/vendor/monolog). It is Monolog 2, installed under the standard Monolog name without being isolated...

The System ID is only shown in this window when the project uses hardware-locked keys. Your screenshot shows the activation window without it, so this application was compiled with "Use hardware-locked keys" unchecked: it accepts keys that are not tied to a computer, and therefore has no System...

Thank you for confirming that activation and deactivation now work. A search for a folder named "monolog" does not always find the copy in cause. Depending on how a plugin bundles it, the library can sit in a folder named "Monolog" with a capital M (the search is case-sensitive on Linux...

Good news. Patched runtimes are now available through Web Update; please rebuild your applications afterwards. Details: PHP2Shell

Patched PHP runtimes are now available for ExeOutput for PHP 2025: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. They fix the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619). What to do Refreshed installer: download ExeOutput for PHP 2025.0 (build 25.0.1.0). If you install it over an...

The new error comes from a conflict between the kit's logging and another WordPress plugin on your site. The kit writes its log with the Monolog library, version 3, which it ships in its own folder. To read your WooCommerce orders, the kit then loads WordPress, and with it your plugins. One of...

Thank you for the heads-up. For other readers: the advisory published on php.net on October 21 covers two critical remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619), fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. New PHP runtimes We are preparing updated PHP runtimes...

The error comes from the web server, before the request reaches the WooCommerce Integration Kit. The HTML in your screenshot is not a reply from the kit. It is a "Checking your browser before accessing" page, a bot protection check that runs JavaScript in a web browser before letting the...

Yes: restarting the EXE with the -enterkey switch is the only way. There is no other SetOption value and no other API call that opens the activation dialog while the application is running. Started with -enterkey, the EXE shows the same activation dialog as at first launch, including the online...

Thank you for the video. To read the remaining days of a trial key, use PLEvalVar("TrialState"), as described here: https://www.xlspadlock.com/doc/retrieve-number-of-remaining-days-in-trial-with-vba There is no VBA call that opens the activation dialog while the application is running. To let a...

The cause was found: there was an error in the workbooks.json file. For anyone who gets the same "The license server could not be reached (HTTP 500)" message, this file is the first thing to check. To answer your question for other readers: updating the WooCommerce Integration Kit does not...

Thank you for the detailed example. This is not a statement size limit: it is a current limitation in our VBA compiler. When a method is called with several named arguments and without parentheses, the compiled code passes them with the wrong names, and Excel rejects the call at runtime (error...

Update (October 2026): how XLS Padlock protects your workbook today The answer above dates from 2020. Here is the current picture, as of XLS Padlock 2026.3. Blowfish is no longer used. Encryption is now based on AES: save files are encrypted with AES 256, with HKDF-SHA256 key derivation and...

This question never got a direct answer from us, so here it is, with the facts as of XLS Padlock 2026.3. XLS Padlock does not obfuscate your VBA code: it compiles it. When you build the application, the VBA Compiler turns the pasted macros into bytecode and removes their original source. There...