nextcloud / nextcloud/server

Lack of standard design to show wrong URLs or pages with errors

Open
#58,539 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I have discovered that NC cannot treat the wrong URL, in particular:

  1. https://mydomain.tld/1 leads to the error Page is not found preserving theming in full. That is FINE.
Image
  1. https://mydomain.tld/1.php leads to the page with just a wording File not found without any theming and UI elements. So, this relates to any absent php files.
Image
  1. https://mydomain.tld/remote.php leads to the page with the error Path not found without theming but preserving the elements
Image
  1. https://mydomain.tld/remote.php/dav/user/ leads to the page with the error Page is not found with the default NC theming (no logo and background are kept).
Image
  1. https://mydomain.tld/remote.php/dav/files/not-loggied-in-username/ leads to the page with warning This is the WebDAV interface. It can only be accessed by WebDAV clients such as the Nextcloud desktop sync client. without keeping any theming.
Image
  1. https://mydomain.tld/remote.php/dav/files/lgged-in-username/ leads to just a blank page. Here should be some themed warning that you have to use your webdav client to access the data, please go back to your homepage, whatever.

  2. https://mydomain.tld/remote.php/dav/contacts/username leads to the page with Sabre errors without any styling.

Image
  1. When updating/upgrading the system the logo and the background changes to the default Nextcloud, so not preserving the theming in full.

Is it possible to fix unique design/theming across all pages?

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

Reproduce the listed URLs, including missing paths, WebDAV endpoints, and upgrade pages, and compare their error responses and theming. Trace where each response is generated and identify the existing themed error page to use as the reference. Done means the affected cases consistently show the intended Nextcloud theming and a clear user-facing message.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
design, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.