nextcloud / nextcloud/server

[Bug]: Default nextcloud logo not obeying overwritewebroot and overwrite.cli.url

Open
#53,313 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 31-feedback bug
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

The default nextcloud installation uses the default logo.svg, however the login page (and potentially elsewhere?) is sending requests to /core/img/logo/logo.svg instead of /NEXTCLOUD_PATH/core/img/logo/logo.svg.

All other requests can be sent to /NEXTCLOUD_PATH with appropriate overwritewebroot and overwrite.cli.url settings in config.php. However, requests for /core/img/logo/logo.svg are still being sent from the login page.

It is likely this affects other interface (eg, android).

Note -- this is likely a bug on the server not the interfaces, as the server contains config.php and thus the server is responsible for setting/sending paths. There may be additional interface issues downstream of this, but ultimately the server

Steps to reproduce
  1. Install nextcloud into a subdirectory in a webserver
  2. Configure config.php to have overwritewebroot and overwrite.cli.url appropriately set to the webserver's subdirectory
  3. Observe nextcloud working fine, but on the website's login page (or see server's logs), requests are not being sent to /core/img/logo/logo.svg and NOT the appropriate subdirectory.
Expected behavior

Default logo path should be as configured in config.php

Nextcloud Server version

31

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the login page and config.php handling for overwritewebroot and overwrite.cli.url, then reproduce the issue with a subdirectory installation and inspect the generated logo URL. Done means the default logo request includes the configured subdirectory while the login page works normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.