I was never really thrilled with the WordPress plugins that use <pre>…</pre> for delimiting code, because of bad mojo between the WordPress editor and <pre>, specifically when the two meet the lowly < character. (Specifically, code can disappear without warning.) I detest having to tip-toe around software; humans shouldn’t have to bend to the code.
I’ve installed SyntaxHighlighter Evolved, which uses the  notation, and doesn’t care how < is encoded.
Quick documentation can be found on WordPress’ Posting Source Code.
By default, standard WordPress installs give the option to perform automatic updates using FTP or FTPS (FTP over SSL). There is another method to have Apache perform the update without passwords. It can be activated by adding the following to the wp-config.php file:
This does require that you have the permissions set up correctly, and you should be aware that there are serious security implications doing this.
Details on the settings for wp-config.php can be found in the documentation Editing wp-config.php.
WordPress has unleashed its video tutorial site, WordPress.tv. You can find all kinds of helpful videos from basic tutorials to WordCamp conference sessions.
I installed the WP-Postview plugin for WordPress. Everything was fine until it encountered Japanese. Then it barfed repeatedly with “Warning: Cannot yet handle MBCS in html_entity_decode()!”.
To work around this problem, I found some great notes on SearchMarked.com.
Edit the wp-postviews.php file, replacing
$text = html_entity_decode($text, ENT_QUOTES, get_option('blog_charset'));
$text = utf8_decode($text);
I installed a new WordPress blog today on a server. The site is served by Apache using virtual hosting. I kept getting 404 errors trying to access any page that required mod_rewrite, pretty much other than the home page and administrative pages.
It turned out that I forgot the following in the Apache httpd.conf file: