<?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: Remove the Website Field From the Comment Form</title>
	<atom:link href="http://www.optiniche.com/blog/261/comment-template-mod/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.optiniche.com/blog/261/comment-template-mod/</link>
	<description>Helping You To Optimize and Monetize Your WordPress Niche Blog</description>
	<lastBuildDate>Sat, 17 Sep 2011 14:31:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kaifu Computing</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-90781</link>
		<dc:creator>Kaifu Computing</dc:creator>
		<pubDate>Wed, 16 Jun 2010 10:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-90781</guid>
		<description>I agree with Yuki, checking to see if either http:// or https:// exists in the website field is a neater solution.

However entirely removing the field is a perfectly valid way to fix the problem, and as you say, websites with readership who are not tech savvy will more often than not leave the field blank anyway.</description>
		<content:encoded><![CDATA[<p>I agree with Yuki, checking to see if either http:// or https:// exists in the website field is a neater solution.</p>
<p>However entirely removing the field is a perfectly valid way to fix the problem, and as you say, websites with readership who are not tech savvy will more often than not leave the field blank anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kwika</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-90362</link>
		<dc:creator>Kwika</dc:creator>
		<pubDate>Mon, 18 Jan 2010 07:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-90362</guid>
		<description>I wonder if removing the URL field would reduce the amount of comment spam. It would certainly manual spamming but how about those scripts they are using.</description>
		<content:encoded><![CDATA[<p>I wonder if removing the URL field would reduce the amount of comment spam. It would certainly manual spamming but how about those scripts they are using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Kumar</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-89024</link>
		<dc:creator>Jay Kumar</dc:creator>
		<pubDate>Sun, 12 Oct 2008 04:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-89024</guid>
		<description>A neat solution for the problem that was bugging me for some time.  I run the website of a professional organization and many members have asked me what to write in the Website field. I used to tell them to leave it blank.

I was thinking of adding (optional, you may leave it blank) next to Website. As my members don&#039;t have their own websites, removing the field is ideal for me.

Thanks.</description>
		<content:encoded><![CDATA[<p>A neat solution for the problem that was bugging me for some time.  I run the website of a professional organization and many members have asked me what to write in the Website field. I used to tell them to leave it blank.</p>
<p>I was thinking of adding (optional, you may leave it blank) next to Website. As my members don&#8217;t have their own websites, removing the field is ideal for me.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markov</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-88808</link>
		<dc:creator>markov</dc:creator>
		<pubDate>Wed, 16 Jul 2008 15:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-88808</guid>
		<description>actually i&#039;ve commented out the email and website fields. the result is an error message that says

Error: please fill the required fields (name, email).

now what?</description>
		<content:encoded><![CDATA[<p>actually i&#8217;ve commented out the email and website fields. the result is an error message that says</p>
<p>Error: please fill the required fields (name, email).</p>
<p>now what?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-88383</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Wed, 26 Mar 2008 01:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-88383</guid>
		<description>I like it, a very simple fix. Of course, we could regex it or something similar, but if you just want to hide the field, this works great!</description>
		<content:encoded><![CDATA[<p>I like it, a very simple fix. Of course, we could regex it or something similar, but if you just want to hide the field, this works great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a.erol</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-88138</link>
		<dc:creator>a.erol</dc:creator>
		<pubDate>Mon, 11 Feb 2008 03:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-88138</guid>
		<description>Better to have there a website name as default! So if we commenters want to change it, we can, otherwise, we will leave it unchanged!</description>
		<content:encoded><![CDATA[<p>Better to have there a website name as default! So if we commenters want to change it, we can, otherwise, we will leave it unchanged!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuki</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-87971</link>
		<dc:creator>Yuki</dc:creator>
		<pubDate>Sun, 13 Jan 2008 18:46:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-87971</guid>
		<description>You can leave &quot;Website&quot; field, but just check if it contains &quot;http://&quot; or not. It&#039;s a more correct way, I think.</description>
		<content:encoded><![CDATA[<p>You can leave &#8220;Website&#8221; field, but just check if it contains &#8220;http://&#8221; or not. It&#8217;s a more correct way, I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wordpress php freak</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-85048</link>
		<dc:creator>wordpress php freak</dc:creator>
		<pubDate>Tue, 13 Nov 2007 12:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-85048</guid>
		<description>I think leaving a website is not a bad option to have. It encourages people specially who have blog to pass sometime valuable comments about your site.</description>
		<content:encoded><![CDATA[<p>I think leaving a website is not a bad option to have. It encourages people specially who have blog to pass sometime valuable comments about your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teli Adlam</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-82468</link>
		<dc:creator>Teli Adlam</dc:creator>
		<pubDate>Mon, 14 May 2007 22:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-82468</guid>
		<description>Hi Eric,
In general, &lt;strong&gt;I agree with you&lt;/strong&gt;. However, to accomplish the checks necessary would require far more tweaking and coding (which could possibly involve modifying core files) than the simple fix of removing the URL option and in some cases it would be overkill, plus it wouldn&#039;t account for the people who put in random URLs (e.g. google.com, msn.com, aol.com, &amp; so forth).

Removing the URL field isn&#039;t a new idea; certain publications that don&#039;t warrant a majority of their users leaving a link will remove the option, for instance &lt;a href=&quot;http://runway.blogs.nytimes.com/2007/05/10/the-pillar-isabella-blow/&quot;&gt;The New York Times blogs&lt;/a&gt;, without adversely impacting the interaction of their readership. 

For the blogs that don&#039;t need to worry about such a problem, URL checking/field removal isn&#039;t necessary. Using this one as an example, I leave it intact because a majority of the commenters will understand that it&#039;s optional and it&#039;s &lt;em&gt;extremely rare&lt;/em&gt; that I receive a gibberish URL (that isn&#039;t attached to a spam comment). :)

~ Teli</description>
		<content:encoded><![CDATA[<p>Hi Eric,<br />
In general, <strong>I agree with you</strong>. However, to accomplish the checks necessary would require far more tweaking and coding (which could possibly involve modifying core files) than the simple fix of removing the URL option and in some cases it would be overkill, plus it wouldn&#8217;t account for the people who put in random URLs (e.g. google.com, msn.com, aol.com, &#038; so forth).</p>
<p>Removing the URL field isn&#8217;t a new idea; certain publications that don&#8217;t warrant a majority of their users leaving a link will remove the option, for instance <a href="http://runway.blogs.nytimes.com/2007/05/10/the-pillar-isabella-blow/">The New York Times blogs</a>, without adversely impacting the interaction of their readership. </p>
<p>For the blogs that don&#8217;t need to worry about such a problem, URL checking/field removal isn&#8217;t necessary. Using this one as an example, I leave it intact because a majority of the commenters will understand that it&#8217;s optional and it&#8217;s <em>extremely rare</em> that I receive a gibberish URL (that isn&#8217;t attached to a spam comment). <img src='http://www.optiniche.com/blog/0/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>~ Teli</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Curtis</title>
		<link>http://www.optiniche.com/blog/261/comment-template-mod/#comment-82467</link>
		<dc:creator>Erik Curtis</dc:creator>
		<pubDate>Mon, 14 May 2007 19:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.optiniche.com/blog/261/comment-template-mod/#comment-82467</guid>
		<description>I would prefer some logic in the code to look at the characters in the field, then varify that they contain one of the valid endings to a domain name. For examlple, it must contain .com, .net, .org, ..ect.

A list of valid domain suffix can be found at http://www.norid.no/domenenavnbaser/domreg.html</description>
		<content:encoded><![CDATA[<p>I would prefer some logic in the code to look at the characters in the field, then varify that they contain one of the valid endings to a domain name. For examlple, it must contain .com, .net, .org, ..ect.</p>
<p>A list of valid domain suffix can be found at <a href="http://www.norid.no/domenenavnbaser/domreg.html" rel="nofollow">http://www.norid.no/domenenavnbaser/domreg.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

