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

Markdown link which url has & has broken #6719

Closed
peccu opened this issue Apr 19, 2017 · 16 comments
Closed

Markdown link which url has & has broken #6719

peccu opened this issue Apr 19, 2017 · 16 comments
Assignees
Milestone

Comments

@peccu
Copy link
Contributor

peccu commented Apr 19, 2017

Rocket.Chat Version: 0.54.2
Running Instances: 1
DB Replicaset OpLog: Enables
Node Version: v4.7.1

Markdown link which url has & has broken.

ex:
[url with & has broken](https://demo.rocket.chat/channel/general?test=test&test2=test2)
becomes a link to https://demo.rocket.chat/channel/general?test=test&test2=test2
( & is replaced to & )

I think this is because of 590d120.
So I'll try to fix and create PR.

@thiagoarrais
Copy link

thiagoarrais commented Sep 28, 2017

Is this live already? I think I've reproduced it in the demo chat today.

Steps to reproduce: Copy and paste this into a rocket chat window:

this is a [mangled link](http://example.com/?q=foo&r=bar)

Expected result: (output html) <a href="http://example.com/?q=foo&r=bar">mangled link</a>

Let me know if you need more info.

@TwizzyDizzy
Copy link

@rocket-cat close

Closibg this, as I cannot reproduce this on latest stable version (0.62.2). Please get back to me with additional details if you think this is still the case and I'll happily reopen :)

Cheers
Thomas

@rocket-cat rocket-cat bot closed this as completed Mar 21, 2018
@nbuchwitz
Copy link

@TwizzyDizzy:
I'm able to reproduce it with 0.63.1 (ac16e93) - maybe be a regression?

@TwizzyDizzy
Copy link

TwizzyDizzy commented Apr 9, 2018

@rocket-cat open

Just reproduced on 0.63.1. Reopening.

Cheers
Thomas

@imeleges
Copy link

Unfortunately, it is the same problem on 0.65.1

@tassoevan
Copy link
Contributor

@rodrigok @sampaiodiego Any update? #7454 and #8318 seem to be related to this.

@sampaiodiego
Copy link
Member

@tassoevan can you please test #8318 to make sure it properly fixes this issue?

@tassoevan
Copy link
Contributor

As @kaiiiiiiiii said there, it isn't the same issue though it has the same root cause. While working on #11165, I noticed that the current markdown parser need some profound tweaks to render messages reliably. I'll look for suggestions from the community and report to the @RocketChat/frontend team.

@ghosty-be
Copy link

issue still present in 0.69.1 ... very annoying since icinga2 also generates this type of URL's with & in between, so alert url in rocketchat are broken :(

@josh0412
Copy link

Issue is sadly still present..

@starso
Copy link

starso commented Jun 27, 2019

I have same problem using api to sen messages - every url been sent to rocketchat have ampersant ( & ) is broken - message is cut just after first occurance of &

@tassoevan
Copy link
Contributor

Which markdown parser (Administration > Message > Markdown > Markdown Parser) is causing this?

@starso
Copy link

starso commented Oct 22, 2019

Which markdown parser (Administration > Message > Markdown > Markdown Parser) is causing this?

Original one

@ggazzo ggazzo added this to the 2.3.0 milestone Oct 25, 2019
@ggazzo ggazzo added the ui/ux label Oct 25, 2019
@MartinSchoeler
Copy link
Contributor

@starso is this only happening when using the API?

@starso
Copy link

starso commented Nov 13, 2019

@starso is this only happening when using the API?

Yes, If i post message directly with url containing & mark everything is fine.
Using API string gets cut after first occurence of & mark.

@MartinSchoeler
Copy link
Contributor

I've just tested using the API and it seems to be working fine in version 2.3.0-develop please try to use the latest version, and if the problem persists, please open a new issue with updated details and the specific API call that you are using. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment