Search results

  1. gdgsupport

    How to configure the splitted files to open them succesfully?

    By default, GSplit produces binary parts meant to be recombined using GSplit’s Self-Uniting feature — not opened directly. That’s why Excel can’t open the resulting files — they’re not valid standalone CSVs. Here’s how to configure GSplit so you get split CSV files that you can open...
  2. gdgsupport

    php protection

    If you have a very simple sample that would let us reproduce the issue, please provide it, as we're not able to get this problem here.
  3. gdgsupport

    Save during execution defaults to old directory

    We added a possible fix in the incoming XLS Padlock 2025.2. Thank you!
  4. gdgsupport

    USER & ADMIN passwords

    XLS Padlock does not natively support assigning two different passwords for two different expiration dates (i.e., one for a standard User and another Admin bypass password) directly within the Application Key Generator. However, here are a few workarounds or solutions to achieve a similar...
  5. gdgsupport

    Code Signing Error

    Please review the compilation log — any code-signing errors will be listed there.
  6. gdgsupport

    Request for XLS Padlock User ID

    The user ID is also now correctly displayed in the "My Account / Downloads" page on our website at https://www.xlspadlock.com
  7. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    ExeOutput for PHP 2025 being officially available, this thread is now closed.
  8. gdgsupport

    ION CUBE EXTENSION NOT WORKING on laravel app

    For IonCube loader DLLs, you must configure ExeOutput for PHP to consider them as ZEND extensions. See our documentation here: https://www.exeoutput.com/help/phpextensions Search for ioncube. You must also use the 32-bit (x86) non thread safe (NTS) version of the DLL file for ExeOutput.
  9. gdgsupport

    Add old php version to Exeoutput for php

    ExeOutput for PHP 2025 brings support for PHP 5. You can get it with the Web Update tool. For other 7.x versions, check our blog at https://www.exeoutput.com/blog
  10. gdgsupport

    Pre-release - ExeOutput for PHP 2025

    You can report the false positive in your app here: [email protected] ExeOutput 2025 is quite new, so some antivirus companies will have to fix their false positives.
  11. gdgsupport

    Pre-release - ExeOutput for PHP 2025

    Thanks for the report. We'll check that.
  12. gdgsupport

    XLS Padlock 2025.1 Is Here - July 10, 2025

    You can remove it here:
  13. gdgsupport

    Request for XLS Padlock User ID

    The user ID was sent to you, please check your support ticket.
  14. gdgsupport

    🔥 ExeOutput for PHP 2025.0 Released with WebView2 Support – Sep 26, 2025

    Thank you oldteacher :D
  15. gdgsupport

    🔥 ExeOutput for PHP 2025.0 Released with WebView2 Support – Sep 26, 2025

    We’re glad to unveil the release of ExeOutput for PHP 2025.0, a major milestone packed with brand-new features and performance boosts for your PHP-to-EXE projects! 👉 Grab the latest version of our PHP to EXE compiler here. Highlights of Version 2025.0 All-New WebView2 Rendering Engine: Choose...
  16. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    Code removed. BTW have you tested removing UTF-8 from the PHP.INI ? Tested your code and could not reproduce the issue...
  17. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    No, but try to remove the default charset in the PHP.ini or leave it empty.
  18. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    Have you defined a default charset in the PHP.ini of your project in ExeOutput?
  19. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    The "about:blank#blocked" issue has been fixed on our side for certain scenarios. For example, internal URLs such as hescript://UserMain.Procedure1|Param1 are no longer accepted in recent Chromium updates. You’ll need to encode the | character for it to work properly. On your side, please check...
  20. gdgsupport

    Pre-release - ExeOutput for PHP 2025 - A Major Update is on the Horizon

    There is no issue actually. You must include an HTML meta tag charset set to UTF-8 and it will work. <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8">
Back
Top