I was using /tmp/sample1.com and /tmp/sample2.com for temp files directories, but just ran into an issue where if that subdir got removed by some process when the machine restarts. So the CSS/JS aggregator would completely barf with an error saying "The selected file /tmp/filechFmhX could not be uploaded, because the destination css/9552f5b9401db9e020656be9e5e3268f.css is not properly configured." This is a bad error message as it really means that /tmp/sample1.com folder needs to be created. If you go to admin >> files, it will say /tmp/sample1.com was just created.

We should create these on demand along with the files dir instead of requiring people to go to the admin screen to do so. I had an issue a while ago on this but couldn't find it.

CommentFileSizeAuthor
#1 file_check_directory-157143-1.patch1.68 KBchx
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chx’s picture

chx CreditAttribution: chx commented
Status: Active » Needs review
FileSize
file_check_directory-157143-1.patch1.68 KB

This tries to create these paths on demand. The performance overhead is next to nothing.

snufkin’s picture

snufkin CreditAttribution: snufkin commented

I could not even reproduce the first error. I created the subfolder in tmp, but the performance css and js directories are constantly created in files only. Tried multiple times. it seemed that the temporary settings are completely ignored.

dpearcefl’s picture

dpearcefl CreditAttribution: dpearcefl commented

Is this issue report still needed?

Status: Needs review » Needs work

The last submitted patch, file_check_directory-157143-1.patch, failed testing.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.