Thread

This question may be related to a resolved thread.

Hi! I just noticed a lot of files as 777 and found the related thread. Why EECMS 2.4 doesn’t fixed the wrong permissions of old files? Found the files this way was a scary experience.

And, more important, how do I set EECMS back to use 755 and 644 as permissions for my files and directories as was when I installed it the first time?

Thank you for your attention, guys!

Hello Robson,

I am sorry to hear you are running into this problem.

What I hear you saying is that you had some files on your server that were chmod 777. The ExpressionEngine update to 2.4 did not find and change the permissions of those files and you are wondering why. Is that correct?

If that is correct I have a few questions.

Where are these files located that have wide open permissions?

I have checked my 2.4 install and the files I upload are not chmod 777. Is it your experience that files you upload are set to 777?

Depending on where these files are, you can use an FTP program like FileZilla to set the permissions or if you have access to the shell on your web server, you can use the chmod command to change the permissions.

I hope this makes sense and that it helps. Once you clarify things for me, I should be able to offer more specific guidance.

Cheers,

Hi, Shane!

Please forgive for gave you so little details. I wrote the message in the heat of the moment.

The related thread is about EECMS 2.3 setting wrong permissions to the uploaded files and generated thumbnails. This bug was tracked as #17160 and it’s now fixed.

My first question is: Why the version 2.4 didn’t fix the permission of the already uploaded files, since the bug caused the mess? I already fixed the permissions, but I bet a lot of developers doesn’t even notice the issue.

And the second is: How can I change the EE setting back to use 755 and 644 as default permissions? I edited the constants.php file, but I need a better approach to the question. Is it possible to set the default permission at the config.php, at least?

Thank you! And, please, forgive my bad English.

Hello Robson Sobral,

Thank you for clarifying, I appreciate that.

Do not worry about your English, it’s just fine.

To answer your first question, we do not check for file perms in your image upload locations as a part of update process. Mostly because those permissions are entirely up to you. It’s much easier for a Systems Administrator to “chmod *” the files than for us to script that and assume everyone desires this change.

To answer your second question. We rely on the constants.php to set the perms. We do not control file permissions in the config.php file. If you need to set different permissions on images, you could always use a script with a cron job or a similar solution.

I hope this helps.

Again, no worries about your English, we are glad to have you here.

Anything else I can help with?

Cheers,

Thanks, Shane.

I expected the update process just fixed the wrong permissions caused by the bug and just for this case.

It’s fine about the constants.php. I just don’t wanna worry about another file at my next update process. Please, just add info about the constants.php to the installation process page of the user guide.

Bye! Thank you so much!

Hello Robson,

No problem at all. I have enjoyed working with you.

If you need anything else, just let me know!

Cheers,