Selected file could not be uploaded, because destination is not properly configured

The selected file could not be uploaded, because the destination is not properly configured

Seen this error before? Or seeing it right now and pulling your hair out? This is a common error involving Drupal's filemanager and image modules (acidfree). In particular, this error occurs when the filemanager file directory and Drupal's native file directory conflict. Also of issue is the location and user permissions of your private files directory. If you transition data to another server, and your private files directory is located above root, then you'll need to adjust user permissions.

How to get filemanager and acidfree working together happily

Note: If you are running a multisite installation, precede with:

• sites/www.example.com/...

Browse to admin -> settings -> filesystem and ensure the following settings are in place:

File system path: files
Temporary directory: files/tmp
Download method: public

Browse to admin -> settings -> acidfree, scroll to the bottom and check the following box:

Force all new images to be transferred by Drupal

Browse to admin -> settings -> filemanager, and make the following settings:

Public file system path: files/public
Public file system URL: http://www.example.com/files/public
Private file system path: /home/username/private

Important:: You need to recursively (ie. w/ all subfolders and files) CHMOD the private file system path and all its subdirectories to 777.

Voila! You should now be able to import images to acidfree without running into the above error.

Security note: The private file system path should be above your document root, ie. a non-public location. However, if you are still getting the error you may need to relocate the path as described below.

If you are still getting the error

If you are still getting the error, particularly after having transferred to another server, change the private file system path to:

Private file system path: /files/private

Note that it is ideal to have your private directory above the document root, so the public cannot access your private files. The method above moves the private directory into the public tree, therefore it's recommended that you add the following to your Virtual Host settings:

# deny access to private directory
Order Deny,Allow Deny from All

Last Resort

If all of the above fail you may have to delete your photo galleries and re-upload them. When doing this, go ahead and delete the "private" folder, browse to filemanager, it will detect that the folder is not there. Create a new one, CHMOD permissions to 777, specify the path in filemanager settings and save. You should now be able to create albums and upload photos without experiencing the above error.