Comments on: Download failed. Could not create Temporary file

By: Richard

Richard — Thu, 12 Aug 2010 17:53:10 +0000

As far as I am aware, it is an ownership issue, rather than plain permissions.

Have you considered using the Multi-User feature of Wordpress 3?

By: Nature is Awesome

Nature is Awesome — Fri, 06 Aug 2010 07:13:11 +0000

It worked! Have multiple blogs though and updating all the wp-configs will be very time consuming, does anybody know what’s causing this at server level?

By: Richard

Richard — Wed, 21 Apr 2010 00:29:10 +0000

@Kirk. Thanks for that. Glad to see you’re keeping an eye on this to make sure I don’t lead people astray.

@Dónal. I’m with Blacknight myself (and wouldn’t be with anyone else).

One thing I have learned from my experience with computers is that they can be frustratingly illogical at times. It is a mystery why sometimes things don’t work, and other times they do. Probably something to do with caching somewhere? Anyway, I’m glad it’s working now.

By: Dónal O'Flynn

Dónal O'Flynn — Tue, 20 Apr 2010 22:18:45 +0000

I don’t know what’s changed, but it seems to be working now (I didn’t remove any plugins or edit wp-config.php).

Only little niggle is that I still can’t upload zipped plugins from my computer via the WordPress interface (not a problem as I have full FTP access).
Thanks for your help Kirk!

By: Kirk M

Kirk M — Tue, 20 Apr 2010 19:08:41 +0000

Dónal – Just a thought out of the blue plus the fact that I’d had the same thing happen to me. It turned out to be a problem with a plugin (can’t recall which one at the moment) causing the problem so if you’re running a few plugins, deactivate them (except Akismet if you wish) and check again. If everything works okay then it’s just matter of isolating the offending plugin. I know it sounds like a redundancy check but it’s worth trying.

Oh, and strange as it might seem, there’s not supposed to be a “?>” tag at the end of the “wp-config.php” file according to the WP developers. It’s purposely left out in order to keep users leaving any white spaces below it as any white space below the “?>” tag can end up causing problems:

“PHP does not require a closing tag (?>) at the end of a script. Actually it’s safer this way, as you are less likely to break your site. You see, blank lines after the closing tag cause PHP to send the headers. It has to send them before the first byte of the response can be sent. Later, WordPress tries to send headers and PHP throws a warning. So the omitted “?>” is not a bug”

Just FYI.