<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Why Are Plugins and Tools Making My Code Invalid?</title>
	<atom:link href="http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/</link>
	<description>Blogging the web, usability and apple.</description>
	<pubDate>Tue, 06 Jan 2009 15:27:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Simon</title>
		<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/comment-page-1/#comment-17915</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sun, 13 Jan 2008 02:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/#comment-17915</guid>
		<description>&lt;strong&gt;Michael&lt;/strong&gt; - I'm still using the Wordpress inline editor, but it's only for lack of an alternative I like enough to stick with.  I'm waiting for Ecto and Mars Edit to merge into a single, glorious, application.

&lt;strong&gt;Marco&lt;/strong&gt; - That plugin looks interesting, I may try it out.  The reason I use the plugin I do is because it's only supposed to challenge spam bots with the CAPTCHA text, and not the average user.  Supposedly giving the best of both worlds (i.e. making it very difficult for the spam bots, while still being seamlessly easy for real commenters).</description>
		<content:encoded><![CDATA[<p><strong>Michael</strong> - I&#8217;m still using the Wordpress inline editor, but it&#8217;s only for lack of an alternative I like enough to stick with.  I&#8217;m waiting for Ecto and Mars Edit to merge into a single, glorious, application.</p>
<p><strong>Marco</strong> - That plugin looks interesting, I may try it out.  The reason I use the plugin I do is because it&#8217;s only supposed to challenge spam bots with the CAPTCHA text, and not the average user.  Supposedly giving the best of both worlds (i.e. making it very difficult for the spam bots, while still being seamlessly easy for real commenters).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Ruelicke.net</title>
		<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/comment-page-1/#comment-17840</link>
		<dc:creator>Marco Ruelicke.net</dc:creator>
		<pubDate>Sat, 12 Jan 2008 15:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/#comment-17840</guid>
		<description>hm...about that plugin, maybe you give &lt;a href="http://www.theblog.ca/anti-spam" rel="nofollow"&gt;Peter's Custom Anti-Spam image&lt;/a&gt; a try. I used on my blog for quite some time but don't use it any longer as I trust Askimet. Another blog of mine is still using it though.</description>
		<content:encoded><![CDATA[<p>hm&#8230;about that plugin, maybe you give <a href="http://www.theblog.ca/anti-spam" rel="nofollow">Peter&#8217;s Custom Anti-Spam image</a> a try. I used on my blog for quite some time but don&#8217;t use it any longer as I trust Askimet. Another blog of mine is still using it though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Martin</title>
		<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/comment-page-1/#comment-17826</link>
		<dc:creator>Michael Martin</dc:creator>
		<pubDate>Sat, 12 Jan 2008 13:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/#comment-17826</guid>
		<description>It's a shame the plugins ruined that on ya. (And I can't stand the WordPress Visual Editor. It's just a pain to write code with! xD )</description>
		<content:encoded><![CDATA[<p>It&#8217;s a shame the plugins ruined that on ya. (And I can&#8217;t stand the WordPress Visual Editor. It&#8217;s just a pain to write code with! xD )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/comment-page-1/#comment-17739</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Fri, 11 Jan 2008 23:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/#comment-17739</guid>
		<description>Thanks for the offer Marco, but I'm actually part way through doing it myself.  As you rightly pointed out, the subscribe to comments plugin is causing a few problems however the worse offender is the CAPTCHA plugin from &lt;a href="http://www.protectwebform.com/" rel="nofollow"&gt;ProtectWebForm&lt;/a&gt;.  I think it's one of the best plugins out there, but the code is really quite horrible, so it's taking longer than expected.  There's loads of incorrectly escaped characters and some sloppy HTML.  It's a shame because I LOVE the plugin.</description>
		<content:encoded><![CDATA[<p>Thanks for the offer Marco, but I&#8217;m actually part way through doing it myself.  As you rightly pointed out, the subscribe to comments plugin is causing a few problems however the worse offender is the CAPTCHA plugin from <a href="http://www.protectwebform.com/" rel="nofollow">ProtectWebForm</a>.  I think it&#8217;s one of the best plugins out there, but the code is really quite horrible, so it&#8217;s taking longer than expected.  There&#8217;s loads of incorrectly escaped characters and some sloppy HTML.  It&#8217;s a shame because I LOVE the plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Ruelicke.net</title>
		<link>http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/comment-page-1/#comment-17735</link>
		<dc:creator>Marco Ruelicke.net</dc:creator>
		<pubDate>Fri, 11 Jan 2008 22:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.oakinnovations.co.uk/blog/2007/12/22/why-are-plugins-and-tools-making-my-code-invalid/#comment-17735</guid>
		<description>I also had a lot of issues with plugins on my page. I'm using XHTML 1.0 Strict as I don't like 1.1 much, especially as there are some browsers which have issues with 1.1....

Anyway, first of all I'm using &lt;a href="http://wordpress.org/extend/plugins/share-this/" rel="nofollow"&gt;ShareThis&lt;/a&gt; instead of AddThis. I had AddThis at first but I got tired of it and ShareThis behaves valid with my template, without having to apply an own fix. Maybe it is worth trying for you. :)

Oh, yes, I got only one bookmark button (which is still generated by addthis) in the sidebar and it behaves valid...

GoogleAdsense....well...I see it this way:
These days many people are using AdBlockers and are most likely blocking the Google Ad. That's why I don't consider the ad as a part of the site, especially as it is included and generated with JavaScript.

The Wordpress' Rich Text Editor is something I don't use at all. I prefer seeing the code, ensuring validity right from the beginning of typing an article.

Other than that I only have/had a few plugins which required my helping hands to get my blog valid again. One of the is "Subscribe to Comments", just place a whitespace entity and a closing p tag in front of that HTML code and an opening p tag + whitespace after the HTTML code you find in the plugin. Only someone who really views the source may discover this "walkaround" ;)

If you don't mind I had a look at your source code and got a few fix recommendations for this page. If you are interested I will write them in an email as a comment is not a good place to share such fixes, especially if the one or the other tag may be stripped away or used in the comment, breaking things even worse :)</description>
		<content:encoded><![CDATA[<p>I also had a lot of issues with plugins on my page. I&#8217;m using XHTML 1.0 Strict as I don&#8217;t like 1.1 much, especially as there are some browsers which have issues with 1.1&#8230;.</p>
<p>Anyway, first of all I&#8217;m using <a href="http://wordpress.org/extend/plugins/share-this/" rel="nofollow">ShareThis</a> instead of AddThis. I had AddThis at first but I got tired of it and ShareThis behaves valid with my template, without having to apply an own fix. Maybe it is worth trying for you. <img src='http://www.oakinnovations.co.uk/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Oh, yes, I got only one bookmark button (which is still generated by addthis) in the sidebar and it behaves valid&#8230;</p>
<p>GoogleAdsense&#8230;.well&#8230;I see it this way:<br />
These days many people are using AdBlockers and are most likely blocking the Google Ad. That&#8217;s why I don&#8217;t consider the ad as a part of the site, especially as it is included and generated with JavaScript.</p>
<p>The Wordpress&#8217; Rich Text Editor is something I don&#8217;t use at all. I prefer seeing the code, ensuring validity right from the beginning of typing an article.</p>
<p>Other than that I only have/had a few plugins which required my helping hands to get my blog valid again. One of the is &#8220;Subscribe to Comments&#8221;, just place a whitespace entity and a closing p tag in front of that HTML code and an opening p tag + whitespace after the HTTML code you find in the plugin. Only someone who really views the source may discover this &#8220;walkaround&#8221; <img src='http://www.oakinnovations.co.uk/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>If you don&#8217;t mind I had a look at your source code and got a few fix recommendations for this page. If you are interested I will write them in an email as a comment is not a good place to share such fixes, especially if the one or the other tag may be stripped away or used in the comment, breaking things even worse <img src='http://www.oakinnovations.co.uk/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.492 seconds -->
