Opened 9 years ago
Closed 6 years ago
#1605 closed defect (bug) (invalid)
Apostrophes in Forum Title are encoded within the Email Subject and Content
Reported by: | garrett-eclipse | Owned by: | |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Support Forums | Keywords: | |
Cc: |
Description
Hello,
I've found with forum posts that have an apostrophe in the title are encoded within the auto-generated email.
For example this post;
https://wordpress.org/support/topic/whats-new-in-216?replies=2#post-8077166
Has the title - What's new in 2.1.6
The Email generated has the subject - What's new in 2.1.6.
Here's the contents of the email;
Delivered-To: garrett@eclipsecreative.ca Received: by 10.107.148.85 with SMTP id w82csp2913460iod; Thu, 25 Feb 2016 06:25:33 -0800 (PST) X-Received: by 10.98.19.12 with SMTP id b12mr62534156pfj.29.1456410333299; Thu, 25 Feb 2016 06:25:33 -0800 (PST) Return-Path: <noreply@wordpress.org> Received: from mail.wordpress.org (mail.wordpress.org. [66.155.40.8]) by mx.google.com with ESMTPS id qn15si12882712pab.22.2016.02.25.06.25.33 for <garrett@eclipsecreative.ca> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Feb 2016 06:25:33 -0800 (PST) Received-SPF: pass (google.com: domain of noreply@wordpress.org designates 66.155.40.8 as permitted sender) client-ip=66.155.40.8; Authentication-Results: mx.google.com; spf=pass (google.com: domain of noreply@wordpress.org designates 66.155.40.8 as permitted sender) smtp.mailfrom=noreply@wordpress.org; dkim=pass header.i=@wordpress.org Received: from mail.wordpress.org (localhost.localdomain [127.0.0.1]) by mail.wordpress.org (Postfix) with ESMTP id 5C904CA658 for <garrett@eclipsecreative.ca>; Thu, 25 Feb 2016 14:25:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=wordpress.org; h=date:to :from:subject:message-id:mime-version:content-transfer-encoding :content-type; s=wp1; bh=NUKa5rtk6l5UTRRQrv0IERgD+1U=; b=YtX5s0B qHtRgBsV5X8ilj67sKuSicnhlWfy8M7jPZsE0eDDTuRi/rvvgp502j8h9VKI641D TiTcvUrDNZWSJyXRDZaYmD+VG9Nl4IJXco/CcNviKhBjZMyUYIT1Pxj+bYWVFUvb pBwLaGbZ96sl/atnH11IM8LyuyzJOC70dfqs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=wordpress.org; h=date:to :from:subject:message-id:mime-version:content-transfer-encoding :content-type; q=dns; s=wp1; b=GlkdrjtkEf39wFZKF30HVxM5iqQwLHxv+ KvUEk9IzIo59dJHp5/UGx0+yKmYEvBHQi8gh0Z2xoR3ITiQIQjpf8pDMXy5juNq4 shwMpBFHND8usJmbsJF4ApUs9qU18ZaPP/EMZsQex11mGydGrVttHWHTykndhhYK J58uw7t4Jk= Date: Thu, 25 Feb 2016 14:24:16 +0000 To: garrett@eclipsecreative.ca From: "WordPress.org" <noreply@wordpress.org> Subject: [WordPress.org Forums] What's new in 2.1.6 Message-ID: <12a40883ebfad55f443dfa2a61174e2c@WordPress.org> X-Priority: 3 X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.4] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" MariaKravchenko wrote: Hello. Not sure why it is not showing in Changelog tab. Here it is: * Fixed the bug when page content was always replaced with property_overview shortcode if wpp_search existed in request parameters. +* Fixed multi-checkbox issue on Property Search. +* Fixed issue with odd br in Text Editor Data Entry field. +* Fixed Single checkbox became enabled when publishing new property. +* Fixed converting apostrophe to slash in Property Types. +* Date and Time attributes now take date and time format from Settings/General tab. Regards. Read this post on the forums: https://wordpress.org/support/topic/whats-new-in-216?replies=2#post-8077166 You're getting this email because you subscribed to 'What's new in 2.1.6.' Please click the link above, login, and click 'Unsubscribe' at the top of the page to stop receiving emails from this topic.
This is concerning the WP.org Forums.
Cheers
Change History (6)
#2
@
9 years ago
- Summary changed from Apostrophe's in Forum Title are encoded within the Email Subject and Content to Apostrophes in Forum Title are encoded within the Email Subject and Content
This ticket was mentioned in Slack in #forums by clorith. View the logs.
7 years ago
#5
@
7 years ago
This was fixed in bbPress upstream in #bbpress2865
It should be available to dotorg on the next bbPress deploy
This should be a simple enough fix, and would improve readability for those receiving forum notification emails greatly.