/tmp/update-cache/ 755
/tmp/update-extraction/ 755

* The specified file temporary://fileNO69rJ could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
* http://ftp.drupal.org/files/projects/advanced_help-7.x-1.0-beta1.tar.gz could not be saved to temporary://update-cache/advanced_help-7.x-1.0-beta1.tar.gz.
*
Downloading updates failed:
o Failed to download advanced_help from http://ftp.drupal.org/files/projects/advanced_help-7.x-1.0-beta1.tar.gz

Comments

dmitrig01’s picture

Project: Advanced Help » Drupal core
Version: 7.x-1.0-beta1 » 7.0
Component: Code » update.module
Category: task » support
bfroehle’s picture

Hi barbank,

Are you on a shared host? I think your issue might be related to #1008328: Uniqueify update-cache and update-extraction directories to prevent "Permission denied" errors.

Try setting your temporary directory to something more unique? Perhaps your host has a tmp directory within your home directory that you could use.

Regards,
Brad

barbank’s picture

Yes, I am on a shared host. However, I have several shared accounts, with the same host, and a couple of others. My 7.0 updates on all of them update just fine, save for this one. I'll call support tomorrow. I've working on my taxes from 6:30AM until about an hour ago.

I did look in the home directory but I did not see any. The permissions on all the directories in the tmp directory are all 755

bfroehle’s picture

barbank: Go to Config > Media > File System, and change your tmp directory by appending some string to the end of the tmp directory -- i.e., change /tmp to /tmp/drupal-foobarbaz

That might just solve your problem.

bfroehle’s picture

Status: Active » Postponed (maintainer needs more info)

barbank: Did the suggested change in #4 work for you?

Marking as postposed since I don't know what the underlying issue is yet.

TimelessDomain’s picture

Issue tags: -automatic aupdate +automatic update

Thanks bfroehle. I had the same problem as barbank. Changing the tmp directory to something like /tmp/drupal-foobarbaz worked! It saved me having to apply a certain patch that was getting annoying.

bfroehle’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

So this is a duplicate of the issue referenced in #2.

christopher james francis rodgers’s picture

All you really need to do if you are having problems is to remove the forward-slash ("/") from "/tmp"
and specify

tmp

only at --> [Your-D7-root-home] » Administration » Configuration » Media: File system » Temporary directory.
.

==========

2011.03.26 - I updated this post to refine the work-around solution.

See http://drupal.org/node/1106492 for all the details.

barbank’s picture

Wow I just saw this. It's been a long time. I ended up wiping out the entire directory, dumped the database and drop it. I installed everything like it was a new install. And populated the database from the command line. I'm going to save the solution and use it if I need it.

On a separate note: I have a script right now that drops a table, creates it again, and populates it each time new room rates are posted. I am trying to migrate it to Drupal. Would I be playing with fire if do it on Drupal? I hand coded the entire system, so I knew all the possible problems. There were none. How about Drupal?