quiescere

I’m experiencing a similar error:

Downloading update from https://www.ads-software.com/wordpress-2.9.1.zip.

Unpacking the update.

Could not copy file: /www/ymca/blog/wp-content/upgrade/wordpress-2.9.1/wordpress/wp-includes/js/codepress/engines/khtml.js

Installation Failed

I’ve enabled SSH rather than SFTP, as there is no FTP daemon on my server. While the update is unpacking, I’ve opened a terminal window and checked the files being unpacked in the upgrade directory. They have expected permissions (755 and 644), and are owned by my user and group. Oh, and I’ve disabled all plugins, of course.

In my terminal window, I ran a small script in the upgrade directory while the auto-update was running:

while true; do
du --si -s wordpress-2.9.1
sleep 1
done

This told me that the directory was getting up to 5.9MB before failing. Considering that when I download the file manually and unpack it the same command says it’s 10MB, I’m assuming I’m hitting some bizarre memory limit. The global php.ini has a significantly higher limit, and apache’s conf file doesn’t have one.

If it’s only supposed to download 5.9MB for an upgrade, maybe it’s unpacking the whole thing but switching to the effective userid of the server, rather than my account userid? I don’t know.

I’m running out of ideas–any suggestions?

Perhaps you don’t consider it a basic HTML tag, but W3C has done so in both CSS2 since 1998 and HTML since 1997. Usage has lagged because Microsoft quit updating standards support for IE in 1998. Personally, I’m glad at least Firefox is finally behaving fairly well, as are (I think) Opera and many special needs browsers. I really hate having to go back and redesign a page because Microsoft hasn’t bothered to enforce standards compliance in 8 years. For those of you keeping count at home, that’s half the time the web has been in existence. The Q tag/property is only one example. There’s a lot of really powerful stuff available that vastly simplifies things, which is impractical for general use because 90% or whatever percentage of web users is still using an abandoned browser.

EDIT: O, and for what it’s worth, the q tag is working like a charm on WordPress 2.0.1 viewed via Firefox, as near as I can tell.