nextcloud / nextcloud/server

[Bug]: 'PDF conversion' flow does not properly update PDF

Open
#51,978 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 31-feedback bug feature: workflows
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

All latest as of this day versions

Nextcloud 31.0.2
'NextCloud office' app 8.6.4
'Collaborative tags' app 1.21.1
'Workflow external scripts' app 2.0.0
'Automated PDF conversion' app 2.0.0 (LibreOffice installed on the server)
'PDF viewer' app 4.0.0
Manual changes to files in https://github.com/nextcloud/server/pull/51927
Collabora Online server (NOT built-in CODE)
NextCloud Encryption enabled

Problem: PDF not correctly updated in 'overwrite existing PDF' mode with 'PDF conversion' flow.

  1. Created flow for PDF creation/update upon 'file created' and 'file updated' events with the following settings

Note - event type does not matter here, the error is reproduced with other trigger events (except for 'tag assigned', which does not work anyway - see https://github.com/nextcloud/server/issues/51849 )

Image

  1. Created ODT file with content 'Lorem ipsum'

  2. Cron job executed. PDF is generated by the flow, with 'Lorem ipsum' content.

Image

Image

  1. Modified ODT (added 'Mod'), saved changes

Image

Image

  1. Cron job executed. PDF file was somehow changed, but there are NO visible changes to the content, the original 'Lorem ipsum' is still there

Image

Image

If PDF is downloaded, it also 'Lorem ipsum' version.

  1. Then, on PDF file, going to Open Details > Versions > clicking on 'Initial version' or 'Current version' or 'Compare to current version' nothing happens - black screen, infinite loader

Image

  1. Then, on PDF file, going to Open Details > Versions > 'Current version' - Download. Downloaded version is 'MOD Lorem ipsum'

Image

So somehow PDF is updated inside, but not written properly (cache, DB, etc, no idea), so end-user still sees old PDFs, when PDF is accessed from regular UIs.

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 reported sequence using the PDF conversion flow, cron job, overwrite-existing-PDF mode, and Versions UI described in the issue, with the listed Nextcloud and app versions. Review the manual file changes associated with PR #51927 and compare the generated PDF's visible content, downloaded content, and version actions; done means updated PDFs are shown and the Versions actions load correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
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.