By vanpepep on

After switching to a Dutch translation (which seems to work), I get the following error message:

"Het bestand kon niet aangemaakt worden"

Which means "The file cannot be created"

The Drupal log (version 6.4) shows the following 3 entries;

/fopen() [<a href='function.fopen'>function.fopen</a>]: SAFE MODE
Restriction in effect. The script whose uid is 10019 is not allowed to
access
/var/www/vhosts/treehoppers.be/httpdocs/sites/default/files/tmp/fileWANyLT
owned by uid 48/ in
//var/www/vhosts/treehoppers.be/httpdocs/includes/file.inc/ on line /757/.

/open(/var/www/vhosts/treehoppers.be/httpdocs/sites/default/files/tmp/fileWANyLT)
[<a href='function.fopen'>function.fopen</a>]: failed to open stream:
Success/ in //var/www/vhosts/treehoppers.be/httpdocs/includes/file.inc/
on line /757/.

An error occurred during creation of the JavaScript translation file for
the language /Nederlands/.

The /sites/default/files/tmp directory, and the files it contains are owned by user Apache, group Apache, and are both writeable. The directory contains files with length 0.

The switch to Dutch works fine on my own (windows) machine.

I suspect some problem with the webserver/php setup, but my hosting company (eTech media in Belgium - who claim to be Drupal experts) has been unresponsive.

I'm especially baffled by the script uid 10019 and the file uid of 49. What does that mean? Can anybody help? Is there a workaround?

thanks

Philippe Vanpeperstraete

⋅ Categories: Drupal 6.x

Comments

lasuax’s picture

lasuax commented

i had the same problem with you. just delete your languages folder created by the drupal and re-create it manually. after all chmod your new languages folder to 777.

alpirrie’s picture

alpirrie commented

Cheers!

auris’s picture

auris commented

What did you do exactly? I have the same problem.

alpirrie’s picture

alpirrie commented

I followed lasuax's advice:
The set up creates a folder called sites/default/files/languages. The permissions of this automatically created folder seem to cause problems, so if you use your ftp access or admin privileges on your server to delete this folder and create it again and then set its permissions to full read/write access the problem disappears.

zoia’s picture

zoia commented

ty i had the same problem described here http://drupal.org/node/505070#comment-1934396 and this solution worked for me