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

User presence status description not updated #15007

Closed
moerks opened this issue Jul 16, 2019 · 2 comments
Closed

User presence status description not updated #15007

moerks opened this issue Jul 16, 2019 · 2 comments

Comments

@moerks
Copy link

moerks commented Jul 16, 2019

Description:

When switching status from a custom status to one of the 4 predefined ones the description is not updated.
Same applies when editing the status message on the fly and then switching back to "online" for example.
grafik

Steps to reproduce:

  1. Create a Custom Status -> yellow - description: "out for lunch"
  2. Switch your Status to "out for lunch"
  3. Switch your Status back to "online"

Expected behavior:

I'd expect my description to say "online"

Actual behavior:

Description is still "out for lunch" while the color changes from yellow to green.

Server Setup Information:

  • Version of Rocket.Chat Server: 1.2.1
  • Operating System: Linux
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v8.11.4
  • MongoDB Version: 3.4.20
@wreiske
Copy link
Contributor

wreiske commented Jul 17, 2019

This is by design. If you have a status that says "free cake in the break room" and have it set to busy, you will want to keep your status when you switch it to online.

If you want to change your presence back to online, just edit your status, clear it, and whatever your presence is set to will become your status.

You can also just type /status without any text and it will clear your status message. This works in mobile too.

EDIT: I fixed this.... I just read your issue again. You are probably hitting the rate limiter issue. There is a fix already but they have not released a new build with the fix. You are seeing this behavior because you are hitting a rate limit. See #14979 and #15001.

@moerks
Copy link
Author

moerks commented Jul 18, 2019

Thanks. I can live with both answers ;)

@moerks moerks closed this as completed Jul 18, 2019
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

No branches or pull requests

2 participants