You may have noticed that the b2evolution.net site is now powered by b2evolution v6.6 and that we have started upgrading sections (skins) to bootstrap skins, effectively making this site responsive as well.
You gave us awesome feedback so far, and we have implemented most of what you requested. A few requests are still in the pipeline, as fixing v6 bugs was a priority over new features. But worry not, if we said we were going to implement it, you’ll see it in the next couple of months.
As you check out b2evolution v6, please continue telling us what you think and what you need. No matter how small or how big! If we can make it happen, we will!
You have probably seen the invitation to upgrade on your dashboard last week. If you haven’t, please be advised we issued a security release (version 5.2.1) and for optimal security, we encourage everyone to upgrade.
If you’re using b2evolution 5.1+, you can upgrade very quickly with the auto-upgrade feature. Otherwise you can download the release here.
Translations & language packs
Now that version 5.x is very stable and not evolving much any more, we are updating all the language packs.
If you’d like to help translating b2evolution to your own language, now is a good time to head over to our Transifex Project Page where you can sign up for free and translate one, a hundred, or a thousand strings. You can also use Transifex to efficiently report any inconsistency or any problem you noticed while using the app in your own language: search for the problematic string and leave a comment on it (mark it as an issue). Of course, if you know a better translation, type it in!
b2evolution v. 6
We regularly update the development version of b2evolution version 6 on GitHub. If you’re interested in the latest cutting edge version of b2evolution and don’t mind a few bugs, you can get it from there.
This month we’ve got some heavy releases! One stable and one alpha!
Version 5.2 (stable)
Beginning of December we released b2evolution 5.2.0-stable. Many bug fixes. Rock solid. It’s a recommended upgrade for everyone. Get it here.
Version 6.0 (alpha)
This is codenamed "i7" and it’s actually not really released yet BUT you can get it on GitHub since today! ;)
This one is really a massive leap forward with tons of new features. We haven’t even documented all the features yet but you’ll find some of them listed here.
This branch actually makes 5.2 seem obsolete already, but as we haven’t fully tested everything yet, we call it "alpha" still. Nevertheless, we wanted to make this available to our true fans without further delay.
If you have some time to play during the Holidays, we believe this should keep you busy for a little while ;)
Please feel free to report bugs for this version already. We’ll make fixes available on GitHub as we progress.
What happened to October & November?
I (francois) haven’t posted any news in the last couple of months. Sorry about that. I was all absorbed in the birth of my first son ;) Despite the silence, we have a great dev team who has worked relentlessly in between. I think that if you look at i7 you will notice! :)
In the meantime, please remember you can always get an up-to-date version, including the latest fixes, on Github here: https://github.com/b2evolution/b2evolution . This would be a good habit to take as we’re going to update GitHub even more frequently in the future. We’re also working on importing the previous project history onto GitHub (thanks to blueyed).
Before the summer we posted quite a few interesting links about web design, front-end development and more generally: techniques to improve your website that complement the use of b2evolution. Did you find those helpful? Would you like some more?
While version 5.1.2 will remain unchanged, upcoming versions (internally "i7" which will probably translate to "6.0") will rely entirely on UTF-8. This is made possible because most web hosts now correctly support UTF-8 in PHP and MySQL which certainly wasn’t the case when we started b2evolution.
But we’re doing it not just because it’s possible. We’re doing it mostly because many users seem to have encoding problems as soon as they run blogs in multiple languages. By standardizing them all on a common character set — and UTF-8 is the de-facto standard for that — all those charset headaches might as well magically go away.
We also have a fallback for old web hosts that don’t have native UTF-8 support, at the expense of a small performance impact.
Globally we feel that moving towards UTF-8 will help us better fulfill our mission of providing a blog/CMS platform that just works from the moment you install it and with any content you add to it.