Just for completeness - the following issue affects above behavior:
opened 09:21AM - 21 Sep 21 UTC
closed 11:27AM - 13 Jun 23 UTC
bug
ticket
verified
prioritised by payment
specification required
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 4.1/stable
* Installation method (source, package, ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: verified on Google Chrome & Thunderbird
* Ticket: #1092157
### Expected behavior:
Using variables within URLs in signatures is no problem if you insert them correctly.
### Actual behavior:
Zammad sanitizes correct inserted URL to death upon saving the signature.
*Note: This does not affect e.g. trigger based emails*
### Steps to reproduce the behavior:
* update any signature of your choice and insert the following URL without formatting (CTRL+SHIFT+V)
`https://example.com/kundenzufriedenheit/123456/1a2b3d/!pi=#{ticket.number}`
* save the signature
* go to any ticket and hit reply and check the signature - the link already is broken:
```
<a href="https://example.com/kundenzufriedenheit/123456/1a2b3d/!pi=#%7Bticket.number%7D"
title="https://example.com/kundenzufriedenheit/123456/1a2b3d/!pi=71005"
rel="nofollow noreferrer noopener"
target="_blank">https://example.com/kundenzufriedenheit/123456/1a2b3d/!pi=71005
</a>
* double tab in the signature section (it's broken there as well)
I also checked rails console level - this is how Zammad saves it into the database
```
Yes I'm sure this is a bug and no feature request or a general question.
2 Likes
system
Closed
January 19, 2022, 4:15pm
3
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.