<?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: bs-wp-noerrors: removing WordPress DB errors</title>
	<atom:link href="http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Как защитить свой блог на Wordpress: 12 незаменимых плагинов для защиты &#124; Pro Dengi blog &#124; Блог о Wordpress и заработке в интернете</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-17944</link>
		<dc:creator>Как защитить свой блог на Wordpress: 12 незаменимых плагинов для защиты &#124; Pro Dengi blog &#124; Блог о Wordpress и заработке в интернете</dc:creator>
		<pubDate>Sat, 16 Jan 2010 06:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-17944</guid>
		<description>[...] Сообщения об ошибках, как правило, содержат много полезной информации не только для вас, но и для желающих взломать наш сайт. Поэтому, лучше их отключить. Для отключения сообщений об ошибках удобно использовать плагин bs-wp-noerror. [...]</description>
		<content:encoded><![CDATA[<p>[...] Сообщения об ошибках, как правило, содержат много полезной информации не только для вас, но и для желающих взломать наш сайт. Поэтому, лучше их отключить. Для отключения сообщений об ошибках удобно использовать плагин bs-wp-noerror. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Безопасность WordPress. &#124; Блог Андрейда</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-9913</link>
		<dc:creator>Безопасность WordPress. &#124; Блог Андрейда</dc:creator>
		<pubDate>Tue, 15 Apr 2008 19:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-9913</guid>
		<description>[...] В сообщениях об ошибках порой содержится очень много полезной для злоумышленника информации. Плаггин забираем отсюда. [...]</description>
		<content:encoded><![CDATA[<p>[...] В сообщениях об ошибках порой содержится очень много полезной для злоумышленника информации. Плаггин забираем отсюда. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress 2.4 wird nicht erscheinen, stattdessen direkt Version 2.5 &#187; miradlo bloggt</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6305</link>
		<dc:creator>Wordpress 2.4 wird nicht erscheinen, stattdessen direkt Version 2.5 &#187; miradlo bloggt</dc:creator>
		<pubDate>Fri, 04 Jan 2008 14:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6305</guid>
		<description>[...] Aus Sicherheitsgr&#252;nden hatte ich au&#223;erdem zwischen den Versionen 2.3.1 und 2.3.2 noch das DB-Errors-Plugin installiert. Wenn solche Aktionen zwischendurch nicht n&#246;tig sind, dann warte ich doch ein [...]</description>
		<content:encoded><![CDATA[<p>[...] Aus Sicherheitsgr&#252;nden hatte ich au&#223;erdem zwischen den Versionen 2.3.1 und 2.3.2 noch das DB-Errors-Plugin installiert. Wenn solche Aktionen zwischendurch nicht n&#246;tig sind, dann warte ich doch ein [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonathon</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6278</link>
		<dc:creator>jonathon</dc:creator>
		<pubDate>Tue, 01 Jan 2008 17:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6278</guid>
		<description>will we be getting a update for this plug in anytime soon, thanks.</description>
		<content:encoded><![CDATA[<p>will we be getting a update for this plug in anytime soon, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharing my latest WordPress errors and new WordPress Version &#124; PhSoftware Programming Blog - PSPB</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6273</link>
		<dc:creator>Sharing my latest WordPress errors and new WordPress Version &#124; PhSoftware Programming Blog - PSPB</dc:creator>
		<pubDate>Mon, 31 Dec 2007 15:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6273</guid>
		<description>[...] possible Protection. For everyone who uses an earlier version, should run BlogSecurity&#8217;s bs-wp-noerrors to have this feature as [...]</description>
		<content:encoded><![CDATA[<p>[...] possible Protection. For everyone who uses an earlier version, should run BlogSecurity&#8217;s bs-wp-noerrors to have this feature as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogSecurity &#187; Blog Archive &#187; WP 2.3.2 Security Fixes</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6271</link>
		<dc:creator>BlogSecurity &#187; Blog Archive &#187; WP 2.3.2 Security Fixes</dc:creator>
		<pubDate>Mon, 31 Dec 2007 10:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6271</guid>
		<description>[...] WordPress have decided to turn off WordPress errors by default now. So, our bs-wp-noerrors plugin is deprecated but still useful for those of us who haven&#8217;t trusted WP 2.3 enough to [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress have decided to turn off WordPress errors by default now. So, our bs-wp-noerrors plugin is deprecated but still useful for those of us who haven&#8217;t trusted WP 2.3 enough to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ваш блог - могут взломать! &#124; AltBlog.ru</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6145</link>
		<dc:creator>Ваш блог - могут взломать! &#124; AltBlog.ru</dc:creator>
		<pubDate>Fri, 14 Dec 2007 16:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6145</guid>
		<description>[...] Часто встречаю блоги на которых по тем или иным причинам вылетают SQL-ошибки. Эти сообщения о SQL-ошибках надо отключать - читать. [...]</description>
		<content:encoded><![CDATA[<p>[...] Часто встречаю блоги на которых по тем или иным причинам вылетают SQL-ошибки. Эти сообщения о SQL-ошибках надо отключать &#8211; читать. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6108</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 11 Dec 2007 22:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6108</guid>
		<description>Thanks, that makes more sense. I have been looking at the WordPress files but I can&#039;t find why at the moment.</description>
		<content:encoded><![CDATA[<p>Thanks, that makes more sense. I have been looking at the WordPress files but I can&#8217;t find why at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6106</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Tue, 11 Dec 2007 19:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6106</guid>
		<description>Andrew, I initally used the init function, however, I think it gets overwritten during or after the query (atleast this is what happened during my tests), hence why I chose parse_query.</description>
		<content:encoded><![CDATA[<p>Andrew, I initally used the init function, however, I think it gets overwritten during or after the query (atleast this is what happened during my tests), hence why I chose parse_query.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/comment-page-1#comment-6104</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 11 Dec 2007 19:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/#comment-6104</guid>
		<description>I am curious about why there is a need to wait until the query has been parsed to turn the errors off.

You suggest that it should be off by default, would it make sense to turn it off using the init action instead? Possibly with a debug flag in the config file.</description>
		<content:encoded><![CDATA[<p>I am curious about why there is a need to wait until the query has been parsed to turn the errors off.</p>
<p>You suggest that it should be off by default, would it make sense to turn it off using the init action instead? Possibly with a debug flag in the config file.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
