Donncha announced today that WPMU 1.3.2 RC (release candidate) is out:
Some highlights:
1. “Whitelisted options” means some of your plugins may break. Se here for more..
2. Signup control is fixed if you limit signups to blogs only.
3. Uploads via xmlrpc can now be checked via the wp_upload_bits filter.
4. Synced with WP 2.3.2 and lots of minor bug fixes.
Download it here.
Using the WP-Super Cache plugin with WordPress-MU is very simple.
WP Super Cache is a static caching plugin for WordPress. It generates html files that are served directly by Apache without processing comparatively heavy PHP scripts. By using this plugin you will speed up your WordPress blog significantly.
Instructions on how to install the plugin can be found in the readme file that comes with the plugin. As noted in the file, installing the plugin for WordPress-Mu differs just a bit from the regular WordPress install:
If you are using WordPress MU you will need to install this in ‘wp-content/mu-plugins/wp-super-cache/’ and the file wp-cache.php must be copied into the mu-plugins directory.
But there is a small problem with the plugin that I find very annoying. Although the cache is cleared with every post update and every theme change, when a user updates his blog’s widget settings the cache is not cleared and the user will not have a clue what is going on. This will result in a flood of support tickets.
I have been trying to solve this issue without changing any core files but came short. Finally I edited the wp-admin/widgets.php file and added just after line 266 the following code:
// Added to clear WP-Super Cache after the widgets are updated.
// Code by Elad Salomons http://www.ringofblogs.com
if(function_exists('wp_cache_no_postid')) {
wp_cache_no_postid(0);
}
If someone finds a way to use a plugin for this please let me know. By the way, this should work just the same for the regular WordPress.
In a new forum thread this week a WordPress MU user asked an old question: how to set the default timezone offset for new blogs? The solution proposed was to edit the wp-admin/includes/schema.php file (line 275). This of course should work but it involves in changing wpmu core files, an option I think is not the best one.
The option I propose is to set the default timezone offset option, and other options as well, using a plugin. This is really simple by using the wpmu_new_blog hook. The entire thing is less than 10 lines of code:
<?php
function new_blogs_setting( $blog_id ) {
//set your options here:
update_option('gmt_offset', 2);
// stop editing here
return;
}
add_action('wpmu_new_blog', 'new_blogs_setting');
?>
The plugin can be download from here (wpmu_new_blog.zip) and needs to be droped in the mu-plugins directory. One can add any other default option settings. In the case were a change of an option for existing blogs is required, the script to set global options for all WPMU blogs may be used.
TNX, the text links ads service, is having problems with their PayPal account. TNX uses its PayPal account to receive funds from advertisers and pay webmasters for publishing ads on their web sites.
The issues with PayPal was published on the company forum:
As for now, payments are sent to publishers using on of the founders PayPal accounts.
After a little testing it seems that the Favicon Manager WordPress Plugin from Digital Ramble works just fine with WordPress-MU.
You are probably familiar with the default favicon that comes with WordPress-MU - 
. This plugin allows each user to set his own favicon via the Options page.
As announced, Google started to roll out the new simplified ads management for Google Adsense. This feature will save the settings of your ad units within your AdSense account. That means, each time you want to change the colors, channels, or even the corner styles for your ad units, you can make the changes directly in your account rather than generating and pasting new code.
There is also an importer that you can paste in any older AdSense for Content code and convert it to the new AdSense unit code. You will then be able to manage your settings from the Manage Ads page directly.
I have been testing the new WLW (Windows Live Writer) for a few weeks now both in English and Hebrew. I must say that I’m very pleased and find the software very easy to use.
Once you download it and install you will be asked to set up the connection to your blog:
That’s it!
Donncha posted that the new 1.3 version of WordPress-MU is out.
There is also a thread on the support forum:
This is a sync of WordPress 2.3.1 which includes native tagging support as well as many bug and security fixes.
WordPress MU specific features include:
1. Better admin controls for the signup page. It can be disabled in various way.
2. Upload space functions have been fixed.
3. The signup form is now hidden from search engines which will help avoid certain types of spamming.
4. Profile page now allows you to select your primary blog.
5. Database tables are now UTF-8 from the start.
6. If you’re using virtual hosts, the main blog doesn’t live at /blog/ any more.
7. The WordPress importer now assigns posts to other users on a blog.
8. A taxonomy sync script is included in mu-plugins but commented out. It hasn’t been tested much but if your site has many hundreds of blogs it might be worth spending some time on a test server. Replicate normal traffic patterns and see if the server can cope with the upgrade process. If not, then look at the sync script, uncomment it and iterate over all your blogs with a script.Developers - get_blog_option() will never return the string “falsevalue” again. That bug has been squished and it now returns the boolean value false.
Many many thanks Donncha 
