Yes I know this is not the one you're expecting... :roll:

We will however release a 0.9 update in the upcoming days, mostly to include a few bug fixes, easy antispam tricks and some new locales (Basque eu-ES, Icelandic is-IS, Polish pl-PL, Estonian ee-ET, Russian ru-RU).

Also, I just need to get this one out in order to clear my head! ;)

By the way, if you have a 0.9.x language update sitting on your drive, please send it *now* ... or wait for Phoenix.

This will be the last 0.9.x release. After that one, it will be all 1.x aka Phoenix.

Update: version 0.9.2 is available now!

I had to take down the centralized antispam backlist because it's really eating up a lot of resources, thus slowing down the main site.

If you really rely on the centralized blacklist more than on your own spam defeating techniques (or on the new Phoenix techniques), I'd like to hear from you.

Also, in order to put the list back up, we could really really use someone willing to provide some server CPU & RAM to run something like antispam.b2evolution.net . It's mostly about processing SQL queries in memory. It's not that much about bandwidth or disk space. If you feel like giving it a try, please step forward ;) Thanks!

-François.

Update: we have a new server for the antispam blacklist.

I stumbled on it by accident, but I thought it was cool enough to mention:

the W3C Mobile Web Best Practices Working Group uses b2evolution! B)

Best of all, making the weeb more usable in the mobile arena is something I'm very interested in ;)

The map below shows where the b2evo team members are located...

But you can do more! Click on the map, zoom in and add your own pin with the URL of your own b2evo blog! See where the other users are... meet you at frappr.com !

PHPBuilder has a really well done tutorial on setting up b2evolution.

This tutorial – written by Ian Gilfillan – will walk you through the installation and all the base features of b2evo, providing screenshots for each step.

Nice! :D

Another frequent question about Phoenix is: What are these "workflow" fields for?

Workflow fields are: Status, Assigned to, Priority and Deadline.

These fields are particularly useful when you are publishing a professional blog which involves several editors before a post goes public. You would typically create new posts as Drafts and then Assign them to someone for review, with a given priority and/or deadline.

You can use none, all or only several fields at your convenience.

The Status field is there in case "draft" is not enough for you. You can add your own custom statuses under the Settings tab. You might want to create statuses such as "idea", "to be reviewed", "needs spell check", "needs final approval", etc.

You will also discover some brand new uses of b2evo with these fields in future releases (probably starting in 1.7)

Now, if you don't need this at all and you think it's just an annoyance on your screen, rest assured, we'll give you an option to turn this off completely very soon. Even better, we'l give you control over hald a dozen of features of the edit screen, allowing you to display just as much as you really need and keeping the other features under the hood, just in case you need them sometime later.