The folder "xxxx" is writable The folder "xxxx" is writable
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

The folder "xxxx" is writable

Started by cludgie, August 31, 2006, 08:05:11 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

cludgie

After upgrading to 1.4.9 when I check the version everything looks alright, however there are several folders with the message:-

Quote"The folder "folder name" is writable. This is an unnecessary risk, coppermine only needs read/execute access"
permisions are set at 755

Folders Include "doc, docs/pics, plugins/sample, plugins."  I will post a full list if needed.

Should I worry about this?
do you need any more info

Regards,
Mark.


Nibbler

It is advisable to make them non-writable using your FTP client or webhost control panel.

cludgie

Done and done  :)

I kinda knew this had to be done, funny thing is when I set the permissions with my ftp client, it would revert back to what it was.  File manager in the control panel worked a treat

Cheers,
M

Joachim Müller

Just for clarification, here's the explanation from the permissions section of the docs that come with coppermine (stuff that applies to you highlighted):
Quote# FTP application
Setting the permissions using your FTP application will be the option available for most users who are webhosted. Depending on the FTP app you use, the user interface will slightly differ: some apps will allow you to enter the CHMOD command by entering the numbers (777 or 755), others will provide you with checkboxes where you can tick the permissions separately for each group. More advanced FTP apps may even provide you with both mechanisms. As this documentation can't cover all individual FTP apps that are available, the exact method might differ a bit from what you have.
Your FTP app will probably have two windows, one showing your local files, the other one showing the files on your server. In the window that shows the remote files on the server, navigate to the folder your coppermine files reside in. Highlight the "albums" folder that resides within the coppermine folder. From the context menu (right-click!), choose "properties" (might be named "chmod" or similar as well). The permissions dialog will then pop up. Choose the proper permissions as suggested above (777 or 755, depending on your server setup). If you have a checkbox that enables the permissions to propagate for all sub-folders and files, tick it. If you don't have it, nevermind. Then click "OK" on the dialog box to apply the permissions. Keep in mind that your FTP app might not have the power to actually find out about the current permissions that are applied, so you mustn't trust the information displayed in the dialog box: even if it appears that the permissions are already set as needed, this may not be the case, so you should re-apply the permissions no matter what.
After having applied the permissions for the albums folder, do the same thing for the include folder that resides within your coppermine folder.

# Website control panel
Some webhosts may not give you the option to access your site using FTP, or they may not allow your FTP client to execute the CHMOD command. If this is the case, you probably have a server setup interface (e.g. cpanel) to apply permission to folders and files. In fact, this doesn't matter, the method for applying permissions doesn't differ from the one described above in the section "FTP application": navigate to the albums folder and apply the permissions needed to give your webserver write access to all files and folders within the albums folder. Do the same thing for the include folder as well.