<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Commenten on Netsensei</title>
    <link>https://www.netsensei.be/tags/commenten/</link>
    <description>Recent content in Commenten on Netsensei</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>nl-NL</language>
    <managingEditor>matthias@netsensei.nl (Matthias Vandermaesen)</managingEditor>
    <webMaster>matthias@netsensei.nl (Matthias Vandermaesen)</webMaster>
    <lastBuildDate>Sat, 09 May 2009 18:03:38 +0000</lastBuildDate><atom:link href="https://www.netsensei.be/tags/commenten/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WP Mollom likes your comments</title>
      <link>https://www.netsensei.be/2009/05/09/wp-mollom-likes-your-comments/</link>
      <pubDate>Sat, 09 May 2009 18:03:38 +0000</pubDate>
      <author>matthias@netsensei.nl (Matthias Vandermaesen)</author>
      <guid>https://www.netsensei.be/2009/05/09/wp-mollom-likes-your-comments/</guid>
      <description>&lt;p&gt;Over the past couple of days, it became apparent that WP Mollom suffers
&lt;a href=&#34;http://blog.zog.org/2009/05/het-probleem-met-commentaren-alhier.html&#34;&gt;an issue&lt;/a&gt; where it “eats” your comment when a CAPTCHA is shown.
The result is that only half of your comment is saved. Not good of course. 
Apart from that, there was also a problem with character encoding.&lt;/p&gt;
&lt;p&gt;Of course, this issue needs solving. I could recreate the problem on a testsetup
and found the culprit. This issue rears its’ ugly head when a commenter
uses double quotes in his/her comment. Because of the way WordPress implements
commenting, I have to embed the commentdata in the CAPTCHA form as a cluster of
hidden fields. The handling of the encoding was a bit wonky here which causes
data to get corrupted.&lt;/p&gt;
&lt;p&gt;I fixed the issue and commited the code in the development version of the plugin
(trunk). I’m not commiting it to a stable version yet because the adjusted
code needs testing against foreign non-western character sets like simplified
chinese and such. If your blog is set to use UTF-8 encoding (which it should!),
you shouldn’t notice big problems with this update.&lt;/p&gt;
&lt;p&gt;If you’re really anxious to get your hands wet, you can download
&lt;a href=&#34;http://downloads.wordpress.org/plugin/wp-mollom.zip&#34;&gt;the development version here&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>