AllBugsFeaturesChangelogBountiesSearchNew post
Sign in with Fluxer
Bugs

Comment history

Versions of a comment on Newly created channels do not appear in the category list until the web app is reloaded, newest first.

Current version | Edited by Fullest
Changes
7. Account B will see no change to the channel list until refreshRemoved: This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur.Added: This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur. It's likely the bot used in the initial report is doing something similar to this. I am guessing clients are set to automatically refresh channel visibility on any permission change, but are not refreshing when new channels are created in categories they already cannot see.
Show
CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US on the main fluxer.app instance. The specific steps that need to happen to reproduce this manually are: Account A = Admin Account B = User
  1. Account A creates a channel category
  2. Account A sets the channel category permission to deny View channel to @everyone
  3. By this point, Account B needs to open the community and be looking at it
  4. Account A clicks to create a channel inside the category
  5. Click the radio button for Private channel and fill out a name
  6. Grant a specific user or role access to the channel
  7. Account B will see no change to the channel list until refresh
This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur. It's likely the bot used in the initial report is doing something similar to this. I am guessing clients are set to automatically refresh channel visibility on any permission change, but are not refreshing when new channels are created in categories they already cannot see.
Edited by Fullest
Changes
Removed: CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-USAdded: CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US on the main fluxer.app instance.The specific steps that need to happen to reproduce this manually are:
Show
CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US on the main fluxer.app instance. The specific steps that need to happen to reproduce this manually are: Account A = Admin Account B = User
  1. Account A creates a channel category
  2. Account A sets the channel category permission to deny View channel to @everyone
  3. By this point, Account B needs to open the community and be looking at it
  4. Account A clicks to create a channel inside the category
  5. Click the radio button for Private channel and fill out a name
  6. Grant a specific user or role access to the channel
  7. Account B will see no change to the channel list until refresh
This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur.
Edited by Fullest
Changes
5. Click the radio button for Private channel and fill out a name6. Grant a specific user or role access to the channelAdded: 7. Account B will see no change to the channel list until refreshThis issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur.
Show
CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US The specific steps that need to happen to reproduce this manually are: Account A = Admin Account B = User
  1. Account A creates a channel category
  2. Account A sets the channel category permission to deny View channel to @everyone
  3. By this point, Account B needs to open the community and be looking at it
  4. Account A clicks to create a channel inside the category
  5. Click the radio button for Private channel and fill out a name
  6. Grant a specific user or role access to the channel
  7. Account B will see no change to the channel list until refresh
This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur.
Original by Fullest
Show
CR: Canary Desktop 2026.1101.10907, Web 2026.1101.35229, Linux 7.2.11-200.fc44.x86_64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US The specific steps that need to happen to reproduce this manually are: Account A = Admin Account B = User
  1. Account A creates a channel category
  2. Account A sets the channel category permission to deny View channel to @everyone
  3. By this point, Account B needs to open the community and be looking at it
  4. Account A clicks to create a channel inside the category
  5. Click the radio button for Private channel and fill out a name
  6. Grant a specific user or role access to the channel
This issue does not get reproduced if you create a channel inside the category and subsequently change the channel's permissions at that stage. You must initially create the channel as a Private channel for this to occur.