More than one way to skin a cat: this is one way. It's not necessarily the best, just an option.
Aims:
To avoid the problem with ~username ending up in PHP variables and causing problems with POSTs, etc. - and avoid the ~username appearing in the url after you POST.
To avoid the need for more than one custom php.ini file to cover all folders.
(A side effect is that sites will run without resetting permissions on php files, though they should still be reset for security.)
Method:
This is a Marmite method (some won't like it at all and it may not work perfectly for every situataion). It uses a wrapper script to reset certain PHP variables. The php.ini for the wrapper then covers all PHP files in all folders.
First create a wrapper script:
<?php
$_ENV["SCRIPT_NAME"]=$PHP_SELF=$_SERVER['PHP_SELF']=$_SERVER["SCRIPT_NAME"]=$_SERVER["REQUEST_URI"];
$_ENV["SCRIPT_FILENAME"]=$_SERVER["SCRIPT_FILENAME"]='/files/homeX/username'.$_SERVER["REQUEST_URI"];
ereg('^/~username(.*)/([^/]*\.php)$', $_ENV["REDIRECT_URL"], $wrap_url);
chdir('/share/storage/0X/us/username'.$wrap_url{1});
include $wrap_url{2};
?>
Edit the above, replacing "/files/homeX/username" in line 2, "username" in line 3 and "/share/storage/0X/us/username" in line 4. "username" is your username and the other strings may be found by placing a <a href="http://community.plus.net/forum/index.php/topic,83568.msg696223.html#msg696223">php.ini file</a> along side a phpinfo() file in your root folder.
<?php
phpinfo();
?>
Chmod the phpinfo file 0700 and call it in a browser. The first string appears under PHP Variables, against _SERVER["SCRIPT_FILENAME"] (just the bit up to username). The second will appear at the top, against "Loaded Configuration File" (again, just the bit up to username).
Name the file "phpwrapper.php", place it in your root folder alongside the php.ini file and chmod it 0700.
Then create a .htaccess file
RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+[^/])$ $1/ [R,L]
RewriteCond %{REQUEST_URI} \.php$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_URI} !^/~username/phpwrapper\.php
RewriteRule .* phpwrapper.php
replace "username" and place the file in your root folder.
Call the phpinfo file again and notice that the relevant PHP variables have changed. Place the phpinfo file in another folder, call it and notice that register_globals is still off.
The rewrite rules in .htaccess can be combined with others. For instance, to run a Wordpress blog from a subfolder, while giving the appearance that it's in the root, you could use something like:
RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+[^/])$ $1/ [R,L]
RewriteCond %{HTTP_HOST} ^ccgi\.yourdomain\.co\.uk$ [NC]
RewriteCond %{REQUEST_URI} !^/~username/wordpress/
RewriteRule (.*) /wordpress/$1
RewriteCond %{REQUEST_URI} \.php$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_URI} !^/~username/phpwrapper\.php
RewriteRule .* phpwrapper.php
and change the Wordpress address to
http://ccgi.yourdomain.co.uk in Settings.
If your site uses .htaccess files in subfolders then the wrapper rewrites will also need to be added to those files, with the wrapper referenced as ../phpwrapper.php (adding more ../ for each folder level down).
Ok, I hope that hasn't just confused things. It's only an option.
Gabe
