<?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"
	>
<channel>
	<title>Comments on: WordPress 1.5.1.3 Security Update</title>
	<atom:link href="http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/</link>
	<description>Philippines, Technology News &#38; Reviews</description>
	<pubDate>Tue, 02 Dec 2008 06:54:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Wordpress Exploit - SEO Blogs Targeted - &#171; Speaking Freely</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-113539</link>
		<dc:creator>Wordpress Exploit - SEO Blogs Targeted - &#171; Speaking Freely</dc:creator>
		<pubDate>Mon, 15 Jan 2007 23:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-113539</guid>
		<description>[...] http://www.yugatech.com/blog/?p=212 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.yugatech.com/blog/?p=212" rel="nofollow">http://www.yugatech.com/blog/?p=212</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markku</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1861</link>
		<dc:creator>markku</dc:creator>
		<pubDate>Mon, 15 Aug 2005 02:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1861</guid>
		<description>You mean we have register_globals turned on at ploghost? It's sad that other developers simply ignore safe programming practices to allow their apps to run with the register_globals directive set to off. It doesn't really take much to code that way.

Another WP update? It's nice to see the community responding swiftly. :)</description>
		<content:encoded><![CDATA[<p>You mean we have register_globals turned on at ploghost? It&#8217;s sad that other developers simply ignore safe programming practices to allow their apps to run with the register_globals directive set to off. It doesn&#8217;t really take much to code that way.</p>
<p>Another WP update? It&#8217;s nice to see the community responding swiftly. <img src='http://www.yugatech.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaypee</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1858</link>
		<dc:creator>Jaypee</dc:creator>
		<pubDate>Sun, 14 Aug 2005 22:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1858</guid>
		<description>i've upgraded mine to 1.5.2 :D</description>
		<content:encoded><![CDATA[<p>i&#8217;ve upgraded mine to 1.5.2 <img src='http://www.yugatech.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Limpag</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1857</link>
		<dc:creator>Max Limpag</dc:creator>
		<pubDate>Sun, 14 Aug 2005 21:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1857</guid>
		<description>Yuga,
WordPress released version 1.5.2 just a few minutes after I did the fixes :-( . The update to my, my wife's and our Newsletter Solutions blogs went smoothly, though. Again, thanks for the warning although i wish I had procrastinated longer (at least in time for the release announcement :-) )

Max</description>
		<content:encoded><![CDATA[<p>Yuga,<br />
WordPress released version 1.5.2 just a few minutes after I did the fixes <img src='http://www.yugatech.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> . The update to my, my wife&#8217;s and our Newsletter Solutions blogs went smoothly, though. Again, thanks for the warning although i wish I had procrastinated longer (at least in time for the release announcement <img src='http://www.yugatech.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> )</p>
<p>Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kates</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1856</link>
		<dc:creator>Kates</dc:creator>
		<pubDate>Sun, 14 Aug 2005 20:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1856</guid>
		<description>Apparently, they forgot to change the version number in the headers. Mine still sports the version 1.5.1.3. I leave that for stats. hehehe</description>
		<content:encoded><![CDATA[<p>Apparently, they forgot to change the version number in the headers. Mine still sports the version 1.5.1.3. I leave that for stats. hehehe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon Kilat ::: The Cybercafe Experiments &#187; Blog Archive &#187; Updating WordPress, installing Serendipity</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1854</link>
		<dc:creator>Leon Kilat ::: The Cybercafe Experiments &#187; Blog Archive &#187; Updating WordPress, installing Serendipity</dc:creator>
		<pubDate>Sun, 14 Aug 2005 19:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1854</guid>
		<description>[...] 1 Ambot Ah!: Yugatech [...]</description>
		<content:encoded><![CDATA[<p>[...] 1 Ambot Ah!: Yugatech [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Limpag</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1853</link>
		<dc:creator>Max Limpag</dc:creator>
		<pubDate>Sun, 14 Aug 2005 18:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1853</guid>
		<description>Yuga,

Thanks for the warning. 

Max</description>
		<content:encoded><![CDATA[<p>Yuga,</p>
<p>Thanks for the warning. </p>
<p>Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaypee</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1851</link>
		<dc:creator>Jaypee</dc:creator>
		<pubDate>Sun, 14 Aug 2005 13:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1851</guid>
		<description>i tried to upload the new wp-settings.php file and got this error message - 
Parse error: parse error, unexpected T_LNUMBER in /home/prolifik/public_html/blog/wp-settings.php on line 91</description>
		<content:encoded><![CDATA[<p>i tried to upload the new wp-settings.php file and got this error message -<br />
Parse error: parse error, unexpected T_LNUMBER in /home/prolifik/public_html/blog/wp-settings.php on line 91</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vern</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1850</link>
		<dc:creator>vern</dc:creator>
		<pubDate>Sun, 14 Aug 2005 13:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1850</guid>
		<description>Yeah they say that, but then their instructions say

"then simply transfer the new version to the /wp-includes/ directory on your site."

People who follow their instructions word for word will run into obvious problems.</description>
		<content:encoded><![CDATA[<p>Yeah they say that, but then their instructions say</p>
<p>&#8220;then simply transfer the new version to the /wp-includes/ directory on your site.&#8221;</p>
<p>People who follow their instructions word for word will run into obvious problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaypee</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1849</link>
		<dc:creator>Jaypee</dc:creator>
		<pubDate>Sun, 14 Aug 2005 13:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1849</guid>
		<description>same goes for me..my wp-settings.php file is found in the root folder and not inside the wp-includes folder.</description>
		<content:encoded><![CDATA[<p>same goes for me..my wp-settings.php file is found in the root folder and not inside the wp-includes folder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yuga</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1848</link>
		<dc:creator>yuga</dc:creator>
		<pubDate>Sun, 14 Aug 2005 13:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1848</guid>
		<description>wp-includes/settings.php is mentioned as the back-up. :)</description>
		<content:encoded><![CDATA[<p>wp-includes/settings.php is mentioned as the back-up. <img src='http://www.yugatech.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vern</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1847</link>
		<dc:creator>vern</dc:creator>
		<pubDate>Sun, 14 Aug 2005 12:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1847</guid>
		<description>wp-settings.php is actually in the Wordpress root (/) and not in wp-includes/. At least it is on mine.</description>
		<content:encoded><![CDATA[<p>wp-settings.php is actually in the Wordpress root (/) and not in wp-includes/. At least it is on mine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: plogHost Weblog &#187; WordPress 1.5.1.3 Security Update</title>
		<link>http://www.yugatech.com/blog/wordpress/wordpress-1513-security-update/#comment-1846</link>
		<dc:creator>plogHost Weblog &#187; WordPress 1.5.1.3 Security Update</dc:creator>
		<pubDate>Sun, 14 Aug 2005 11:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.yugatech.com/blog/?p=212#comment-1846</guid>
		<description>[...] For all those with Wordpress installed on their account, please follow these instructions. [...]</description>
		<content:encoded><![CDATA[<p>[...] For all those with Wordpress installed on their account, please follow these instructions. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
