I just tried updating some modules through the Drupal interface. All failed, and they all produced errors like this:

The file permissions could not be set on temporary://update-cache.

This error is not useful because Drupal declines to tell me the directory path where the module is trying to be saved.

I filed this as a bug because unhelpful error messages are contrary to the usability improvements.

Comments

bfroehle’s picture

Component:update.module» file system

Where in the update process did the occur? Did you get prompted to enter your ssh or ftp credentials?

bfroehle’s picture

Component:file system» update.module

Oops, didn't mean to change component.

Aren Cambre’s picture

Never got prompted for credentials. It happened right after I hit the button to start the updates. That button was on the page that identified the modules needing updates.

TNmoxa’s picture

I have the same problem. Is there any solutions?

bfroehle’s picture

Can you give a description of your setup? What are the file system settings (Admin -> Config -> Media -> File System). Do you have any messages in Admin -> Reports -> Status?

bfroehle’s picture

Status:Active» Postponed (maintainer needs more info)

Setting to postponed (maintainer needs more info). This might be related to #1008328: Uniqueify update-cache and update-extraction directories to prevent "Permission denied" errors...

Please change status back to Active upon reply.

Aren Cambre’s picture

Status:Postponed (maintainer needs more info)» Active

This issue is about the error message, not the underlying cause.

All error messages should be helpful. Telling us something about temporary://update-cache doesn't help us diagnose the root cause.

This issue is not about making the error go away. It's about Drupal providing useful error messages.

dww’s picture

Issue tags:+string freeze

See #605292: propagate failure during batches in update manager. Update manager is completely full of unhelpful error messages, since most of them are Exceptions being thrown deep in the bowels of the logic and propagated back up to the end user. No one rallied to try to work on this particular aspect of the Update manager before 7.0 shipped, so now we're in string freeze. It's possible we'll get more exceptions for fixing unhelpful error messages on the grounds that it's a usability bug, but I'm personally not going to invest any energy in patches like this until there's clear agreement from Drieschick that such patches will be committed.

You might have more luck turning this into a D8 issue and at least fixing up error propagation to be more user-friendly and helpful there.

Aren Cambre’s picture

Wow, that's a surprising usability omission given D7UX.

dww’s picture

It wasn't really an omission. I kept bringing this up, and webchick, Bojhan, and others were well aware. The resources just never materialized... I can't personally do everything myself, and without outside help, I had to be very selective about what I spent my limited time on. Crappy error messages suck, but they're not as critical as totally broken functionality...

Aren Cambre’s picture

Understood.

originalusrnm’s picture

You can find the temp file directory in the Drupal File System Settings:

/admin/config/media/file-system

Try giving that directory full access. It worked for me.

Taran’s picture

Issue summary:View changes

I'm just bumping this thread because I ran into it with a client. I don't expect it to be fixed in Drupal 7 - dww was clear and I understand the need for triage - but this should not stand in the future with Drupal 8.