nextcloud / nextcloud/whiteboard
Add an administration option to remove the real-time collaboration error message in the “Overview” section
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
I suggest adding an administration setting (in the Whiteboard panel) to make this error message disappear from the "Overview" admin panel:
"WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it."
Please refer to the Nextcloud Talk case when HPB is not configured; an option in the Talk administration settings allows you to hide the warning and ensure that the instance verification turns green.
Nextcloud Talk mentioned setting :
Where you should add the same kind of option to hide the Whiteboard error message in the "Overview" panel :
The Whiteboard error message I'm talking about :
I am making this suggestion because you are not preventing people from using Whiteboard, and it is simply necessary for them to know that online collaboration is not possible without Websocket, just as it is possible to use Talk without HTB.
The idea is for administrators to be aware of this, without scaring them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Whiteboard administration panel and the warning shown in the Overview admin panel. Compare the proposed setting with the existing Nextcloud Talk administration option for an unconfigured HPB. Done means administrators can hide the WebSocket warning while basic Whiteboard functionality remains available and instance verification reflects the chosen setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100