Unable to upload "because the destination is not properly configured"

that looks like some kind of permissions problem with the webserver in the temp directory. have you had any luck uploading with the upload module?

Yes, no problem with upload module. Video module working well also. php upload limits sky-high. I evan put a tmp/audio directory at the root of public_html to test and see if that was the problem and even chmoded to 777 and still the same result. Where exactly does this tmp/audio directory normally live?

OK, I went back and checked. I'm using attachment and filemanager, not upload. However, I enabled them upload module. Then in audio content type I enabled both "attachments" that appear after enabling upload module. Then I configured upload to allow .mp3. I created a tiny mp3 so file size is irrelevant. Still get the same errors. In the drupal admin log I see three new lines each time I try to upload an audio file:

help! It looks like something is wrong with the destination directories, but I don't see those listed directories (tmp/audio) in the root of public_html. There is a tmp director at the root of the virtual server, above the public_html directory.

I also disable attachment and file manager. I also reset ID tags setting to default. Still get the exact same erros in the log. Here is a more verbose error message:

yeah it should be using /tmp (the server's temp directory) to store the files you've uploaded. it then tries to move them to a directory in temp named audio. if you said that the directory doesn't exist, then it looks like that's where the error is occuring. maybe you could try creating the directory manuallly and see how that works?

Still throws the exact same error. Same on two sites now on the same host. The directory tmp site next tp public_html and is world writeable. I put an audio directory inside which is also world writeable. Any other ideas? .htaccess file issues? php.ini issues?

sorry..in a rush...the tmp directory sits next to the public_html directory.

see also: http://drupal.org/node/65211

renaming this to make it easier to find.

a few questions:
* do you get this error on preview, on submit, or on both? (i'm assuming both)
* do you see any errors listed on the admin screen that might be related?
* can you try changing drupal's temp directory to drupal/temp or something like that?

yes, I am getting the exact same errors as you, I wonder what's wrong...

hey cheif, those questions go for you as well...

Ok, here are the errors that this gave me when I tried to upload another song.

This is the error that it gives me no matter if I preview or submit:

These are the three errors I get everytime I try to upload a song in my admin logs:

and I do not have a tmp directory, well not that i see in my ftp, if I create one it will not do anything, if I change it, it will also not do anything...

Thanks for your time :)

Charles

I thought I posted my fix for this. I changed the Temporary directory in Drupal/admin/settings/file system to "files" and the problem simply disappeared. I think some hosting environments don't like it if you are using a tmp directory inside public html for this, or trying to name another directory tmp. "I should point out that "don't like" is NOT a technical term and is in no way meant to explain the problem. It just seems that way to me.

I should also point out that Site5.com has clearly changed something about their environment becasue the module now works out of the box. The tmp/audio directory is created without any trouble. Somebody fixed something on my server and din't own up to it.

Yes, thank you very much, that fixed it my friend. :)

This should be pointed out in the README file drewish, it works after this, I am just getting some ID3 tag errors, but I am assuming that this is normal.

Thanks for all your time ;)

Charles

I had a similar problem, and took hours to try to figure it out. Changing the temp directory to files didn't work. Changing files permision to 777 didn't work either. I kept getting the same error, unable to upload because the destination is not properly configured, where destination was actually only the name of the file, not including a full path to it. Looking at the error log, it was trying to write in root. ("The directory . is not writable").
I'm posting my solution here, in case anybody else has the same problem.
What solved it for me was to change the administer / settings / file system settings / File system path from files to /full-unix-path-to-drupal/files. Same for Temporary Directory.
Now, why I have to do this, I don't know. If anybody could help me understand it I would appreciate it.
Cheers.

with no additional feedback i'm going to assume you got this working. feel free to reopen if that's not the case.

Forgive me if I'm adding this is in the wrong place--I'm new to PHP and to Drupal...

The above solution worked great for me, except it broke images already on my site because it gave a different file path. I worked around it with the following cheesy hack on audio.module, line 546 ff., hardcoding in the full path as d.b.s. did:

If my PHP skills were better I'd try to give more, but I hope this helps someone out there.

