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

Adding rooms to a community where the group server is not aware of the room leads to "Unamed room" #5866

Closed
turt2live opened this issue Dec 21, 2017 · 1 comment
Labels
A-Spaces Spaces, groups, communities P3 S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@turt2live
Copy link
Member

Description

This does require a bit of database surgery as I don't think it's possible in the current form of groups. As groups progress, this probably will come up more often.

When a room is added to a group where no users of the room are part of the group server, the room shows up as "Unamed room".

Steps to reproduce

This is best reproduced on a fresh homeserver. You'll need two homeservers to do this.

  • On homeserver1 create a new group
  • Add your homeserver2 user to the group
  • Make your homeserver2 user an admin in the group (requires a DB update)
  • On homeserver2's user, add a room which homeserver1 has never seen the group
  • Observe "Unamed room".

Log: not sent

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 63
  • OS: Windows 10
  • URL: riot.im/develop
@t3chguy
Copy link
Member

t3chguy commented Jun 22, 2021

Solved by Spaces

@t3chguy t3chguy closed this as completed Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Spaces Spaces, groups, communities P3 S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants