<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: WordPress Problem: Double-Spaced Emails</title>
	<atom:link href="http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<pubDate>Wed, 19 Nov 2008 21:42:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Erik J. Barzeski</title>
		<link>http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20983</link>
		<dc:creator>Erik J. Barzeski</dc:creator>
		<pubDate>Sat, 04 Nov 2006 21:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails/#comment-20983</guid>
		<description>[quote comment="20975"]I'll try a str_replace and report back.[/quote]
Adding this in the appropriate location seems to have helped.

&lt;code&gt;$notify_message = str_replace("\r", '', $notify_message);&lt;/code&gt;

I had done this in my own code, yet it wasn't working. But again, that's because I was uploading my own code to the new server, yet messages were still being created on the old server.

Time to re-extract these methods into a plugin for my own use.</description>
		<content:encoded><![CDATA[<p class="quote_header"><a href="http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20975">Erik J. Barzeski said</a> on November 4, 2006:</p>
<blockquote cite="http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20975"><p>
I'll try a str_replace and report back.</p>
</blockquote>
<p>Adding this in the appropriate location seems to have helped.</p>
<p><code>$notify_message = str_replace("\r", '', $notify_message);</code></p>
<p>I had done this in my own code, yet it wasn't working. But again, that's because I was uploading my own code to the new server, yet messages were still being created on the old server.</p>
<p>Time to re-extract these methods into a plugin for my own use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik J. Barzeski</title>
		<link>http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20975</link>
		<dc:creator>Erik J. Barzeski</dc:creator>
		<pubDate>Sat, 04 Nov 2006 21:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails/#comment-20975</guid>
		<description>[quote comment="20974"]What are the strings in the code that generate the email?  If the emails are plaintext I'd guess unix line endings will give you one line, whilst windows line endings (crlf) would give you two lines?[/quote]
They're \r\n. I had changed them earlier and it seemed to have little effect, but come to think of it, that may have been because I was only uploading the changes to my new server, and some folks were still hitting the old one. Except&#8230; I never had any problems with this double-spacing on the old server.

At any rate, replacing \r\n with just \n on the new server fixes things &lt;em&gt;except&lt;/em&gt; in the comment itself. There, it's still doubled. I'll try a str_replace and report back.</description>
		<content:encoded><![CDATA[<p class="quote_header"><a href="http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20974">bgk said</a> on November 4, 2006:</p>
<blockquote cite="http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20974"><p>
What are the strings in the code that generate the email?  If the emails are plaintext I'd guess unix line endings will give you one line, whilst windows line endings (crlf) would give you two lines?</p>
</blockquote>
<p>They're \r\n. I had changed them earlier and it seemed to have little effect, but come to think of it, that may have been because I was only uploading the changes to my new server, and some folks were still hitting the old one. Except&hellip; I never had any problems with this double-spacing on the old server.</p>
<p>At any rate, replacing \r\n with just \n on the new server fixes things <em>except</em> in the comment itself. There, it's still doubled. I'll try a str_replace and report back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bgk</title>
		<link>http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20974</link>
		<dc:creator>bgk</dc:creator>
		<pubDate>Sat, 04 Nov 2006 21:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails/#comment-20974</guid>
		<description>What are the strings in the code that generate the email?  If the emails are plaintext I'd guess unix line endings will give you one line, whilst windows line endings (crlf) would give you two lines?</description>
		<content:encoded><![CDATA[<p>What are the strings in the code that generate the email?  If the emails are plaintext I'd guess unix line endings will give you one line, whilst windows line endings (crlf) would give you two lines?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Mientjes</title>
		<link>http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails#comment-20966</link>
		<dc:creator>Rob Mientjes</dc:creator>
		<pubDate>Sat, 04 Nov 2006 20:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2006/11/04/wordpress_problem_double-spaced_emails/#comment-20966</guid>
		<description>I've been getting that for about a few months now, and assumed it was just a plug-in mucking about, but if it's the server (as is your case), that could clear things up. I'll keep checking this post and the comments it will receive</description>
		<content:encoded><![CDATA[<p>I've been getting that for about a few months now, and assumed it was just a plug-in mucking about, but if it's the server (as is your case), that could clear things up. I'll keep checking this post and the comments it will receive</p>
]]></content:encoded>
	</item>
</channel>
</rss>
