I'm not sure what's so difficult to understand. This ExeOutput is not a standard server, but some wrapper, and clearly it breaks some PHP behavior. If you really need to use it, then surely you have the technical capabilities of looking into PHP features that it breaks? I can't support some app that creates "stand-alone and secure applications in native Windows EXE format with PHP, JavaScript and HTML" unless it follows standard PHP features.
fabiosistemi running the same test with XAMPP (leaving the configuration unchanged) the problem does not arise.
Of course, because XAMPP correctly supports $_FILES['file']['size']
.
fabiosistemi There is something wrong with the ExeOutput for PHP configuration.
Yes. Because $_FILES['file']['size']
is empty or not set.
I'm not sure how you expect me to give you solutions when it's the application ExeOutput that is breaking the behavior. If it doesn't work, then this should be fixed in ExeOutput, because this is what causes the issue.
fabiosistemi I have not made any changes to the index.php section if(!isset($file['size']) || empty($file['size'])) json_error('invalid file size'); was left unchanged.
Never said you did. I said this is where it fails on ExeOutput, because the values from ExeOutput are empty. This is obviously wrong, because file size is obviously not 0 or empty.
If you want, you can edit the index.php code to remove all checks for uploaded file size, and that might then work in ExeOutput. This would just be a hack to get it to work with ExeOutput, because size is supposed to be set of course.
fabiosistemi Is there any way to make uploading with files.gallery easier?
What do you mean make it easier? Is it difficult? If you want to fix it in ExeOutput, then fix the problem. The problem is ExeOutput. Surely this makes sense?