Mail: Link with # is cut off at that point

Created on 15 Sep 2017  Â·  4Comments  Â·  Source: nextcloud/mail

Steps to reproduce

  1. Have an email with a link containing a #, like https://docs.nextcloud.com/server/12/admin_manual/installation/source_installation.html#example-installation-on-ubuntu-16-04-lts-server
  2. Click on the link

Expected behaviour

It correctly leads to docs.nextcloud.com/server/12/admin_manual/installation/source_installation.html #example-installation-on-ubuntu-16-04-lts-server

Actual behaviour

It will cut off at the #, leading to https://docs.nextcloud.com/server/12/admin_manual/installation/source_installation.html

(This breaks some links pretty hard, for example because https://zammad.org uses the hashes to link to specific tickets.)


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

3. to review bug good first issue papercut

Most helpful comment

Sounds like what was reported in #147.

Paintext :D Hellos from Mr. Freud.

@ChristophWurst i did a regex for links in comments also a little while back. Also, a pain, i agree. Perhaps it does help you though? cf. https://github.com/nextcloud/server/pull/7680/commits/282567fcedf34d2b7043f90cd5b7ce18d4753720#diff-8d84b744472f51309f72bc30ae82b1b7R24

All 4 comments

Perhaps related: also parameter indicators (?) are ignored, rendering e.g. confirmation links broken.

Perhaps related: also parameter indicators (?) are ignored, rendering e.g. confirmation links broken.

Yup, super annoying. It's some regex magic I couldn't wrap my head around IIRC, thus it's still not fixed. Sounds like what was reported in https://github.com/nextcloud/mail/issues/147.

Sounds like what was reported in #147.

Paintext :D Hellos from Mr. Freud.

@ChristophWurst i did a regex for links in comments also a little while back. Also, a pain, i agree. Perhaps it does help you though? cf. https://github.com/nextcloud/server/pull/7680/commits/282567fcedf34d2b7043f90cd5b7ce18d4753720#diff-8d84b744472f51309f72bc30ae82b1b7R24

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and questions.

Was this page helpful?
0 / 5 - 0 ratings