nextcloud / nextcloud/richdocuments
NextCloud 25.0.2 + built-in CODE 22.5.802 does not open files, only download them
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Describe the bug
It is not possible to open files online. I can only download them.
To Reproduce
Steps to reproduce the behavior:
- Go to Files
- Put the cursor over an .ODT file
- See the URL shown by the browser
- The URL is a Webdav link of the type:
https://…/remote.php/webdav/file.odt
Expected behavior
The URL should be one opening the file: https://…/index.php/apps/files?dir=/&openfile=319304
Screenshots taken when a Collabora demo server is selected



Screenshots taken when the Built-in CODE is configured



Client details:
- OS: macOS 13.1 (22C65)
- Browser 1: Safari 16.2 (18614.3.7.1.5)
- Browser 2: Chrome 108.0.5359.124 (Official Build) (x86_64)
- Device: MacBook Pro 15"
Server details
Operating system: Linux 4.9.182-paas-110c975 x86_64, 3 CPU, 1 GB RAM
Web server: Apache/2.4.43 (Unix) with loaded modules: core.c, event.c, http_core.c, mod_access_compat.c, mod_alias.c, mod_auth_basic.c, mod_auth_digest.c, mod_auth_form.c, mod_authn_core.c, mod_authn_file.c, mod_authz_core.c, mod_authz_groupfile.c, mod_authz_host.c, mod_authz_user.c, mod_autoindex.c, mod_cgi.c, mod_deflate.c, mod_dir.c, mod_env.c, mod_expires.c, mod_filter.c, mod_gandiacc.c, mod_headers.c, mod_include.c, mod_info.c, mod_log_config.c, mod_mime.c, mod_negotiation.c, mod_proxy.c, mod_proxy_fcgi.c, mod_request.c, mod_rewrite.c, mod_session.c, mod_session_cookie.c, mod_session_crypto.c, mod_setenvif.c, mod_so.c, mod_status.c, mod_unixd.c, mod_vhost_alias.c
Database: MySQL version: 8.0.18
PHP version: 8.0.12
Nextcloud version: 25.0.2.3
Version of the richdocuments app: Nextcloud Office version 7.0.2
Version of Collabora Online: Built-in CODE Server version 22.5.802
Logs
Nextcloud log (data/nextcloud.log)
Nothing during these tests and while configuring CODE.
Browser log
Empty
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure from Files with an .ODT file, comparing the configured Collabora demo server with the built-in CODE server. Check the URL produced in each case and use the expected /index.php/apps/files?dir=/&openfile=... form as the completion criterion; the issue reports no useful Nextcloud or browser logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100