I experienced this same problem with acid free photo galleries when transferring to a new site. I ended up having to uninstall the modules image, filemanager, and acidfree, and delete their corresponding DB tables. After reinstalling I reconfigured permissions and everything works fine.

Alex
----------
Contract Web Development

Just to reiterate for those like myself that skip to the bottom of these to get to the solution the quickest...

If you're receiving this error with 5.x, you want to go to Home > Administer > Site Configuration > File System and modify the Temporary File Directory field to reflect the correct location of a directory that Drupal can write to. Mine was set to /tmp which not only didn't exist, but I believe the slash in front would have messed with it even if it did exist. I changed mine to files/tmp and everything works fine.

Thanks for the great advice from all of the above contributors. I just wanted to put a cap on things for the terminally impatient like myself.

Guys my problem is NOT related to audio module but I am getting EXACT same error. I am uploading images but not able to see them. I have just changed my host and it seems the problem is caused because of changing the hosts.

I tried all the combinations of Home > Administer > Site Configuration > File System in my 5.3 but it is still not working!

I don't get any error as well, it is just that the image don't gets shown! What might be the problem ?

I have some more information on why this issue happens (it just happened to a site I work on).

I found that Drupal was leaving tmp_* files in the /tmp directory. This may be caused by users uploading a file and cancelling the node edit form, or errors or timeouts after the file was uploaded and saved as a tmp_* file. It seems that you get an error when you upload a file and the tmp_ file Drupal tries to create for it already exists.

I deleted all of these old tmp_ files from the /tmp directory and Drupal was once again able to upload and save the files we were having problems with.

Drupal should clean out these old files during cron runs, but in lieu of that I have setup a simple cron job to run every morning at 5:00am and delete any of them that are older than one week: 0 5 * * * find /tmp -name "tmp_*" -type f -mtime +7 -exec rm {} \;

For anyone who has read through all this and still gets the "because the destination is not properly configured" error, let me point out that you need correct file permissions set not only here: Home > Administer > Site Configuration > File System but also under the module settings. E.g., in my case, Node Images.

check if your host has open basedir restrictions that might be preventing access to the directory.

The problem is most likely related to file ownership rather than persmissions. If you are running Apache as the user apache, chown your files directory to apache:apache.

I ran across this problem with the FileField module. After trying nearly evrey solution suggested above unsuccessfully, changing the user using chown (as suggested by Andrew_Mallis) finally worked. I also chowned the directory created by the File Field module the file field settings (i.e. files/filefield).

I suspect (but cannot prove) that this error message may sometimes be misleading because it points to the tmp directory (or whatever is set in the file system settings) when the directory the file is being moved to (usually created by the module) is the one at fault.

Sorry for the reopening of this, but I've some serious trouble in using the file upload. The error is the same, but for some reason i cannot unset the read-only attribute on windows wamp folder. I've read saomething about, it seem tha tha apps mostly ignore the read-only attrib for the folder. How can I resolve this prob?

In D6 if the directory you want to move a file too is not in your 'files' path set in your site config you can't use the api functions: file_move, file_copy or file_save_upload because they all call file_create_path, which requires that the file destination is in the site 'files' path. So, if you want your module to use a different directory, store it using say variable_set('mymodule_files', path) and basically copy the api functions into into mymodule_file_move() ... etc. but remove the call to file_create_path and replace with a check for your modules file path (don't just allow any old path, it's asking for trouble!), and call those functions instead. Hope that helps :)

Another solution: I used a custom module which called file_save_data(), but the target was outside the Drupal directory which appears to be forbidden.

I an using version 6.x. I had every problem on this list and I finally got it to work. My situation was images but it was a problem with the file system configuration:

1) There was a conflict with the Pathauto module. After I disabled Pathauto it worked!

2) On my install on a shared server, /tmp is actually /home/greatbas/tmp. put "/home/greatbas/tmp" in the "Temporary Directory" field on admin/settings/file-system.

3) I am using a multisite configuration. in admin/settings/file-system the "File System Path" starts at the server public_html/ directory. Enter "sites/greatbassguitars.com/files" in this field to access the "files" directory in your home directory.

I hope that this can save someone else about 4 hours!

Same issue here, also none of the tokens are being replaced !!

Though we can't turn pathauto off.