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
Describe the bug
The avatar is a nice new feature. The problem is, when kimai is installed as subfolder of the top level domain, e.g example.com/kimai2. Then, avatars won't be shown, because the url will resolve in example.com/avatars/.png instead of example.com/kimai2/avatars/.png
To Reproduce
Steps to reproduce the behavior:
Go to example.com/kimai2/de/admin/user/
You won't see the avatars, only broken images of the users
Right-Click on one of the broken images
You will get to an url, like example.com/avatars/.png
Insert 'kimai2', like example.com/kimai2/avatars/.png
Avatar will show up.
Additional context
Add any other context about the problem here.
Kimai version kevinpapst/kimai2 | 1.4.2.0@de533e7031ae194b35f6a638cd95f5c94c516796
PHP version 7.3.1
The text was updated successfully, but these errors were encountered:
Hi @daesters , thanks for letting me know!
I have no subdirectory installation, any chance you could test the changes from the PR #1201 ?
I cannot verify if they work properly, all I can say is that they still work as before for me in a root folder installation.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.
lockbot
locked and limited conversation to collaborators
Jan 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The avatar is a nice new feature. The problem is, when kimai is installed as subfolder of the top level domain, e.g example.com/kimai2. Then, avatars won't be shown, because the url will resolve in example.com/avatars/.png instead of example.com/kimai2/avatars/.png
To Reproduce
Steps to reproduce the behavior:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: