Timeline for How to set up permissions for the private files directory?
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2018 at 6:26 | answer | added | Free Radical | timeline score: 1 | |
| Jul 25, 2018 at 15:25 | review | Close votes | |||
| Aug 2, 2018 at 5:43 | |||||
| Jul 24, 2018 at 13:06 | comment | added | lacuna | Thanks Clive - I appreciate your efforts, and those of other long-time users, in keeping quality here high. There do seem to be unknown/unstated specifics regarding the private-files directory, and as you acknowledge, some holes in official documentation. I plan to help edit the Drupal docs page once I have a bit more clarity (ideally with similar help in making sure my edits are accurate and useful). | |
| Jul 24, 2018 at 13:01 | comment | added | Clive♦ | Ok I give :) I've edited into the more generic version - like I said before, I can't promise that's not going to make it attract "too broad" close votes (if I wasn't a mod and didn't have a binding vote I'd be voting it as such if I'm honest). Good luck getting it sorted anyway | |
| Jul 24, 2018 at 12:59 | history | edited | Clive♦ | CC BY-SA 4.0 |
edited title
|
| Jul 24, 2018 at 12:45 | comment | added | lacuna | Thanks for the additional details, Clive. Unfortunately it does not seem that the 2 items you list in fact cover the requirements. There must still be something missing, as user, permissions and path all appear to be correct according to documentation, yet the error message persists. The strength of Stack Exchange is that a community can pool their knowledge; my request continues to be that the question continue to specify a need for details, and that the bitnami platform be an aside vs a primary point. | |
| Jul 24, 2018 at 12:38 | comment | added | Clive♦ | You're right, it doesn't, my bad. But that doesn't change the fact that what you need to know isn't about Drupal. You already know all the Drupal parts of this, which are basically 1. that the folder needs to be read/writeable by the user that executes the PHP part of the website, and 2. you need to set the path to it under Admin -> Config -> Media. There's nothing else to know from the Drupal perspective, everything else is about how to set up appropriate users/permissions to allow PHP to write to the folder | |
| Jul 24, 2018 at 12:25 | comment | added | lacuna | Again with respect, Clive (and I know it's hard to convey in text, but sincerely!) - that page does not document requirements of private files. Please have another look (you can use your browser keyword find function with 'private') and reconsider. If someone is able to improve that page, I'd be a huge fan! | |
| Jul 24, 2018 at 12:25 | comment | added | Clive♦ | ...a full tutorial, though, you need to extract the information from there, combine it with knowledge of how to administer the server, and come up with a solution that matches your exact needs | |
| Jul 24, 2018 at 12:23 | comment | added | Clive♦ | Drupal's full file permission requirements are very well documented: drupal.org/node/244924. The problem you're experiencing is not knowing how to set up your operating system/environment to fulfil those requirements. Drupal also requires MySQL and PHP, a web server, etc, but a question on how to install those wouldn't be on topic here either. I do understand it's something people do need to cover, that's why we deliberately let this question through the cracks: drupal.stackexchange.com/questions/373/…. That's never going to be.. | |
| Jul 24, 2018 at 12:20 | comment | added | lacuna | I will respectfully disagree, knowing you have a lot of experience on Stack Exchange. Please reconsider your stance. I'm unable to find a detailed explanation of Drupal's full requirements for private files, or a trouble-shooting guide. A good answer here will be a service to the community. | |
| Jul 24, 2018 at 12:18 | comment | added | Clive♦ | To put it succinctly: this is a file permission problem, not unique to Drupal, and we wouldn't teach you what you want us to teach you here (how to manage generic file permissions on any platform). It's been made specific to your current environment, in an attempt to avoid it being closed as "too broad" or otherwise off topic, because the knowledge you need is not unique to Drupal, but there\s an outside chance that there might be something unique to Bitnami that can be identified and addressed to help you and future users of the same platform | |
| Jul 24, 2018 at 12:16 | comment | added | lacuna | @clive - a polite request, since I'm attempting to learn - please note the above request and revert my question to my own title of a moment ago unless you are able to describe why this issue is specific to the Bitnami platform. Is there reason to believe that bitnami needs special permissions, ownership, locations or other consideration? Alternatively, please feel free to point me to an existing answer that actually covers all the details. I've not found one. | |
| Jul 24, 2018 at 12:16 | comment | added | Clive♦ | Sorry but that would be much too broad for a single question in this format. There are many different environments with many different considerations, too many to cover in a couple of paragraphs. File permissions are file permissions at the end of the day - Drupal just needs to be able to write to two folders (public and private), and read from the rest of the docroot. How you get that to happen across multiple platforms isn't something that Drupal is concerned with, it only cares about the result, and nothing in and of Drupal itself will teach you *nix file permissions | |
| Jul 24, 2018 at 12:13 | history | rollback | Clive♦ |
Rollback to Revision 3
|
|
| Jul 24, 2018 at 12:13 | history | edited | lacuna | CC BY-SA 4.0 |
add info after attempt to resolve per recent recommendation in an answer
|
| Jul 24, 2018 at 11:46 | comment | added | lacuna | As the original poster of this question, I want to be sure to understand the considerations of setting up private files no matter the platform. For those editing my question to make it more specific to bitnami: please avoid doing so lightly. I don't believe Bitnami has some unique secret in this regard. Please address that uniqueness if in fact it's the case. | |
| Jul 24, 2018 at 11:45 | history | edited | lacuna | CC BY-SA 4.0 |
as the original poster of this question, I want to be sure to understand the considerations of setting up private files no matter the platform. I don't believe Bitnami has some unique secret. Please address that uniqueness if in fact it's the case.
|
| Jul 23, 2018 at 20:37 | history | edited | leymannx | CC BY-SA 4.0 |
edited title
|
| Jul 23, 2018 at 19:42 | answer | added | leymannx | timeline score: 3 | |
| Jul 23, 2018 at 16:23 | comment | added | lacuna | Thanks - I've come across instructions on acting as a different user. Will do that and follow the same steps above. I'm assuming no one actually sees issues with those steps other than doing things as root user? (btw, I've been following bitnami instructions, which don't mention the need to act as a different user....). | |
| Jul 23, 2018 at 16:06 | history | edited | avpaderno♦ | CC BY-SA 4.0 |
edited title
|
| Jul 23, 2018 at 15:04 | answer | added | brace110 | timeline score: 1 | |
| Jul 23, 2018 at 14:59 | comment | added | Alfred Armstrong | Are you running drush as root? That's not going to help because any files created by drush will not be writable by the webserver. Better to run it as the daemon user to reduce the chance of file ownership issues. | |
| Jul 23, 2018 at 14:44 | history | asked | lacuna | CC BY-SA 4.0 |