<?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>WordPress Designpraxis Forum Tag: ownership</title>
<link>http://wpforum.designpraxis.at/</link>
<description>WordPress Designpraxis Forum Tag: ownership</description>
<language>en</language>
<pubDate>Tue, 07 Feb 2012 15:51:25 +0000</pubDate>

<item>
<title>bcking on "BackupWordPress 0.4.5 Permissions Problem"</title>
<link>http://wpforum.designpraxis.at/topic/backupwordpress-045-permissions-problem#post-365</link>
<pubDate>Wed, 28 Nov 2007 22:15:16 +0000</pubDate>
<dc:creator>bcking</dc:creator>
<guid isPermaLink="false">365@http://wpforum.designpraxis.at/</guid>
<description>&#60;p&#62;I have found through some testing that an ownership permissions problem causes BackupWordPress to create huge archives. I also found that when a backup is sized larger than the php.ini memory limit the process crashes with a php memory error.&#60;/p&#62;
&#60;p&#62;My server is running apache with user group and user name of the server apache:apache. The individual websites have their own names so files would normally be owned websitename:websitename with the exception of files uploaded or downloaded through the web interface. These files would be owned apache:apache. &#60;/p&#62;
&#60;p&#62;In the process of moving some directories between servers the /wp-content/uploads directory was reowned by websitename:websitename and permissions of rw-r--r-- and rw-rw-rw-. Under this circumstance tar archives had several files of the same name in sub directories under /wp-content/uploads/etc-etc-etc.&#60;/p&#62;
&#60;p&#62;The fix for both problems above was to change directory ownership to apache on /wp-content/uploads. I also changed the permissions to 666 on these files. My tar.gz went from 131 MB to 5 MB.&#60;/p&#62;
&#60;p&#62;I don't think the plugin should care about this ownership as both apache owned and websitename owned files are valid to view in a browser.
&#60;/p&#62;</description>
</item>

</channel>
</rss>

