[GH-ISSUE #597] general feature req for simple extensibility (umbrella feature req, cite previous feat. reqs also) #429

New issue

Open

opened 2026-03-02 15:58:42 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 15:58:42 +03:00

Owner

Originally created by @acerbis on GitHub (Jul 15, 2021).
Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/597

would be nice at this point to allow in the config.php include approach to define (keeping the "simple" and straightforward approach of config.php) several "events" of the software that the user can specify like:

(AUTH) possibility to declare in config.php a user function that if present is called instead of the default one) used to authenticate the user (accepting user + password)
(SESSION PARAMS) possibility to declare in config.php a user function (that if present is called instead of the default one) that returns the environment and parameters to be used by fileman for the authenticated user (readonly or confined in its user home , forced/allowed filepaths etc....)
(UPLOAD CALLBACK) possibility to declare in config.php a user function (that if present is called instead of the default one) that is called after a successful upload event (passing in the file path just uploaded)
(DOWNLOAD CALLBACK) possibility to declare in config.php a function (that is present if called instead of the default one) that is called after a successful download event (passing in the file path just downloaded)

especially the first three would increase the software usability tenfold in many environments with relatively little modifications.
for example, when i refresh the fileman main file, I need to fix some parts of the main code to allow for i.e. custom authentication

thanks

Originally created by @acerbis on GitHub (Jul 15, 2021). Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/597 would be nice at this point to allow in the config.php include approach to define (keeping the "simple" and straightforward approach of config.php) several "events" of the software that the user can specify like: - (AUTH) possibility to declare in config.php a user function that if present is called instead of the default one) used to authenticate the user (accepting user + password) - (SESSION PARAMS) possibility to declare in config.php a user function (that if present is called instead of the default one) that returns the environment and parameters to be used by fileman for the authenticated user (readonly or confined in its user home , forced/allowed filepaths etc....) - (UPLOAD CALLBACK) possibility to declare in config.php a user function (that if present is called instead of the default one) that is called after a successful upload event (passing in the file path just uploaded) - (DOWNLOAD CALLBACK) possibility to declare in config.php a function (that is present if called instead of the default one) that is called after a successful download event (passing in the file path just downloaded) especially the first three would increase the software usability tenfold in many environments with relatively little modifications. for example, when i refresh the fileman main file, I need to fix some parts of the main code to allow for i.e. custom authentication thanks