nextcloud / nextcloud/files_lock

Provide the internal file id in the web UI of the Files app

Open
#161 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement good first issue
Dominant language
JavaScript
Stars
39
Forks
10
Avg merge
1d 11h
Merged PRs (30d)
48

Description

Is your feature request related to a problem? Please describe.
(unrelated to this issue either my Nextcloud instances have a common problem or Nextcloud 24 has a file locking problem with readme.md and files touched by Nextcloud Office remain locked "by {0}" indefinitely)

In order to use occ files:lock I need the file_id. Lately I need it often, most of the time triggered by something suddenly being locked in the Web UI. I would really ike to get an easy way to get a file_id for copying and pasting

Describe the solution you'd like
Add a tab "internal information" to the file properties where this (and other interesting facts about a file required for occ commands) can be inspected and copied from. You could of course also add tools like forceful file unlocking (or clearing the entire locking database table) to an admin-only section of the right-click pop-up menu)

Describe alternatives you've considered
Sitting in a corner and cry. There is no alternative to unlocking the files manually right now s I need the information.

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 locating the Files app file-properties UI and the entry point that exposes the file_id used by occ files:lock. Define the internal-information tab's displayed and copyable values from the issue, then verify that a user can retrieve the file_id from the web UI for a locked file; the optional unlocking tools are separate scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
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.