-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default logo reference should not be absolute #119
Comments
Yes, please. This is a problem that's been keeping me from using this application. |
Does the workaround that I described not work for you? |
Hi, yes the problem is here: I can fix it, do you have any others issues with subfolder usage? |
It is still early days, but I have not found any other of these issues yet! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm trying to deploy xmpp-web in a context root of my webserver (eg:
https://example/xmppweb
).On the login screen, I'm greeted with a broken image.
It appears that the default location of the image that is used, (when the
logoUrl
option is left empty) is absolute:/img/icons/android-chrome-192x192.png
. This causes the breaking image, as the webapp attempts to download:https://example/img/icons/android-chrome-192x192.png
instead of:
https://example/xmppweb/img/icons/android-chrome-192x192.png
It is easily worked-around by configuring the relative path in
local.js
, like this:... but it'd be nice if this would work out of the box.
Steps to reproduce
No response
Expected behavior
Without specifying a
logoUrl
, the image that is used by default should be loaded based on a relative, not absolute location.Relevant log
No response
local.js configuration
No response
XMPP-web version
0.10.0
Installation
Github release archive
XMPP server(s)
Openfire
Browser(s)
Chrome
Device(s)
desktop
Other information
No response
The text was updated successfully, but these errors were encountered: