[SOLVED] Wordpress and it's file/dir access by the worthless(?) installer.
by Basher52 from LinuxQuestions.org on (#4T8AK)
Hi!
I've been fiddling with wordpress a loooong time and every time I have to give it extra access to directories that the installation will not set correctly.
For an example that will let me know that this will be a problem later on is that it can't even create the wp-config.php file, well because that directory isn't publicly accessible which is good but why doesn't the installer set the correct access then, at least temporarily.
This is however not an issue on a web hosting service.
A friend of mine that has been using Linux since early 90's told me ones that NEVER EVER let Apache be the owner of files and dirs, and I sure trust him with that.
Now I'm at the point to install a new site and yet again this occurs and tired of do fixes for this so mow I'm asking all of you guys.
I've been googling every time for this and tried a lot of settings but in the end I always go back to restricting the access so no one can access them unless it's me...
and NO, I do not EVER use a web hosting service for testing a new site, I got my own servers for that and yes they are running fine with CentOS 7.
Why can't the installer set the correct access for the directories at installation time?
It is always a problem installing themes and such so it's always the wp-content directory that is incorrect. Yeah, I use to set 777 just to make it work and then set it back but this can't be the correct way, can it? and as I won't have to do that on a web hosting service, there gotta be another thing that I can't think of.
A lot of google-search answers says to let Apache be the owner of this directory but as I said above, I will not let that happen as one told me not to.
How can this be a non issue at a web hosting service?
As I can see when doing the same there it always works but still the access to files and directories is not 777.
What have I been missing all these years?
I'm kinda pi$$ed at this now.
It's been a long time since I was doing Joomla installations but with this not even once did this fail and it would let me know even before the installation, telling me to correct the access to certain directories so later when the installation began, it all just worked.
Is Wordpress still some thing for kiddies after all these years?
I've been fiddling with wordpress a loooong time and every time I have to give it extra access to directories that the installation will not set correctly.
For an example that will let me know that this will be a problem later on is that it can't even create the wp-config.php file, well because that directory isn't publicly accessible which is good but why doesn't the installer set the correct access then, at least temporarily.
This is however not an issue on a web hosting service.
A friend of mine that has been using Linux since early 90's told me ones that NEVER EVER let Apache be the owner of files and dirs, and I sure trust him with that.
Now I'm at the point to install a new site and yet again this occurs and tired of do fixes for this so mow I'm asking all of you guys.
I've been googling every time for this and tried a lot of settings but in the end I always go back to restricting the access so no one can access them unless it's me...
and NO, I do not EVER use a web hosting service for testing a new site, I got my own servers for that and yes they are running fine with CentOS 7.
Why can't the installer set the correct access for the directories at installation time?
It is always a problem installing themes and such so it's always the wp-content directory that is incorrect. Yeah, I use to set 777 just to make it work and then set it back but this can't be the correct way, can it? and as I won't have to do that on a web hosting service, there gotta be another thing that I can't think of.
A lot of google-search answers says to let Apache be the owner of this directory but as I said above, I will not let that happen as one told me not to.
How can this be a non issue at a web hosting service?
As I can see when doing the same there it always works but still the access to files and directories is not 777.
What have I been missing all these years?
I'm kinda pi$$ed at this now.
It's been a long time since I was doing Joomla installations but with this not even once did this fail and it would let me know even before the installation, telling me to correct the access to certain directories so later when the installation began, it all just worked.
Is Wordpress still some thing for kiddies after all these years?