CHMOD Permissions

[GTB]

When you run the "File Permissions Checker", to check permissions in the admin section on directorys and files, and your asked to CHMOD all the PHP files in this directory to writable:

public_html/cache/lang_cache/en/

Should I change them to 777 or 666 on a Unix server. I'm taking about the "PHP" files in the "EN" directory.

[uberjon]

although this is not a support board. they should be set to 644 to keep them safe from malicious users. they should function properly at that setting. if not your web server is setup incorrectly.

[GTB]

although this is not a support board. they should be set to 644 to keep them safe from malicious users. they should function properly at that setting. if not your web server is setup incorrectly.

OK, sorry it's in the wrong section. But what you said cannot be right, as 644 is not a "world writable" CHMOD permission setting on a Unix/Linux server, they would have to be either 777 or 666. And if they are left as 644 "which they are as default" after a clean install. Every single PHP file in that folder shows as RED in the file permission checker page that needs to be writable.

[uberjon]

what?

you dont want some random person from the "world" to be able to "edit" a php file. if they can. you could wakeup one morning with an empty database...

only reason to need to chmod something. is if a script "you" are running "at that moment" needs write permission. such as when ipb install adds data to the conf_global.php file. then you chmod it to 777. after it is done. chmod it back to 644...

folders should be kept chmodded to 755 unless you need temp script write access. or once again. users can maliciously upload their own php scripts and run them from your server.


permission checker for what? the IPB install?

[AndyF]

There is a guide in the installation documents and also on over on IPSBeyond :)

[Mark]

uberjon, he is talking about the language files which must be writable otherwise certain features (well one feature: the language editor) won't work. Nor will the universal mod installer which many people use nowadays. And the file permisison checker (which is in the ACP) will bug you unless they're 777.

You should CHMOD them to 777 unless you have no intention of editting the language strings or installing mods. But in future ask at IPSBeyond.
666 might work - try it and see if the checker likes it - if not go for 777.

[GTB]

uberjon, he is talking about the language files which must be writable otherwise certain features (well one feature: the language editor) won't work. Nor will the universal mod installer which many people use nowadays. And the file permisison checker (which is in the ACP) will bug you unless they're 777.

You should CHMOD them to 777 unless you have no intention of editting the language strings or installing mods. But in future ask at IPSBeyond.

666 might work - try it and see if the checker likes it - if not go for 777.

That's correct, also I'll point out if you don't also change the CHMOD settings on the extra Plug-in files that go into this same directory, like the Gallery plug-in ones. You get an error when you try to access the Gallery after you've run the installer and it's installed - if the files that go in the same same directory from the gallery are not previously chmod to 666 before running the installer itself. It does in my case anyway!

All the files are showing as Green in the permission checker as 666 chmod, but they do also as 777 as well. I'm just wondering which way to go though. Keep them as 666 or change them to 777. What do you think?

[bfarber]

We don't check chmod - we check if they are writable. If you are running PHP as a fastcgi module it's quite probable your PHP process user and FTP user are the same, so the 666 might work. It's all relative. Really though, this sort of question is best left for IPS Beyond as others have pointed out, since we don't allow support-type topics here. :)