There we are. The latest and probably the last of the 0.9.x series is available now.

Download here.

If you are running version 0.9.1, here are the news:

• Bug fixes
• More spam detecting techiques
• More locales: Basque eu_ES, Icelandic is-IS, Polish pl-PL, Estonian ee-ET, Russian ru-RU

Plus, you'll probably never get a 0.9.x update again! From now on, all efforts will go onto the new 1.8 "Phoenix" release.

Note: You still want to run 0.9.2 on heavy loaded production servers because it's still more efficient than the feature packed Phoenix releases. If you have CPU to spare on your server though, then you may want to upgrade to Phoenix in a couple of weeks.

Update: Thanks to Vee, we now have a small download available which contains only the files which have significantly changed since verison 0.9.1 (comment changes have been left out).

Thanks to Ed (Head of Central Antispam) and Ryan (New Host), we now have a brand new host for our central antispam list. It's a separate host from the main site, so we might get better performance on the one or the other if not both

Because it's a new server, you will need to do some small modifications to your b2evo installation if you want to take advantage of it.

Pick your easiest solution:

Solution 1

You're not in a hurry: just wait for the next 0.9.2 [Update: available now] or 1.8-alpha release and you'll be fine.

Solution 2

You care a lot about antispam, but not so much about pinging b2evo when you publish a new post.

Just go into your /conf/_advanced.php file, and at the end of the file replace this line:

$evonetsrv_host = 'b2evolution.net';

with this line:

$evonetsrv_host = 'antispam.b2evolution.net';

Solution 3

You're running version 0.9.1 and you want it all:

Go the end of your /conf/_advanced.php file, and add the following lines:

$antispamsrv_host = 'antispam.b2evolution.net';
$antispamsrv_port = 80;
$antispamsrv_uri = '/evonetsrv/xmlrpc.php';

Note the $antispamsrv prefix. It is different from the existing $evonetsrv lines.

Download this file and use it to replace your existing /b2evocore/_functions_antispam.php file. (If you have trouble with downloading the PHP file, you can get this ZIPped file instead).

CVS

Note: CVS servers are not up to date right now because SourceForge? has had them down for the whole week... stay tuned.

Update: 0.9.2 is now up to date on CVS (look for the v-0-9-1 branch).

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

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!

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!

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.

One question that is comming back frequently is: What happened to the language files in Phoenix? Why are there only translations for French, German and Japanese?

Actually all previous translations are still there in CVS. However we haven't shipped them with the release because they haven't been updated yet, i-e they do not contain translations for many many strings in Phoenix. Using the old files would only partially localize Phoenix to the desired language.

To update 0.9.x languages files to Phoenix, you need to merge them with the new .POT file found in Phoenix as described in the online manual.

Also, we're planning to only ship a limited number of localizations by default in future releases, in order to keep the main download file small. All other languages will be provided separately in their own language packs.

Ladies & gentlemen,

Though we're a little bit ashamed it took so long, we're also proud to announce that we're finally back with a brand new release and a load of brand new features.

The much anticipated Phoenix release is now available at SourceForge, you can get it here.

The main new features are:

• File manager
• Mailing lists/Subscriptions for new posts and/or new comments
• Group based blog permissions with presets for new users
• Enhanced user interface

The multiple domain support is still experimental and will work well only under specific conditions (you'll have to use the forums for more on that...)

More below...

This release is a real collaborative work with at least 15 contributors involved, some developping, some testing, some debugging, some validating... Many thanks to all of them!

This is an ALPHA release. This means it's far from perfect... but still, we already like it, use it, dig it... as it is! We only recommend that you upgrade if you are comfortable with patching bugs manually in case of need. Otherwise you should probably wait for the Phoenix Beta or Final.

This is a FEATURE release, not a PERFORMANCE release. So we don't recommend that you upgrade if you are running a production site with several thousands of users, of blogs or tens/hundreds of thousands of pges served every day. The "Dawn" release will still do a better job for this. This is not a promise, but we expect to come back to similar performance levels with version 1.7 or 1.8 .

Full story »