Rocket.chat: Can't set default rooms anymore

[apmilen]

Rocket.Chat Version: 0.55.1
Running Instances: 1
DB Replicaset OpLog: Disabled
Node Version: v4.8.1

Hi! It seems that setting default rooms is disabled for me somehow? I definitely used to have this admin permission, but now I can't see the option when viewing a room.

Is there some new UI that I'm missing here? Or am I mistaken in the assumption that members of the admin role can set default rooms?

[ccesareo]

This happened to me the other day. I believe when I refreshed the page and went back to it the option appeared again.

[MartinSchoeler]

Hey @apmilen looks like you are using a outdated version of Rocket.Chat, this issue has been fixed on version 0.56.0, so updating your instance should fix the issue. Thanks for the feedback!

[apmilen]

thanks :)

[johanricher]

I'm having the same problem on our instance (chat.codefor.fr): impossible to change the default status of rooms. I've done it before and could swear it was a toggle option within the Rooms page in the Administration panel. It's not there anymore:

Can we please reopen this issue to get to the bottom of this?

Version: 2.4.0
Deployment Method: Cloudron
OS: linux x64 4.4.127-mainline-rev1
Node version: v8.12.0
Mongo version: 3.6.3
OpLog | Enabled

[johanricher]

@MartinSchoeler Can you give me some advice? Do I open a new issue?

[MartinSchoeler]

@johanricher This Bug seems to have returned, I will reopen this issue.

[ritwizsinha]

I would like to work on this,

[MartinSchoeler]

@ritwizsinha there is no ownership of issues in Rocket.Chat, so nobody should give or ask for permission to work on stuff, if you want to work on something, just create a pull request. We usually review and merge PRs based on their quality, and not by "who made it first", anyways this particular issue will already be closed on #16025

[GoetheG]

Having version 2.4.0. I have the same issue here.

[gabriellsh]

Fixed by #16433

[johanricher]

Problem solved on my end, with Rocket.Chat 2.4.7. :tada: Thank you and congrats to all the team on releasing version 3.0.0 soon. :clap:

[Attack44]

The problem has been around for a long time and version 3.2.0 is no different.