The specified file temporary://filet8OKMQ could not be copied, because the destination directory is not properly configured

Odd - I'm running the stack on Ubuntu without errors... assuming you are running a default LAMP the Apache owner should we www-root. Did you create the prepro folder yourself?

Try 777'ing sites/all/files and deleting the sites/all/files/prepro folder. If that doesn't work try chown'ing the prepro folder to your WWW-user (should be www-root unless you explicitly changed it)

(moving this over to Prepro)

No updates in a while. Unable to reproduce.

If someone else has this issue please do reopen it and let me know!

I do have this issue and I've trying to fix it for a more than a week now. Any help is very appreciated.
Here are the details:
Any time a user uploads a profile photo I get the error. Please see the error in the attached image.
I am using 7.14 though

i also have this issue. i encounter it while using a feeds importer on a bluehost server. any help would be appreciated.

thanks,
- nick

Yes, I get these too. After every cron run there's at least 20 lines in Watchdog:

The file public://prepro/fresh.css was not deleted, because it does not exist.

@BiigNiick, Moh: this issue doesnt seem to be anything to do with Prepro, more that your filesystem is not set up to handle uploads correctly. Make sure the web user (www-data, for example) has the correct permissions for writing to the assigned directories.

@ladyofthelake, can you give me some more info on your setup? Prepro's "clear cache" mode deletes only files that it has a record of having compiled since the last cache clear, so there shouldnt be any way that it would be deleted.

I had a similar problem (with drupal 8). If I saved my files settings page (not change any of the settings, just save it). Then I dont get the errors. #1861956: translations imported but error shows: .po could not be copied because the destination directory translations:// is not configur

Can you try upgrading to 1.x and see if that sorts it?

It wasn't fixed. It's just that there hasn't been a solution submitted.

I'm having the problem too. I'm pretty sure it has something to do with the path I've specified for Temporary Directory in Configuration > File system. My site is buried pretty deep in a shared server and I don't have administrative privileges over the root directory. I was able to get my sysadmin to let me change my sites/default/files directory to full 777 permissions, so I went ahead and placed my tmp folder there. Site seems to work perfectly fine, but I'm constantly getting the error messages described by other people above.

Have you tried upgrading to current 1.x branch? The 0.x isn't supported any more

update

I had this problem and for me the issue was that Locale install (7.31) didn't create the directory sites/all/translations defined at admin/config/regional/language/update

Don't know why, don't know why it wasn't an issue on the Status report page but creating that directory fixed it for me...

As it was said before, creating the directory site/all/translations solved the issue.

My SOLUTION:

Relevant in the situation:

• Linux system
• Apache webserver
• Using Drush to install my modules

I already had the directory cd /sites/all/translations. But it had the wrong permission due to the fact that I install all modules with drush, so the permission was set to 775 and the owner and group to the dush-user, that's me on the Linux file system. If Drupal want's to write file's to the file system, the user www-data (that's the Apache user) needs permission the write in that directory. So change the group on /sites/all/translations to www-data .

Typ this command on the command line while your in de root of the Drupal installation.
USER@SYSTEM:chgrp www-data /sites/all/translations
This gives Apache (and Drupal) the permission to write in that directory.

Very weird issue in my case, I originally did assign 755 with www-data as owner for my /sites/default/files, and then I was getting the error. Re-assigning the same owner again (www-data) fix the issue.