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

[Bug] Mentions of #channels do not work #23080

Closed
aleadco opened this issue Sep 1, 2021 · 11 comments
Closed

[Bug] Mentions of #channels do not work #23080

aleadco opened this issue Sep 1, 2021 · 11 comments

Comments

@aleadco
Copy link

aleadco commented Sep 1, 2021

Description:

Mentions of #channels do not work. In mobile applications it works correctly.

The bug is present since 3.17.2 and remains in 3.18.0

Steps to reproduce:

  1. #channel does not create hyperlink

Expected behavior:

Click to go to the channel

Actual behavior:

No hyperlink is created to go to the channel, only the name is displayed.

Server Setup Information:

  • Version of Rocket.Chat Server: 3.18.0
  • Operating System: Ubuntu 20.04
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Yes
  • NodeJS Version: v12.22.1
  • MongoDB Version: 4.4.8

Client Setup Information

  • Desktop App or Browser Version: Web and desktop client.
  • Operating System: Any

Additional context

Relevant logs:

@ankar84
Copy link

ankar84 commented Sep 1, 2021

Not confirm that bug
image
That's from 3.18.0

@aleadco
Copy link
Author

aleadco commented Sep 1, 2021

@ankar84 This is on the web.
https://user-images.githubusercontent.com/35962168/131606625-8e21f597-5866-45f0-999a-8fdf1568eadf.mp4

In the App
Screenshot_2021-08-31-23-24-02-961_chat rocket android

This started from 3.17.2
Is there an option that disables the channel mention?

@aleadco
Copy link
Author

aleadco commented Sep 1, 2021

@ankar84 I already found the cause of the error, it appears when the message analyzer is enabled in Administration / Accounts

@aleadco
Copy link
Author

aleadco commented Sep 1, 2021

As soon as I disabled the option the hyperlink was activated
image

@ankar84
Copy link

ankar84 commented Sep 1, 2021

@ankar84 I already found the cause of the error, it appears when the message analyzer is enabled in Administration / Accounts

You are totally right!
That issue is related to #22280

Someone must take a view to that endless bugs of new parser that meant to be default soon.
@debdutdeb @yashovardhan please pay attention on that.

@debdutdeb
Copy link
Member

Hmm .. let me think on this. Maybe by the end of this week I can get you some answer.

@aleadco
Copy link
Author

aleadco commented Sep 1, 2021

@ankar84 @debdutdeb
I was also able to confirm that the emojis are altered, I just verified.

IMG_20210901_011649.jpg

@debdutdeb
Copy link
Member

I was also able to confirm that the emojis are altered, I just verified.

Is this on the mobile only? Any way to reproduce it?

As an update I'm listing all the bugs that are/might be related to this new parser, and will present them to product.

@aleadco
Copy link
Author

aleadco commented Sep 2, 2021

Is this on the mobile only? Any way to reproduce it?

As an update I'm listing all the bugs that are/might be related to this new parser, and will present them to product.

@debdutdeb
It is not a problem on mobile. When message analysis is active, the encoding of some emojis is not related to the mobile app.

  • Access via the web from any device and react with 👍
  • Access from the mobile application and react with the same emoji but without pressing on the existing one, you must select it as if you were going to add a new one.

Result:
Two different reactions when they should be the same.

Solution:
I deactivated the message analyzer and the reactions match again.

@debdutdeb
Copy link
Member

Hmm. I'll check this out. Thank you Alejandro, :)

@milton-rucks
Copy link

Fixed

@aleadco aleadco closed this as completed Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants