If you’re using WordPress 2.2, you’ll want a version of WP-United that is compatible. that means the development version, which you can grab from the SVN repository at http://svn.wp-united.org using your favourite SVN client.

Please note that if you do decide to use this code, it is changing rapidly, so be sure to check for changes often, including changes to the mod upgrade file.

For those who have already been making use of the SVN code, the version has just been bumped up to v0.9.5 in preparation for the next release. You’ll need to look at the upgrade mod file if you’ve been using v0.9.2.

If you’re a phpBB3 user, you’ll see phpBB3 code in there, but it is not currently supported (and will not work as you expect)… best to leave it for a few days.

Most phpBB-based sites fall into two categories: Those where phpBB is used as an add-on feature of the main site: for example, as a support forum; and those where a phpBB community is the site.

Sites in the latter category live and breathe ‘community’ — and are often places for pre-existing off-line communities to discuss topics and meet online. Often, such sites using a stock phpBB install spring up and attract large numbers of users — without even a custom design or other site features. It usually doesn’t take long, however, for users to request new features, and a nice portal page summarizing news or announcements is usually the first request. (More…)

Thanks to George, who spotted this update on the WordPress site… if you downloaded and installed WordPress 2.1.1 recently, it contained compromised code, which could lead to your server being exploited. While this has nothing to do with WP-United, I recommend that all users upgrade their WordPress as soon as possible.

I hope they catch whoever was responsible for the breach…

Just upgraded the site to the latest WordPress. No news is good news, and there’s really nothing to report — an uneventful upgrade!

It apparently fixes several bugs, so I recommend that WP-United users give it a try.

Update on 4/3/2007: It turns out that v2.1.1 contained compromised code. If you did install this version, you should upgrade immediately. (of course, this has nothing to do with WP-United).