Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Text app does not detect changed files on external ressources

オープン
  • 何か問題がありますか？
#9,236 コメント 4 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
javascript, nodejs
領域
backend, databases

調査の方向性

The issue involves external storage handling and caching in the Nextcloud Text app. Look at the filesystem abstraction layer and how file timestamps are compared. Check the caching mechanism in the text editor component, likely in Vue files. Start by examining the external storage integration and the conflict detection logic that used to work. Running the reproduction steps locally will help identify where the cache is not invalidated.

索引モデルが issue の本文から書いたものです。

説明

bug

Describe the bug
Nextcloud text does not detect changes to files in the filesystem. Overwrites changed files with stale content.

To Reproduce
Steps to reproduce the behavior:

  1. Add an external to nextcloud
  2. create file test.md on the external storage
  3. open test.md in nextcloud
  4. add text "nexlcoudcontent" to the file via nextcloud text
  5. open test.md outside of nextcloud, where the external(!) storage is primarily used
  6. change text to "externalcontent" in the file via some external resource
  7. open test.md in nextcloud
  8. content of the file is still "nextcloudcontent"
  9. change content to "stillnextcloudcontent"
  10. safe the file in nextcloud
  11. there is NO conflict, the real filesystem content is ignored and overwritten

Even the following is possible:

  1. Add an external to nextcloud
  2. create file test.md on the external storage
  3. open test.md in nextcloud
  4. add text "nexlcoudcontent" to the file via nextcloud text
  5. open test.md outside of nextcloud, where the external(!) storage is primarily used
  6. change text to "externalcontent" in the file via some external resource
  7. open test.md in nextcloud
  8. content of the file is still "nextcloudcontent"
  9. rename the file to test.txt within nextcloud
  10. open test.txt in nextcloud
  11. content of the file is "externalcontent" now
  12. rename the file back to test.md
  13. open test.md in nextcloud
  14. content of the file changes back to "nextcloudcontent"

even running "occ files:scan" in between does not make any difference. Even if "occ files:scan" does detect the changed file, the integrated nextcloud text editor still uses its outdated cache.

Expected behavior
Nextcloud should always(!) check if the file on the filesystem has changed and should deny to use other sources if the file has changed
At least it should use a timestamp within its non-filesystem-cache for cached files and should compare these when writing: if the timestamp in the non-filesystem-cache and the timestamp of the file in the filesystem are different, then obviously some external change was made to the file; in this nextcloud should deny overwriting the file and instead show a conflict warning!

Silently overwriting changed files on external(!) storage is fatal!

This already worked in the past. I'm using this for some time and in the past a conflict was shown. This has gone with one of the last updates. So this is a serious regression.

Screenshots
n/a

Server details:

  • Nextcloud version: from Version 34.0.x on, currently using 35.0.0
  • PHP Version: 8.4
  • Database: MariaDB 11.8.6
  • OS: Debian 13

Client details:

  • OS: several (Linux, Windows, Android)
  • Browser: several (Firefox, Chrome, Android App)
  • Browser version: n/a
  • Device: n/a
主要言語
JavaScript
スター
665
フォーク
133
平均マージ
1日 17時間
マージ済み PR（30日）
172

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextcloud/text のほかの issue

nextcloud/text の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。