Hi I have installed Drupal 5 & 6 previously with alternative themes. I have a new shared webhost for a new project On this host was 6.13; I have also tried 6.17 and 7.0alpha6. When installing or configuring a theme I get a load of errors which look like it is because Drupal is using absolute file paths rather than relative to the web-root Does anyone agree with this from the following. I have access to the directories in question and I can have Drupal upload a logo or favicon. I cannot however select a contributed theme or configure the colours of a theme When changing Bartik to Plum on Drupal 7 the following errors are generated Error message

The specified file themes/bartik/logo.png could not be copied, because the destination public:// color/bartik-1aa4743a/logo.png is not properly configured. This is often caused by a problem with file or directory permissions. The specified file temporary://filefxlLrD could not be copied, because the destination public:// color/bartik-1aa4743a/colors.css is not properly configured. This is often caused by a problem with file or directory permissions.

errors from Drupal 6.17 the installation works, but errors appear

warning: fopen() [function.fopen]: SAFE MODE Restriction in effect The script whose uid is 10302 is not allowed to access/var/www/vhosts/strongaccounting.co.uk/httpdocs/sites/default/files/tmp owned by uid 48 in/var/www/vhosts/strongaccounting.co.uk/httpdocs/includes/file.inc on ine 129 warning: fopen(sites/default/files/tmp/.htaccess) [function.fopen] failed to open stream: Success in/var/www/vhosts/strongaccounting.co.uk/httpdocs/includes/file.inc on ine 129 Security warning: Couldn't write .htaccess file. Please create a.htaccess file in your sites/default/files/tmp directory which contains the following lines: SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006 Options None Options +FollowSymLinks

Comments

damien tournoud’s picture

damien tournoud commented
Category: bug » support

The only thing you can do here is contact your host to have those permission issues fixed. You need to make sure that Drupal can write into both the "Filesystem directory" and the "Temporary directory".

richard.e.morton’s picture

richard.e.morton commented
Version: 6.17 » 7.x-dev
Category: support » feature

In Drupal 7; have Drupal only refer to filesystem paths relative to the installation directory in order to remove this issue from shared hosts.

damien tournoud’s picture

damien tournoud commented
Category: feature » support

I don't see why we should do that. We are already using a relative directory for the default file directory, and using sys_get_temp_dir() to automatically detect the temporary directory. The rest is misconfiguration of your host.

richard.e.morton’s picture

richard.e.morton commented
Category: support » bug

I had the host turn off php safe mode and the issue has gone away.
In the hosts opinion this should only be a temporary measure and I would tend to agree.
thoughts?

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Using safe_mode is simply a very bad idea. See http://php.net/manual/en/features.safe-mode.php

hernan_cemedete’s picture

hernan_cemedete commented

This is only a test

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Category: bug » support
Status: Active » Closed (works as designed)

Per #3 and #5.