At http://

I have the following messages:

"The CTools CSS cache directory, sites/default/files/ctools/css could not be created due to a misconfigured files directory. Please ensure that the files directory is correctly configured and that the webserver has permission to create directories.

warning: realpath() [function.realpath]: SAFE MODE Restriction in effect. The script whose uid/gid is 175774/175774 is not allowed to access /f5/
/public/sites/default/files/ctools owned by uid/gid 25000/25000 in /f5/
/public/includes/ on line 182."

I have tried many combinations of permissions using Ubuntu's gui, nautilus. The permissions seem to change but I'm not sure what I should have.

I don't really know what permissions or ownership should be assigned or how to do it.

Any suggestions?


islevegan’s picture

In the forums, someone suggested I do the following:

in /home/public chgrp web index.php

in /home/public/sites/default chgrp web files

I am no longer getting the error from Ctools, but I now get this:

warning: realpath() [function.realpath]: SAFE MODE Restriction in effect. The script whose uid/gid is 175774/25000 is not allowed to access /f5/
/tmp owned by uid/gid 0/175774 in /f5/
/public/includes/ on line 190.

merlinofchaos’s picture

Status: Active » Closed (won't fix)

Unfortunately I am unable to advise; individual servers have different methods of ensuring file permissions. You may need to ask your hosting company for information about how to do it. The information that the error provides is pretty complete, so anyone who understands how your server is configured should be able to tell you how to do the right thing.

Vc Developer’s picture

You have to give the group write permission for that folder. Only that folder!

Stomper’s picture

This error popped up for me when I recently transferred by website from my localhost to a live VPS.

This seemed to work for me in removing the error on the status report page, it now displays "exists" in nice and happy green.

I navigated to ctools css folder on my server and changed the folder permissions from "755" to "777". Is this how I should've set the file permissions?

Hope this helps someone

merlinofchaos’s picture

It needs to be writable by the webserver user. The best way is to make sure the folder is owned by the webserver user but that's not always possible if you're not root. So the next choice is 777.

Stomper’s picture

I'm on a VPS with full root access, is "777" still ideal and where specifically should it be applied?

merlinofchaos’s picture

If you have full root access, then ideally figure out the webserver user (often it's 'apache' but it varies from system to system) and use the command 'chown apache filename'.

Stomper’s picture

Oh, I may look further into that, but would permissions set to "644" be superior to "777"?

merlinofchaos’s picture

If the ownership is right, yes. Though you want 755 on directories and 644 on files.

Stomper’s picture

That's good to know, thanks for the general rule on permissions for directories and files.