Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#16 2015-06-20 20:05:54
- sunmaker
- Member
- From: Washington DC
- Registered: 2005-01-04
- Posts: 40
Re: 755 'not writable'
This old problem has still got hold of us as we try to update our TXP site to 4.5.7.
Can’t write to /public/images and /public/files unless these are set to 777.
Currently, /public/images and /public/files are 775, which does not work despite the hosting company recommending 775 or 755 for folders. 755 also makes no difference. Only 777 will enable these folders to pass the pre-flight check.
Virtually all of the folders in the site have group and owner of 108243, which appears to be the equivalent to group “web” as the hosting company recommends.
Note also that the tmp folder automatically found by TXP is not in the textpattern folder. According to the TXP instructions the tmp folder used should be in the textpattern folder. But our installation found it in /home/tmp instead.
- – -
Textpattern version: 4.5.7 (r5900)
Last update: 2015-06-20 13:28:43/2015-06-20 13:25:41
Document root: /home/public/ (/home/public)
$path_to_site: /home/public
Textpattern path: /home/public/textpattern
Permanent link mode: messy
upload_tmp_dir: /tmp
Temporary directory path: /home/tmp
Site URL: kimelli.nfshost.com
PHP version: 5.5.26-nfsn1
GD Graphics Library: bundled (2.1.0 compatible); supported formats: GIF, JPG, PNG.
Server TZ: UTC
Server local time: 2015-06-20 19:53:29
DST enabled?: 0
Automatically adjust DST setting?: 0
Time zone: America/New_York (-18000)
MySQL: 5.3.12-MariaDB
Locale: en_US.UTF-8
Server: Apache
PHP server API: NFGI
RFC 2616 headers:
Server OS: FreeBSD 10.1-RELEASE-p8
Active plugins: adi_gps-0.2, upm_date_archive-0.2.5
Admin-side theme: hive 4.5.7
Pre-flight check:
------------------------
Image directory is not writable: /home/public/images
File directory path is not writable: /home/public/files
------------------------
<code>.htaccess</code> file contents:
------------------------
#DirectoryIndex index.php index.html
#Options +FollowSymLinks
#Options -Indexes
#ErrorDocument 403 default
<IfModule mod_rewrite.c>
RewriteEngine On
#RewriteBase /relative/web/path/
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+) - [PT,L]
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*) index.php
RewriteCond %{HTTP:Authorization} !^$
RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization}]
</IfModule>
#php_value register_globals 0
# SVG
AddType image/svg+xml svg svgz
AddEncoding gzip svgz
------------------------All boundaries are for practical purposes only.
Offline
Re: 755 'not writable'
sunmaker wrote #291736:
This old problem has still got hold of us as we try to update our TXP site to 4.5.7.
Can’t write to /public/images and /public/files unless these are set to 777.
Currently, /public/images and /public/files are 775, which does not work despite the hosting company recommending 775 or 755 for folders. 755 also makes no difference. Only 777 will enable these folders to pass the pre-flight check.
Virtually all of the folders in the site have group and owner of 108243, which appears to be the equivalent to group “web” as the hosting company recommends.
Note also that the tmp folder automatically found by TXP is not in the textpattern folder. According to the TXP instructions the tmp folder used should be in the textpattern folder. But our installation found it in /home/tmp instead.
I had a similar issue some years ago with the host I still use. Nothing would work unless folder and permissions were set to 777 despite the host’s recommendation for 755. When I asked them why only 777 would work for my TXP installations they told me that they didn’t support third party applications.Inevitably a bunch of my sites were hacked and then they sat up an paid attention. It turned out that it was a configuration issue that revolved around which process owned which folders. They moved all my sites to a another server that didn’t have those issues and that solved the problem. I was able to give all the folders a more secure set of permissions and we have never looked back.
It was all some time ago and I can’t remember the full detail. The point though is, that just because a host recommends 775 or 755 don’t leave it there, challenge them on why those permissions don’t work for your TXP installation. At the time, I knew I was on pretty solid ground because I transferred the hacked sites (with the hacks excised) to another host for a while and was able right away to apply a sensible set of permissions.
Last edited by joebaich (2015-06-20 20:41:19)
Offline
Re: 755 'not writable'
^ What Joe says… and if they don’t fix it, switch to a different webhost.
Offline