nextcloud / nextcloud/server

Link to removed content in documentation

Open
#36,680 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage feature: settings needs review technical debt
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

These messages refer to the documentation:
https://github.com/nextcloud/server/blob/dcfc96f0cce0a4bc50c4c989464fbbb275ec16b0/lib/private/legacy/OC_Util.php#L545
https://github.com/nextcloud/server/blob/dcfc96f0cce0a4bc50c4c989464fbbb275ec16b0/lib/private/legacy/OC_Util.php#L575
https://github.com/nextcloud/server/blob/dcfc96f0cce0a4bc50c4c989464fbbb275ec16b0/lib/private/legacy/OC_Util.php#L584

but this part in the documentation was removed:
https://github.com/nextcloud/documentation/pull/431

The go-link was also removed: https://github.com/nextcloud/documentation/pull/8226 but I didn't find the reference here. So question is what to do about this?

  • keep the message, just remove the link (is this enough?)
  • add something new in the documentation, and then link to this new stuff

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 with the three referenced messages in lib/private/legacy/OC_Util.php at lines 545, 575, and 584, then review the documentation removals in nextcloud/documentation PRs 431 and 8226. Determine whether each message should lose its link or point to replacement documentation, and confirm that no message links to removed content when done.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.