You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot find any channel with an underscore in it's name when using the search nor can I find it through the directory list. This only happens when special characters in channel names are allowed.
IMO this happens, because underscores get replaced with dashes?!
Server Setup Information:
Version of Rocket.Chat Server: 0.63.3
Operating System: Ubuntu
Deployment Method(snap/docker/tar/etc): tar
Number of Running Instances: 4
DB Replicaset Oplog: yes
Node Version: 8.9.4
mongoDB Version: 3.6
Steps to Reproduce:
Allow special characters in channel names
Create a channel with underscores in its name
Expected behavior:
Channel name in sidebar with underscores
Channel name in browser url bar with underscores
Channel name on channel information page with underscores
Channel name on edit page with underscores
Channel name in search with underscores
Channel name in directory list with underscores
Actual behavior:
Channel name in sidebar with underscores
Channel name in browser url bar WITHOUT underscores (replaced with dashes)
Channel name on channel information page WITHOUT underscores(replaced with dashes)
Channel name on edit page with underscores
Channel name in search WITHOUT underscores (replaced with dashes)
Channel name in directory list WITHOUT underscores (replaced with dashes)
Screenshots:
The text was updated successfully, but these errors were encountered:
kaiiiiiiiii
changed the title
Cannot find channel in search & directory list when using underscore in channel name
Cannot find channel in search & directory list when using underscores in channel name
Apr 19, 2018
Description:
I cannot find any channel with an underscore in it's name when using the search nor can I find it through the directory list. This only happens when special characters in channel names are allowed.
IMO this happens, because underscores get replaced with dashes?!
Server Setup Information:
Steps to Reproduce:
Expected behavior:
Actual behavior:
Screenshots:
The text was updated successfully, but these errors were encountered: