One thing to keep in mind is that you create files, and even if they are readable by you, for a web page, the relevant question is "can they be
read by the web server". For simple static content, usually the files you create should be "644" and the directories should be "755". ("directory" is same as "folder").
I'm guessing you are creating files on a hosting service's web server where they told you to create files in a folder called "web" or "public_html", and new folders you create are giving you "Permission Denied" when you try to load them in a web browser? If that's not the scenario, ignore ALL the rest of this. But if that's correct, a quick way to deal with getting existing stuff readable, assuming you have shell
access, is:
#chmod -R o+rx ~/public_html
(or ~/web, whatever folder they told you to create files in. "~" is shorthand for "my home directory").
That will set all files and folders in public_html, recursively, to be readable and executable. It's brute force and overkill (files don't need to be executable). And you'll have to do it everytime you upload something new, so it's not a long term solution. If you're on a hosted site, and your putting up files by ftp, sftp or something similar, is get the "umask" right so that files created in the future get created readable in the first place. If Nimoy's links don't help, ask your site admin, and tell them what software you're using to upload files.
|