This means the web ui has no permissions to write to or update drupal files which breaks updating or installing a new module via the uiĬonsequently, you can't use drupal best practice (for dir and file permissions ) or you have to change them when you do an update and change them back when you're done. Interesting note, when following the drupal security guidance ( ref: ) which comes down toĬ) file owner should NOT be the apache(webserver id)ĭ) special case for the files directory ( and its sub folders 770 ) and files in it (600 ) to allow uploads from the web uiĪnd files and directories SHOULD be owned by the web server So this should do the trick when the user is and the chown did fix the issue for me. For me it would be OK that the temporary directory is writable by the apache user and the themes or modules folder is writable as well. It doesn't make so much sense to me, but there might be an explanation. On most Ubuntu installations, this is the apache user: I don't know if this is intended or not. To avoid this, make sure the folder /sites/default is OWNED by the user that executes the drupal scripts. It asks for some FTP (or SSH) credentials.What I have seen on several installations, and this is what you don't want: You paste the url of the module or theme you want to install.Now I have been able to pin down the problem. I have been fighting this problem several times, without success.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |