nextcloud / nextcloud/richdocuments

Document cannot be saved, please check your permissions.

Open
#5,212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

Describe the bug
Exporting a .docx document to PDF fails

To Reproduce

  1. Editing a text document in the web-interface
  2. choosing "Export As"
  3. "PDF Document"
  4. "Save As" (I choose path + filename)
  5. "PDF Options" (I click Export)

I get the error:
Document cannot be saved, please check your permissions.

I can save the document as .docx under a new name in the same folder, so permissions don't seem directly to be the issue.

Expected behavior
I want the pdf file to be generated in the selected directory.

Screenshots
Image

Client details:

  • OS: Ubuntu
  • Browser Chromium and Firefox tested

Server details

I have just installed the apps from the admin web interface, so I don't think there are any non-standard settings.

Debian
Web server: Apache

Database: mysql, Version: 10.11.14

PHP version: Version: 8.2.29

Nextcloud version: Nextcloud Hub 25 Autumn (32.0.2)

Version of the richdocuments app Nextcloud Office Version 9.0.2

Version of Collabora Online Collabora Online - Built-in CODE Server
Version 25.4.702

Configuration of the richdocuments app

occ config:list richdocuments
{
    "apps": {
        "richdocuments": {
            "canonical_webroot": "",
            "disable_certificate_verification": "yes",
            "doc_format": "ooxml",
            "enabled": "yes",
            "external_apps": "",
            "installed_version": "9.0.2",
            "public_wopi_url": "https:\/\/DOMAIN",
            "types": "filesystem,prevent_group_restriction",
            "wopi_allowlist": "",
            "wopi_url": "https:\/\/DOMAIN\/apps\/richdocumentscode\/proxy.php?req="
        }
    }
}

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 by reproducing the .docx-to-PDF export flow in the web interface using the reported Ubuntu, Apache, MySQL, PHP, Nextcloud, richdocuments, and built-in CODE versions. Inspect the richdocuments configuration and export path to determine why PDF output fails despite saving .docx successfully. Done means a PDF is generated in the selected directory without the permissions error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.