Active
Project:
FileField Sources
Version:
7.x-1.x-dev
Component:
General
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Sep 2012 at 23:22 UTC
Updated:
12 Mar 2015 at 15:32 UTC
Jump to comment: Most recent
Comments
Comment #1
quicksketchHm, well sounds like your root "files" directory is not writable. I don't think this is a bug in FileField Sources, it sounds like a permissions problem on your server (as the error suggests). Try making your sites/default/files directory owned by the same user as your web server.
Comment #2
aaronbaumanI'm having the same issue, and files directory and all subdirectories are a+rwx
I don't have any problem uploading a file directly, just with filefield sources
Comment #3
aaronbaumanIn my case this error was an unrelated symptom, but led me to the cause of my WSOD:
php-curl was not enabled on my server.
(fyi: `apt-get install php5-curl`)
Dunno if this will solve d_hall's issue or not, but either way the permissions message is not fatal and is probably not the root cause.
However, this leads me to an unrelated question: #1880210: Why not use system_retrieve_file instead of invoking curl directly?
Comment #3.0
aaronbauman...
Comment #4
Berliner-dupe commentedThis Module dont work.
When i use remote URL images i get ....
"The file permissions could not be set on public://"
I changed user and group from "files directory" to www-data - i installed cUrl (apt-get install php5-curl) .. now i have no error in Logfiles but i get only WSOD when i will make a testnode with remote URL images.
And now?
Comment #5
Berliner-dupe commentedComment #6
quicksketchIf you're getting a WSOD, I'd suggest turning on the display_errors option in php.ini so that you get displayed an error instead of a white screen. PHP should give you an error that way, and once we know what the error is we'll be likely to solve it.
Comment #7
scotty commentedI was getting the similar error 'The file permissions could not be set on private://' and the file was not being uploaded. As with aaronbauman, I had to install curl which allowed the file to be uploaded but still gave the error. Setting ownership of the private files directory to www-data resolved the error.
Comment #8
aaronbaumanSeems like there should be a hook_requirements to verify that curl exists, rather than erroring out.