php protection
- Thread starter app-user
- Start date
We'll try to reproduce the issue, thanks for the report!
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.
Yes, it is easy, with version 2024.0 save the following code as index.php (for example) , using encoding: utf-8 without BOM...
<?php
header('Content-Type: text/html; charset=UTF-8');
?>
<!DOCTYPE html>
<html lang="es" dir="ltr">
<head>
<meta charset="UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Prueba de codificación</title>
</head>
<body>
<h1>El niño se cayó del monopatín</h1>
<br>
</body>
</html>
Then, in ExeOutput for PHP , at FILE MANAGER, add the file, right click over it, in properties check "Unpack the file to virtual memory at startup..." only, and under the Security tab select "Encode PHP file with internal protection" only. Then, at SECURITY > PHP PROTECTION check "Encode Marked PHP files with internal protection system", compile it and the output text will be:
...as soon as you go back to ExeOutput and uncheck the "internal protection" (both on File Manager or in Security, then recompile, you will see the correct text (without encoding issues). If your need the exop file or any other help from my side, just tell me.
<?php
header('Content-Type: text/html; charset=UTF-8');
?>
<!DOCTYPE html>
<html lang="es" dir="ltr">
<head>
<meta charset="UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Prueba de codificación</title>
</head>
<body>
<h1>El niño se cayó del monopatín</h1>
<br>
</body>
</html>
Then, in ExeOutput for PHP , at FILE MANAGER, add the file, right click over it, in properties check "Unpack the file to virtual memory at startup..." only, and under the Security tab select "Encode PHP file with internal protection" only. Then, at SECURITY > PHP PROTECTION check "Encode Marked PHP files with internal protection system", compile it and the output text will be:
El niño se cayó del monopatÃn
...as soon as you go back to ExeOutput and uncheck the "internal protection" (both on File Manager or in Security, then recompile, you will see the correct text (without encoding issues). If your need the exop file or any other help from my side, just tell me.
Thank you for your reply and the instructions.
Followed them but in ExeOutput 2025 it's working as expected:
Make sure that the PHP source file is encoded as UTF-8: in NotePad++, this command:
Followed them but in ExeOutput 2025 it's working as expected:
Make sure that the PHP source file is encoded as UTF-8: in NotePad++, this command:
OK thanks for the sample, this time we were able to reproduce the problem. We'll study the issue now.