settings.php / 644 / Bug or Error...

yellowboyee

Hi,

After deleting the setup directory for a fresh install, I updated the file permissions for the settings.php file to 644 (using FileZilla) - but the following error message is still being displayed on the admin side:

Please change permission of config file (settings.php) to remove write access. e.g chmod 644 settings.php

Everything else is working fine. Is there any way to fix that?

Thanks.

scottro

Depending on your host it may look like you changed the permissions through Filezilla but it actually isn't, if you can't get to the command line and manually run chmod 644 settings.php then I would check with your host to make sure that the permission is actually 644. Also double check to make sure you have the correct file, just in case. ;)

Katanshin

I get the same message - I have no command line access but the built in file browser allows me to chmod etc through a web interface, as well through ftp etc and the perms are apparently set to 644

I'm checking osticketinstalldir/settings.php too.

User error ;) or something more sinister? :

mslisalisa

I get the same message - I have no command line access but the built in file browser allows me to chmod etc through a web interface, as well through ftp etc and the perms are apparently set to 644
I'm checking osticketinstalldir/settings.php too.
User error ;) or something more sinister? :

I am getting the same message too. I have changed the file permission to 644 with Filezilla and from the hosting account cpanel. But still get the message:

"Please change permission of config file (settings.php) to remove write access. e.g chmod 644 settings.php"

What's the deal?

lead_head

Just thought I would chime in here with some advice. If you are using filezilla to change your write settings you must make sure all write boxes are clear. Make sure they do not have a green square inside. You have to click it once to clear the x then again to clear the green box.

Kenneth

Here

http://osticket.com/forums/showpost.php?p=9939&postcount=7(http://osticket.com/forums/showpost.php?p=9939&postcount=7)

I might just go create a wiki entry for this as I had the same Problem!

-Ken

mslisalisa

Here
http://osticket.com/forums/showpost.php?p=9939&postcount=7(http://osticket.com/forums/showpost.php?p=9939&postcount=7)
I might just go create a wiki entry for this as I had the same Problem!
-Ken

I clicked on the link above, read over it, tried it and now i have a new error on my site...geez.!

Parse error: syntax error, unexpected $end in /home/energy/public_html/support/scp/admin.php on line 708

Kenneth

That means you messed up when copying the code.

Try again and make sure you get everything and that you only replace what you are supposed to.

-Ken

gabberkopf

I have the same problem since I updated to RC5. I changed permissions through filezilla and also checked directly through the admin panel from my host. Permissions are correct but still this message in the admin panel of os ticket.

PRedmond

I found that 644 still displayed the error. I think I had to set it to 444 before the error would go away.

If you cannot cmod to 444, maybe try contacting your webhost, and ask them to do it for you. Or you could reove the error using the link above, or just ignore it...

awells527

Chmod to 444 Instead

I had the same problem, and chmodding (is that a word?) to 444 fixes the problem. I'm guessing it's because I have (suPHP) running on my server, and that means that my PHP scripts run as my web account's user, and not www-data. So, because the script can write to the settings file, it assumes that the file permissions is insecure when it is not.

tcsllc

location of settings file

just to be 110% sure. what is the location of the settings file that needs to be changed?

scottro

just to be 110% sure. what is the location of the settings file that needs to be changed?

include/settings.php

For instance my DocumentRoot is /var/www/tickets, so in my case I could do the following

cd /var/www/tickets

chmod 444 include/settings.php

That will take care of the issue.