[GH-ISSUE #1180] after login the user is redirected to the directory and not to the (renamed) tinyfilemanager.php #759

Open
opened 2026-03-02 16:01:16 +03:00 by kerem · 1 comment
Owner

Originally created by @BlackBrix on GitHub (May 12, 2024).
Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/1180

after update to 2.5.3:
after the user has logged in with his credentials,
he is redirected to to the directory and not to the (renamed) tinyfilemanager.php.

I renamed "tinyfilemanager.php" to "pro_filer.php"
in my case "pro_filer.php" is located in the directory "https://myDomain.tld/upload/uploads/"
so when calling "https://myDomain.tld/upload/uploads/pro_filer.php"
the login dialog appears in the browser.
The user fills in his known credentials, and hits the "sign in" button

doing so the user should be redirected to "https://myDomain.tld/upload/uploads/pro_filer.php" , right ?
instead he is redirected to the bare directory "https://myDomain.tld/upload/uploads/"
where a "forbidden" page appears in the browser since there is no index.* file (or whatsoever) in this directory

(Then if I again type in manually "https://myDomain.tld/upload/uploads/pro_filer.php" in the browser,
I get into the tinyfilemanager GUI being logged in and can work normally ...)

I did not have this problem with 2.5.0 (same server / same directory)


my configuration is (was the same in 2.5.0):

// Root path for file manager
// use absolute path of directory i.e: '/var/www/folder' or $_SERVER['DOCUMENT_ROOT'].'/folder'
// $root_path = $_SERVER['DOCUMENT_ROOT'];
$root_path = '/home/webpages/XXX/YYY/www/myDomain/upload/uploads';

// Root url for links in file manager.Relative to $http_host. Variants: '', 'path/to/subfolder'
// Will not working if $root_path will be outside of server document root
// $root_url = '';
$root_url = '/upload/uploads';

// Server hostname. Can set manually if wrong
// $_SERVER['HTTP_HOST'].'/folder'
$http_host = $_SERVER['HTTP_HOST'];
Originally created by @BlackBrix on GitHub (May 12, 2024). Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/1180 after update to 2.5.3: after the user has logged in with his credentials, he is redirected to to the directory and not to the (renamed) tinyfilemanager.php. I renamed "tinyfilemanager.php" to "pro_filer.php" in my case "pro_filer.php" is located in the directory "https://myDomain.tld/upload/uploads/" so when calling "https://myDomain.tld/upload/uploads/pro_filer.php" the login dialog appears in the browser. The user fills in his known credentials, and hits the "sign in" button doing so the user should be redirected to "https://myDomain.tld/upload/uploads/pro_filer.php" , right ? instead he is redirected to the bare directory "https://myDomain.tld/upload/uploads/" where a "forbidden" page appears in the browser since there is no index.* file (or whatsoever) in this directory (Then if I again type in manually "https://myDomain.tld/upload/uploads/pro_filer.php" in the browser, I get into the tinyfilemanager GUI being logged in and can work normally ...) I did not have this problem with 2.5.0 (same server / same directory) ------------------- my configuration is (was the same in 2.5.0): ``` // Root path for file manager // use absolute path of directory i.e: '/var/www/folder' or $_SERVER['DOCUMENT_ROOT'].'/folder' // $root_path = $_SERVER['DOCUMENT_ROOT']; $root_path = '/home/webpages/XXX/YYY/www/myDomain/upload/uploads'; // Root url for links in file manager.Relative to $http_host. Variants: '', 'path/to/subfolder' // Will not working if $root_path will be outside of server document root // $root_url = ''; $root_url = '/upload/uploads'; // Server hostname. Can set manually if wrong // $_SERVER['HTTP_HOST'].'/folder' $http_host = $_SERVER['HTTP_HOST']; ```
Author
Owner

@BlackBrix commented on GitHub (May 12, 2024):

OK,
I just found out that this (release) version 2.5.3:
https://github.com/prasathmani/tinyfilemanager/releases
is not the same as this version 2.5.3:
https://github.com/prasathmani/tinyfilemanager/blob/master/tinyfilemanager.php
(very confusing -> both the very same version numbers)

so this bug was solved 2 years before:
https://github.com/prasathmani/tinyfilemanager/pull/896/commits/1f0c8538edbc832713f582bb7a86d19aac28d100
but is not part of the release from Feb 22, 2023 (1 year old)
https://github.com/prasathmani/tinyfilemanager/releases

<!-- gh-comment-id:2106217553 --> @BlackBrix commented on GitHub (May 12, 2024): OK, I just found out that this (release) version 2.5.3: https://github.com/prasathmani/tinyfilemanager/releases is **not** the same as this version 2.5.3: https://github.com/prasathmani/tinyfilemanager/blob/master/tinyfilemanager.php (very confusing -> both the very same version numbers) so this bug was solved 2 years before: https://github.com/prasathmani/tinyfilemanager/pull/896/commits/1f0c8538edbc832713f582bb7a86d19aac28d100 but is **not** part of the release from Feb 22, 2023 (1 year old) https://github.com/prasathmani/tinyfilemanager/releases
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tinyfilemanager#759
No description provided.