Export to linked file fails with "Invalid column index 16385" after the file was edited in an office suite

未關閉
#3,831 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
php
領域
backend

研究方向

Start in SubmissionService::exportData, where the existing linked spreadsheet is loaded and its columns and rows are synced, and follow the calls to getHighestColumn() and removeColumnByIndex. SyncSubmissionsWithLinkedFileJob hits the same path in the background. Reproduce by loading a spreadsheet whose row 2 has styled cells out to column XFD and checking which column index is passed in. Done means the export either succeeds on that file or stops with a clear error, and the maintainers still need to pick between those two behaviours.

由索引模型根據 Issue 內容生成。

描述

0. Needs triage bug

Exporting submissions into an existing (linked) spreadsheet fails once that file has been opened and saved in an office suite (Collabora/Nextcloud Office). The UI shows "Error while exporting to Files" and the log contains:

PhpOffice\PhpSpreadsheet\Exception: Invalid column index 16385
Since 5.4.0 the export loads the existing file and syncs columns/rows into it (SubmissionService::exportData). After saving in an office suite, row-level formatting (e.g. on the hidden ID row 2) makes getHighestColumn() return the last possible column (XFD = 16384). The column sync (removeColumnByIndex / writing the header) then addresses column 16385, which PhpSpreadsheet rejects.

Steps to reproduce
Create a form, add a submission.
Results → "Export to Files" (xlsx), so the form gets a linked file.
Open the exported xlsx in Nextcloud Office (Collabora), change nothing or format a cell, save.
Add another submission, or export to Files again.
Export fails; the background sync (SyncSubmissionsWithLinkedFileJob) fails the same way.
Expected behavior
The export either works on a file edited in an office suite (e.g. by using getHighestDataColumn() instead of getHighestColumn() and ignoring styled-but-empty cells), or fails with a clear message such as "The linked file was changed outside Forms – please unlink or rename it".

Workaround
Rename or move the edited file and unlink it, then export again (a fresh file is created).

Environment
Forms 5.4.0 (code path unchanged in 5.4.1 and main as of 2026-11-03)
Nextcloud 34.0.5, Docker image nextcloud:34.0.5-apache
Office: Collabora Online (richdocuments 11.1.2)

主要語言
JavaScript
星號
385
分支
133
平均合併
7 小時 54 分鐘
30 天內合併 PR
157

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

nextcloud/forms 的其他 Issue

查看 nextcloud/forms 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。