this same bologna from “experts” whose job it is to help, not roll their eyes every time someone has a problem. If you don’t like helping people, get a different job
It’s no one’s “job” here to help, we’re all volunteers, the developers, the people helping in the forums, etc. We’re all volunteers giving up our free time to help, we don’t want to waste your time any more than we want our time wasted, so please do rein it in a bit and trust that when asked for something, it’s for good reason.
We ask that you please open your own thread for two very important reasons:
1. Just because it’s the same error message doesn’t mean it’s the same problem, cause, or solution. Trust me, I know it’s counterintuitive, but I have been doing this for almost 10 years. Adding to someone else’s thread will simply lead to more confusion as different sets of instructions and solutions are being traded back and forth.
2. These forums support reply notifications via email. The original poster probably doesn’t want your journey to a solution filling their inbox any more than you would in their place.
So, with that said, on to the issue at hand. Directory and file permissions are basic web development knowledge, they have been here since the dawn of computers and won’t be going aware. Depending on how the server is configured, WordPress will need the directory to be set 777 so it has permissions to actually write something to that directory. That’s not a WordPress problem, that’s a server configuration problem. WordPress can’t write to where it doesn’t have permissions to write. A properly configured server will allow WordPress to write to a directory set to the more secure 755, but again that’s a server configuration issue, not a WordPress issue.
So, if you are still having trouble yourself, or would like to just rant about this in general (keeping in mind that this is a server configuration issue, not a WordPress issue), please open your own thread.
