Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
What does mean this errors?
http://ftp.drupal.org/files/projects/ds-7.x-1.3.tar.gz could not be saved to temporary://update-cache-474722ac/ds-7.x-1.3.tar.gz.
http://ftp.drupal.org/files/projects/date-7.x-2.0-alpha4.tar.gz could not be saved to temporary://update-cache-474722ac/date-7.x-2.0-alpha4.tar.gz.
Downloading updates failed:
Failed to download ds from http://ftp.drupal.org/files/projects/ds-7.x-1.3.tar.gz
Failed to download date from http://ftp.drupal.org/files/projects/date-7.x-2.0-alpha4.tar.gz
Message will be shown after progress bars with downloading modules.
What is wrong?
Comments
Comment #1
mfraz74 CreditAttribution: mfraz74 commentedYes I'm seeing this too:
http://ftp.drupal.org/files/projects/addressfield-7.x-1.0-beta2.tar.gz could not be saved to temporary://update-cache-77740e74/addressfield-7.x-1.0-beta2.tar.gz.
Downloading updates failed:
Failed to download addressfield from http://ftp.drupal.org/files/projects/addressfield-7.x-1.0-beta2.tar.gz
Comment #2
Honza Pobořil CreditAttribution: Honza Pobořil commentedIssue occurs in newest release too.
Comment #3
Everett Zufelt CreditAttribution: Everett Zufelt commentedDo you have your temporary path defined at:
http://example.com/admin/config/media/file-system
Does your site status report give any errors or warning about your temporary path, or any other possibly related errors?
http://example.com/admin/reports/status
Comment #4
Honza Pobořil CreditAttribution: Honza Pobořil commentedTemporary path is defined and no errors in status report. Btw, uploading images and generating thumbnails by Image module works correctly.
Comment #5
J.Schimmel CreditAttribution: J.Schimmel commentedI have the same error message after updating from 7.0 to 7.8:
My temporary file path in ...admin/config/media/file-system is set to: tmp
After updating to 7.8 on a Virtual Server the tmp and the update-cache-xxxxxxx dirs are created by drupal and the permission for the update-cache-xxxxxxx dir is set to 755. When updating there is an error message:
http://ftp.drupal.org/files/projects/imce-7.x-1.4.tar.gz konnte nicht unter temporary://update-cache-xxxxxxx/imce-7.x-1.4.tar.gz gespeichert werden.
My provider told me that safemode ist turned on and that it cannot be turned off due to security reasons. Before updating to Drupal 7.8 the temporary dir worked without problems, with safemode-on.
Is there any solution to use 7.8 with safemode or do I have to downgrade to an older Drupal 7 Version?
Any ideas? Any help would be very much appreciated.
Comment #6
handokozhang CreditAttribution: handokozhang commentedMe do have similar problem too.
I was able to perform module updates. But not now, after I upgraded to Drupal Core 7.8. The error messages are similar to those above:
... could not be saved to temporary: ...
I have checked the folder name, it typed correctly on configuration > file system > temporary directory. I even tried to change the folder permission to enable all (7, 7, 7) but not help.
A strange thing, after upgrading from 7.7 to 7.8, I was able to perform translation updates, success without any problem. So I think, this bug is not about the temporary folder permission, nor any issue from the webhosting. It should be the coding itself. I'm not a programmer, hope someone have programming knowledge can help checking the coding.
Comment #7
handokozhang CreditAttribution: handokozhang commentedHello all, I guess I found the temporary solution for this problem.
It seems this problem is cause by safemode directive and limitation of Drupal to handle it. For more information please visit these pages:
http://drupal.org/node/1267240
http://drupal.org/project/issues/drupal?text=safe+mode&status=All&versio...
Solution:
Simply turn off the safemode directive off in php.ini
Step by Step Explanation:
1. You need to have php.ini file. If don't, ask your webhost if you're allowed to have it.
2. Set your website to maintenance mode.
3. Backup your php.ini.
4. Edit the php.ini and set safemode to off.
5. Save/upload the 'edited' php.ini file to your website.
6. Make sure the php.ini file permission is 755.
7. Goto Report section and perform the module updates.
8. Fix if there still any issue reported.
9. Quit the maintenance mode.
10. Have a cup of coffee and relax ;-)
Strange thing:
After turn safemode off, I realized it's been reported that "CKEditor was not found at sites/all/modules/ckeditor/ckeditor". So, I uploaded the module following the instruction. Strange, as far as I remember, I'd already uploaded the module to the specified location, and CKEditor was working correctly before.
Another strange thing:
If I'm not wrong, Drupal won't able to install if safemode is on. I guess, my provider had ever updated the php.ini and changed the safemode to become on without noticing me.
So far, everything is working fine on my website. Please do necessary backup before you try this solution.
Comment #8
johnnykrisma CreditAttribution: johnnykrisma commentedI wish it were that easy in my case. Safe mode is off and has always been off, and I am still seeing this error. Double and triple checked permissions of temporary directory too.
Comment #9
Honza Pobořil CreditAttribution: Honza Pobořil commentedIn my case, safe mode disable helped.
Comment #10
PasqualleComment #11
Prancz_Adam CreditAttribution: Prancz_Adam commentedSame error here. Any update?