[Jordan]

As you may have noticed that in the early morning your site may have tossed up a 500 Internal Server error. This error is due in part to the re-addition of suPHP to the server. This prevents users from having folders that are using 777 permissions. This is dangerous as it can be rewritable by anyone that tries to attempt, and as such it can have server-wide issues.

This was in place prior to the migration however during the busy process it had been put on the backburner as our main concern was getting clients on our new server.

Most of you should see your sites back up and running with no issues. If you are receiving 500 Internal Server Errors you will either need to fix your permissions (CHMOD) or you may need to edit your .htaccess file as any kind of script changes will need to be put in your own php.ini file.

If you have any questions about this please reply to this thread or open up a support ticket.

Thanks!

[Sunny]

Does this mean we do not need to CHMOD folders to 777 any more? (That is, any script requiring a writeable folder will no longer need the folder to be CHMOD'd 777.)

AFAIK I am not receiving any 500 errors, but I have a folder that is still CHMOD'd to 777 and I was wondering if it was possible to change the permissions back to 755 and have it still work. :)

Thanks!