Is there a way to run a server-side command (or a PHP/AJAX function) when 504 error occurs? #3341
Replies: 3 comments 1 reply
-
A quick and dirty way would be to use jQuery .ajaxError() to catch 504 Gateway Timeout. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the answer @mguinness, I still need to find some time to try and implement your suggestion. That said it looks promising. 😉 Here are some (more or less) related issues:
A partially OT questions: is there a way to make elFinder change the Update: Could elFinder query files and their metadata async’ly? That is as soon the metadata of a file are gathered, the file is shown in the UI. Also when the execution time limit is approaching, elFinder should start the gathering again (of course not quering files of which we already gathered the metadata). Update 2: Can elFinder (or I) use |
Beta Was this translation helpful? Give feedback.
-
@tukusejssirs You can extend the execution time by calling However, be aware that PHP does not control timeouts other than max_execution_time for Nginx servers. |
Beta Was this translation helpful? Give feedback.
-
@nao-pon, I need to manage many SMB shares (from Windows mounted on Linux server) for many users via a local website (all shares are available for all users), therefore I opted to mount the shares directly on the server and then add them as simple local storage in elFinder. All those shares should be permanent unless the remote (Windows) is down.
The only issue I currently experience is that when the machine goes offline, it tooks elFinder several seconds (10+ seconds) to notice this and then the following error shows up:
Is there a way to run a command (or a PHP/AJAX function) on the server when this error occurs? Then I’d destroy the elFinder instance and create a new one.
Thanks for the help!
Beta Was this translation helpful? Give feedback.
All reactions