Use complete URLs and not only relative paths on notification emails' content

Diego Algorta's Avatar

Diego Algorta

17 Feb, 2009 07:19 PM

Hi,

I've just received a notification email about this new comment on my ticket:

http://rails.lighthouseapp.com/projects/8994/tickets/1960-make-named_scopes-remember-the-current-scope-when-defined#ticket-1960-7

As you can see, the commenter included a link to another ticket which works perfectly from the web interface, but in the email I got it doesn't include the protocol and host so my email client can't guess it's a link and makes it tedious to follow it. This is the text I got:

// Add your reply above here
==================================================
Ryan Berdeen updated this ticket at February 17th, 2009 @ 06:12 PM

I believe this was previously reported as [\#1770](/projects/8994/tickets/1770 "Ticket \#1770"), which doesn't have a patch.
--------------------------------------------------------------------------------

NOTE: I had to add the backslash before the # sign so it doesn't get converted again into a link. That backspash is NOT comming in the email

Being a rails developer myself I can guess you're using the _path version of the named route instead of the _url one. Maybe?

  1. 1 Posted by Will Duncan on 17 Feb, 2009 10:55 PM

    Will Duncan's Avatar

    That actually makes a lot of sense and I'm surprised it hasn't come up before. Thank you for the suggestion.

  2. 2 Posted by System on 14 Mar, 2009 12:37 PM

    System's Avatar

    A Lighthouse ticket was created for this discussion

  3. Nicole closed this discussion on 07 Dec, 2009 10:10 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac