nextcloud / nextcloud/richdocuments

Collabora export pdf not working with spaces in filename

Open
#3,185 15 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug integration: built-in code server
Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

Describe the bug
With Nextcloud running as a snap on Ubuntu and with Nextcloud Office enabled with the CODE server, it is not possible to export a document to pdf format.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Files/Documents in Nextcloud web interface
  2. Click on '(+)/New document' and accept the default name (New document.odt)
  3. Add some text
  4. Click on 'File/Export As/PDF Document' and accept the default name (New document.pdf)
  5. Click 'Export' to accept the PDF Options
  6. Click on 'X' to close the document
  7. Refresh the Documents folder - no new pdf document appears!

Expected behavior

  1. Repeat the steps above, but change the document name to 'New_document.odt', or something else without any spaces
  2. After clicking 'Export' in step 5 above, a dialog box appears with 'Exported to Storage / Successfully exported: New_document.pdf'

Note that changing the name of the exported document doesn't seem to make any difference.

Screenshots
image

Client details:

  • OS: Nixos 23.05
  • Browser Firefox 116.03
  • Device: Lenovo laptop

Server details

Operating system: Ubuntu 22.04

**Web server: See Nextcloud snap version 27.0.2snap1

**Database: See Nextcloud snap version 27.0.2snap1

**PHP version: See Nextcloud snap version 27.0.2snap1

**Nextcloud version: 27.02

**Version of the richdocuments app: Nextcloud Office 8.2.0

**Version of Collabora Online: CODE 23.5.301

Logs
Nextcloud log (data/nextcloud.log)

No new log entries shown in Nextcloud logging.

Insert your Nextcloud log here


#### Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...


</details>

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 export flow in the Nextcloud web interface with the default “New document.odt” name and Collabora CODE enabled, then compare it with a filename without spaces. Trace the export-to-storage path and its interaction with Nextcloud Office; done means a PDF is created and the success dialog appears for filenames containing spaces.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.