nextcloud / nextcloud/text

Recipient of a federated share cannot edit md file

Open
#2,053 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Describe the bug
When creating a federated share of a md file, the recipient is asked to choose from "Current version" and "Saved version" even if is the first time he/she opens it.

Subsequent actions of the recipient on the received file cause undefined behaviour (file infinite reloading, reloading of the same page ...)

To Reproduce
Steps to reproduce the behavior:

  1. Go to instance1 with user1, create a file called new-file.md, put some contents in it, save it and share it with user2@instance2 with edit privileges
  2. Go to instance2 with user2, accept the federated share and open the file new-file.md

Expected behavior
user2@instance2 should be able to edit the file or receive a clear message that file editing is not supported for federated shares

Screenshots
Screenshot from 2022-01-04 20-59-02

Client details:

  • OS: Ubuntu Desktop 21.10
  • Browser: Firefox
  • Version: 95.0.2 (64-bit)
  • Device: laptop
Server details

2022-01-04.md

Logs Please note instance1 and instance2 are behind a Global Scale Master node, but I replicated the issue also in a non-GS setup.

nextcloud.log

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 issue with new-file.md across instance1 and instance2 using the listed federated-share steps, and review the attached logs and screenshot. Determine whether the recipient can edit the shared file; done means editing works without the version prompt and reload loop, or a clear unsupported-editing message is shown.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.