<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Weblogtoolscollection News Topic: Claim your rights!</title>
<link>http://weblogtoolscollection.com/news/</link>
<description>Weblogtoolscollection News Topic: Claim your rights!</description>
<language>en</language>
<pubDate>Sun, 19 May 2013 16:25:21 +0000</pubDate>

<item>
<title>brut on "Claim your rights!"</title>
<link>http://weblogtoolscollection.com/news/topic/claim-your-rights#post-4342</link>
<pubDate>Sat, 18 Apr 2009 08:47:19 +0000</pubDate>
<dc:creator>brut</dc:creator>
<guid isPermaLink="false">4342@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;Have you ever found yourself in a situation where a web application or a WordPress plug-in created a folder or a file you couldn’t touch afterwards, not even to rename or delete? It happens more often then you might think, most of the times because a developer neglected to chmod newly created item to 666 after it was created. Which causes the same to remain property of the web server account and inaccessible to the ftp account one uses to work with files on a web server. More at &#60;a href=&#34;http://brut.bukve.net/?p=1033&#34; rel=&#34;nofollow&#34;&#62;http://brut.bukve.net/?p=1033&#60;/a&#62;
&#60;/p&#62;</description>
</item>

</channel>
</rss>