You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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'];
The text was updated successfully, but these errors were encountered:
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):
The text was updated successfully, but these errors were encountered: