I did check permissions etc to start off with but that wasn’t the issue, however i’ve solved the prob - one of the directories i was uploading onto the assets/images/ directory was named thus: e&u
I changed it to this: e_u
and solved the prob.
ampersand is obviously a reserved or inappropriate character for this directory, and probably others. Live and learn i guess.
Thanks for the help
Quote from: rootsdiv at Oct 27, 2007, 07:29 AM...
Incidentally, the site is running on a 1and1 server with php 4.4.7 and register_globals ON (i can’t change this).
You can run PHP5 on 1and1 with register_globals OFF (by default) by adding a few lines to your .htaccess:
# Use PHP 5 for this site
AddType x-mapp-php5 .php
Standard Disclaimer
I could be totally wrong.
Is this method absolutely bullet-proof?
Well I’m not sure what defines "bulletproof" but it works for me. You can
read their FAQ for more details if you like.
Standard Disclaimer
I could be totally wrong.
I asked one of their techies a while ago about this and he was really vague and made it sound as though this .htaccess command only ’emulates’ php5 and reg_glob OFF, which seems like ’papering over the cracks’ to me and possibly not a proper fix for xss attacks. Basically he left me in doubt about how secure the whole setup is and i wonder if a talented script-kiddie could find a workaround with the .htaccess fix.
however, from the link in your message it does appear that php5 is actually implemented with the .htaccess call
I have used the .htaccess trick to use php5 on my server for a long time. It worked great, we never had any problems. Now we reversed it, where php5 is the default and 4 is available with the .php4 extension.
This does not emulate php5, what this means is that you have both 4 and 5 available. 4 is the default and 5 needs to use .php5 extension. The .htaccess maps the php5 extension to us .php extension thus making it the default.