Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling showChat at settings file padOptions #4927

Closed
pedrobmarin opened this issue Mar 5, 2021 · 8 comments · Fixed by #5313
Closed

Disabling showChat at settings file padOptions #4927

pedrobmarin opened this issue Mar 5, 2021 · 8 comments · Fixed by #5313

Comments

@pedrobmarin
Copy link
Contributor

Describe the bug
Disabling showChat does not hide chat the same way passing showChat=false as an URL query string.

"showChat": true,

To Reproduce
Steps to reproduce the behavior:

  1. Set showChat to false at settings
  2. Join user
  3. Chat is visible
  4. Add ?showChat=false to the URL
  5. Chat is hidden

Expected behavior
Chat to be hidden when disabling showChat at settings.

Server (please complete the following information):

  • Etherpad version: 1.8.12
  • OS: Ubuntu 18.04.3
  • Node.js version (node --version): v12.18.2
  • npm version (npm --version): 6.14.5

Desktop (please complete the following information):

  • OS: Ubuntu 18.04.3
  • Browser Firefox & Chrome
  • Version 86.0 & 89.0.4389.72
@JohnMcLear
Copy link
Member

We need to make a bigger decision on if passing false as a param hides it by default or just minimizes it. For now can you use ep_disable_chat and be in an okay position?

@webzwo0i
Copy link
Member

webzwo0i commented Mar 5, 2021

Proposal:

Site admins determine if they want chat functionality via settings ('enableChat' defaults to true). If false, PadMessageHandler should not react to chat messages/all server code re chat should be ignored and any functionality re chat in UI should be unavailable (e.g. no sticky, "show chat and user" should read "show user", showChat query param should be ignored)

If enabled, user can pass the following as query string:

  • showChat, determines if the chat window is visible (maximized) after page load, defaults to false
  • disableChat, removes all chat functionality from UI, defaults to false

@stale
Copy link

stale bot commented May 5, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Wont Fix these things, no hate. label May 5, 2021
@stale stale bot closed this as completed May 12, 2021
@JustAnotherArchivist
Copy link
Contributor

I just ran into the same issue. I also expected showChat = false to hide the chat entirely.

And I agree with @webzwo0i. A way to actually disable chat entirely would be great. ep_disable_chat is an okay workaround but only hides the UI elements; the backend would still accept, process, and broadcast chat messages, etc.

@rhansen
Copy link
Member

rhansen commented Sep 16, 2021

My preference would be to move all chat functionality to a plugin.

@rhansen rhansen reopened this Sep 16, 2021
@stale stale bot removed the wontfix Wont Fix these things, no hate. label Sep 16, 2021
@stale
Copy link

stale bot commented Nov 16, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Wont Fix these things, no hate. label Nov 16, 2021
@stale stale bot closed this as completed Nov 23, 2021
@rhansen rhansen reopened this Dec 1, 2021
@stale stale bot removed the wontfix Wont Fix these things, no hate. label Dec 1, 2021
@Loki-Afro
Copy link

@rhansen plus one for the plugin approach.
For context, we integrate etherpad in our platform and have a chat there, having another chat in etherpad is confusing therefore we need to disable it :)

@rhansen
Copy link
Member

rhansen commented Dec 5, 2021

I decided to split this into three issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants