<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compatibiliteit on Netsensei</title>
    <link>https://www.netsensei.be/tags/compatibiliteit/</link>
    <description>Recent content in Compatibiliteit 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>Sun, 20 Dec 2009 16:18:17 +0000</lastBuildDate><atom:link href="https://www.netsensei.be/tags/compatibiliteit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WP Mollom 0.7.5</title>
      <link>https://www.netsensei.be/2009/12/20/wp-mollom-0-7-5/</link>
      <pubDate>Sun, 20 Dec 2009 16:18:17 +0000</pubDate>
      <author>matthias@netsensei.nl (Matthias Vandermaesen)</author>
      <guid>https://www.netsensei.be/2009/12/20/wp-mollom-0-7-5/</guid>
      <description>&lt;p&gt;It took a while, but as promised: I just tagged version 0.7.5 of &lt;a href=&#34;http://wordpress.org/extend/plugins/wp-mollom/&#34;&gt;WP Mollom&lt;/a&gt;.
This release only contains small bugfixes. From the changelog:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;fixed: wrong character encoding when comment is fed to wordpress after a
CAPTCHA&lt;/li&gt;
&lt;li&gt;fixed: url was also truncated in href if &amp;gt; 32 chars in the management module&lt;/li&gt;
&lt;li&gt;fixed: changed 2 strings against typo’s&lt;/li&gt;
&lt;li&gt;improved: added pagination on the bottom of the management module&lt;/li&gt;
&lt;li&gt;changed: contact details of plugin author&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The first change is a long overdue bugfix but finally it got into stable. The
bug it fixes caused WP Mollom to truncate the comment body text in certain cases
due to wrong character handling.&lt;/p&gt;
&lt;p&gt;The plugin should also be compatible with WordPress 2.9. I tested it in the past
hours and didn’t have any problems with it so far.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>WordPress 2.0 (bijna) uit!</title>
      <link>https://www.netsensei.be/2005/12/27/wordpress-20-bijna-uit/</link>
      <pubDate>Tue, 27 Dec 2005 11:02:13 +0000</pubDate>
      <author>matthias@netsensei.nl (Matthias Vandermaesen)</author>
      <guid>https://www.netsensei.be/2005/12/27/wordpress-20-bijna-uit/</guid>
      <description>&lt;p&gt;Bon. Officieel is er nog geen bericht van maar de &lt;a href=&#34;http://wordpress.org&#34; title=&#34;&#34;&gt;WordPress&lt;/a&gt; site is
vernieuwd en blijkbaar zijn ze alles aan het gereed zetten om &lt;a href=&#34;http://wordpress.org/download/&#34; title=&#34;&#34;&gt;WordPress 2.0&lt;/a&gt;
vrij te geven. Spannend!&lt;/p&gt;
&lt;p&gt;Toch zijn er ook &lt;a href=&#34;http://www.heritage-tech.net/177/wordpress-20-out-now/&#34; title=&#34;&#34;&gt;disonnante geluiden&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I won’t be upgrading in the near future. Some of the plugins I use works kinda
flakey in WP2.0. I’ve ran 2.0RC3 on HTNet for about 3 hours and the
incompatibilities kinda overwhelmed me.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Verder is de grote vraag: &lt;a href=&#34;http://asymptomatic.net/2005/12/19/2171/whats-not-gonna-work-in-wordpress-20/&#34; title=&#34;&#34;&gt;Wat gaat er (niet meer) werken?&lt;/a&gt; Ik ga gelijk naar
&lt;a href=&#34;http://codex.wordpress.org/User:Matt/2.0_Plugin_Compatibility&#34; title=&#34;&#34;&gt;deze lijst&lt;/a&gt; met plugins die compatibel zijn, verwijzen.&lt;/p&gt;
&lt;p&gt;Zelf ga ik zo snel nog niet upgraden. Ik kijk de kat een beetje uit de
boom…&lt;/p&gt;
&lt;p&gt;En verder schijnt &lt;a href=&#34;http://blog.zog.org&#34; title=&#34;&#34;&gt;Michel&lt;/a&gt; volledig van het Net gevallen te zijn.
Ontwenningsverschijnselen? Náááh!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;UPDATE: &lt;a href=&#34;http://wordpress.org/download/&#34; title=&#34;&#34;&gt;EM IS JUST UIT!&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>