Ticket descriptions do not escape HTML entities
Reported by Aman Gupta | July 31st, 2008 @ 05:24 PM
Making posting ruby error backtraces particularly painful:
This won't show up:
>> p RuntimeError.new('some crazy error')
#
But if I escape it manually, it will:
>> p RuntimeError.new('some crazy error')
#<RuntimeError: some crazy error>
Comments and changes to this ticket
-
Will July 31st, 2008 @ 05:45 PM
- → Tag changed from “@high error” to “tickets”
- → State changed from “new” to “open”
and you're pasting these into your LH rickets or it's coming in from the API?
-
-
Will July 31st, 2008 @ 06:05 PM
What if you put them into code blocks for formatting by using @@@ruby
http://lighthouseapp.com/help/te... has more details
example
>> p RuntimeError.new('some crazy error') #<RuntimeError: some crazy error> -
Aman Gupta July 31st, 2008 @ 06:18 PM
- → Tag changed from “tickets” to “email tickets”
Test:
>> p RuntimeError.new('some crazy error') #<RuntimeError: some crazy error>Seems to work.. however the email notification I received had the same problem- everything after the # was missing.
As a sidenote, the formatting page is hard to read. A light background on the left half would help distinguish the source from the results.
-
Will July 31st, 2008 @ 06:27 PM
- → Tag changed from “email tickets” to “@high email tickets”
- → Assigned user changed from “” to “rick”
Indeed, I noticed it wasn't workin in the email too. I'll bring this up at the start of next week when Rick is back in the office and we'll start working on a fix. It will probably be tied into our update for markdown.
Thanks for pointing this out. Sorry about the issue.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Using Lighthouse to track Lighthouse.
rick