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
Background image not showing when Nextcloud runs in sub folder of domain #97
Comments
Thanks for reporting this. It'll probably make sense to specify the custom background location as a relative path instead of absolute. I'll have a look and get it fixed. |
Yor're welcome, I'm happy to help. Let me add a little observation, although I'm not sure it is even related. |
…nds don't use colour from theming app as background
I've have changed the background paths to relative ones, which should hopefully fix it. it will be in the next release, hopefully, out sometime this upcoming week. I also had a look at the background colour on the login screen. I changed it so the background-color is always the main background for the theme, and therefore should look less out of place. |
Actually while I'm working on another issue for the upcoming release, could you verify my change works as intended? I've changed the path to
|
@mwalbeck Yes and thanks, this path works. If you can test it with a installation in the webroot, then this can be closed. |
Great, thanks for testing. It works as intended with with a webroot setup. I'll go ahead and close the issue when the next release is published. |
New release has just been published. |
Describe the bug
When running the nextcloud installation in a sub folder of the domain (mydomain.de/nc) the background image for the login is not displayed.
Setup (please complete the following information):
Additional context
When I manually add the subfolder "nc" to the guest.css like this, it is working:
(original url: /apps/theming/image/background)
The styles from the regular theming show already the correct path but get overwritten by the guest.cc.
The text was updated successfully, but these errors were encountered: