Project

General

Profile

Actions

Defect #11355

closed

Plain text notification emails content is HTML escaped

Added by Arnis Juraga over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Category:
Email notifications
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

There are some problems with latest Redmine versions.
After upgrade to 2.0.2 (the same problem with 2.0.3), when sending e-mail notifications as PLAIN TEXT, something has changed.

Now - "<pre>" tag is replaced with &lt;pre&gt;

There are some other issues with incoming e-mails as well, but this is another issue.


Related issues

Has duplicate Redmine - Defect #12138: Plain Text Emails are Html EscapedClosed

Actions
Actions #1

Updated by Toshi MARUYAMA over 11 years ago

  • Category set to Email notifications
  • Affected version (unused) set to 2.0.3
  • Affected version set to 2.0.3
Actions #2

Updated by Etienne Massip over 11 years ago

  • Subject changed from Redmine 2.0.2 e-mail notifications parsing to Plain text notification emails content is HTML escaped
  • Status changed from New to Confirmed
  • Target version set to Candidate for next minor release
Actions #3

Updated by Etienne Massip over 11 years ago

  • Description updated (diff)
Actions #4

Updated by Etienne Massip over 11 years ago

Bad news: this is a Rails issue, more specifically a 3.x issue regression according to original LH ticket.

Good news: the issue has been reopened 14 days ago and a PR is being worked on (or, at least it was 8 days ago) so it could be fairly well fixed soon.

Actions #5

Updated by Jean-Philippe Lang over 11 years ago

  • Status changed from Confirmed to Closed
  • Assignee set to Jean-Philippe Lang
  • Target version changed from Candidate for next minor release to 2.1.0
  • Resolution set to Fixed

Etienne Massip wrote:

Good news: the issue has been reopened 14 days ago and a PR is being worked on (or, at least it was 8 days ago) so it could be fairly well fixed soon.

The ticket was closed on github. That's odd because I'm still able to reproduce with Rails 3.2... Patch applied in r10205 anyway.

Actions

Also available in: Atom PDF