Timeline for Error when uploading file through Drush on S3 volume
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2015 at 20:51 | comment | added | kha | I still can't find a solution for this issue. I strictly followed the access rights recommandation, and its works fine locally. Issue only appears when storing docs on S3. .htaccess is created on S3 bucket file are upload correctly to bucket I still get the warning message Any idea ? | |
| May 8, 2015 at 1:24 | comment | added | kha | Thanks for your precious answers.I'll try these leads and report on the topic later today. Now, I have read the File source code, and it seems that even if you don't use public or private but s3, it stills checks the folders configuration to see if it can or can not create files there, including .htaccess. So it may be a simple standard access rights configuration issue. | |
| May 4, 2015 at 7:17 | comment | added | Ben | As the poster mainly wanted to silence the warning without changing the current behavior (file are created correctly) I figured having the rights files should be enough. It will remove the warnings/errors in admin/reports/status too. Still, I wouldn't accept my answer as it's really not a clean solution to the problem at hand but a workaround at most. | |
| May 3, 2015 at 10:34 | comment | added | Clive♦ | S3 doesn't use Apache and doesn't process .htaccess files, so doing this would be pointless. This would be perfectly fine advice for people using Apache with the relevant overrides enabled, though | |
| May 3, 2015 at 3:51 | history | answered | Ben | CC BY-SA 3.0 |