Once upon a time, there was a Backstage

With Luna 2.0 Preview 1 coming along nicely, I found it kinda fitting to go over the history of the Backstage. We’ve done this before, prior to the launch of ModernBB 3.3, but this time around, there is so much more to say about the Backstage. So let’s take a look at how we got from Dashboard 1.6 in ModernBB 1.6 to Backstage 6.0 “Astrid” in Luna 2.0.

Dashboard 1.6/1.7

adminpanel1.6

Framework: None / Icon set: None / Awesomeness: 11%

As ModernBB 1.x was more of a maintenance release to continue where FluxBB failed, the Dashboard that could be found in these early ModernBB versions wasn’t anything different from FluxBB. What you see above is an interface that isn’t responsive and not optimized for management at all. It’s actually quiet boring. Moving on…

Dashboard 2.0

dashboard2.0

Framework: Bootstrap 2.3.2 / Icon set: None / Awesomeness: 24%

Similar to Luna 2.0, the first beta of ModernBB 2.0 focused on revamping the Dashboard – and only the Dashboard. This is where the basic structure that is still in use today, is introduced. Not only that, but for the first time in ModernBB’s history (which includes PunBB’s and FluxBB’s) a framework is introduced. In this case, it was Bootstrap 2.3.2. It’s the first time it appears, and also the last. But I’m gonna be honest with myself, the UI was a mess. Let me illustrate:

dashboard2.0bis

That’s the Settings-page. The very same page we’re now getting very positive feedback on. Let me be clear: this version… not that positive. And I can only say that I agree. Somehow, I found it a good look back in the day, now I don’t.

Backstage 2.1

dashboard2.0bis2

Framework: Bootstrap 2.3.2 / Icon set: None / Awesomeness: 27%

In beta 2 of ModernBB 2.0, not that much changed about the design, however, a notable change in functionality was that the index now included features instead of just a list of things you could do. And another obvious change was the introduction of the word “Backstage”.

Backstage 3.0

backstage3.0

Framework: Bootstrap 3.0.0 / Icon set: None / Awesomeness: 43%

Then ModernBB 2.0 beta 3 happened. Not only did this release revamp the front-end completely – something that’s totally besides the point for this blog post – but it also revamped the Backstage. Big time. We kicked Bootstrap 2 out, and included Bootstrap 3 instead. Thank god, you might say, because for the first time, the Backstage was finally taking shape.

Beyond a visual refresh – as you can see below – not that much changed to the Backstage in ModernBB 2.0’s releases after beta 3. It didn’t change a thing in ModernBB 2.1 either. The only notable difference was that Bootstrap got updated to version 3.0.2, and even that isn’t that notable at all.

backstage3.0bis

Backstage 3.1

backstage3.1

Framework: Bootstrap 3.0.3 / Icon set: None / Awesomeness: 51%

Little note: so far, non of the versions of Backstage where actually responsive. Backstage 3.1 did bring a responsive design. A poor implementation, but one nonetheless. This puts ModernBB in history as one of the first forum software to have a fully responsive design, thanks to Bootstrap. Version 3.1 also introduced the now much used panel-button (as can be seen in the “New reports” panel). For some reason, we also made the design wider. I don’t know why, but we did.

Backstage 4.0

backstage4.0

Framework: Bootstrap 3.1.1 / Icon set: Glyphicons / Awesomeness: 59%

ModernBB 3.0 introduced a less colorfull design (though it did introduce the idea of accents). It is however notable for – what I believe to be – the first good implementation of Bootstrap in ModernBB. The result was a properly functioning responsive design and a much cleaner interface overall. Through later versions would still improve on that, it was a major improvement. Also, we started using icons in the Backstage in version 4.0 too. ModernBB 3.1 and 3.2 also used Backstage 4.0 with some minor adjustments.

Backstage 4.1

backstage4.1

Framework: Bootstrap 3.1.1 / Icon set: Glyphicons / Awesomeness: 49%

And this is the point where we got into a personality crisis. Backstage was redesigned with a more colorful interface once more. And a bright on. A little to bright (but the worst has yet to come). This version of Backstage did introduce the accent system we use today (that is, setting the accent). ModernBB 3.4.3 would upgrade Bootstrap to version 3.2.0, but did not bring any other visual changes. It was a release I am particulary proud of, the Backstage design? Not so much.

Backstage 4.2

backstage4.2

Framework: Bootstrap 3.2.0 / Icon set: Glyphicons / Awesomeness: 56%

As if Backstage 4.1 wasn’t bright enough, version 4.2 made the navbar white. White! It did make the design look more professional and all, but it certainly was a downgrade for people working often in dark spaces with not enough light.

Backstage 4.3

backstage4.3

Framework: Bootstrap 3.3.1 / Icon set: Glyphicons / Awesomeness: 64%

The good news is that that light design didn’t last that long. ModernBB 3.6 started to introduce design aspects that could be found in the Luna Preview 0 builds from that time. This time, the Backstage did gain a functional update: touch-friendly dropdowns for tablet users. Backstage 4.3 is basically the last iteration of the Backstage 2-based series. ModernBB 3.7 used the exact same code for it’s Backstage and after that, it was Luna all the way. But ModernBB had one last update…

Backstage 4.9

backstage4.9

Framework: Bootstrap 3.3.5 / Icon set: Font Awesome 4.4 / Awesomeness: 83%

ModernBB 4 brought Backstage 4.9 along. This version of the Backstage was a back-port of the Backstage that could be found in Luna 1.1. It brought Font Awesome as the icon set to ModernBB and was the final ModernBB release.

Backstage 5.0

backstage5.0

Framework: TrentUI 1.0 / Icon set: Font Awesome 4.2 / Awesomeness: 71%

So, now we go backwards. Backstage 5.0 is older then version 4.3 and 4.9. This is the first itteration of Backstage since version 4.2. It introduced a brand new design and 2 noticable framework changes: Bootstrap was set aside for TrentUI (a Bootstrap fork) and Font Awesome took over the Glyphicons usage. Perhaps more important: this update changed the menu and required less navigation within the hamburger menu on small screens. Later revisions did put Bootstrap 3.3.0 back in place.

Backstage 5.1

backstage5.1

Framework: Bootstrap 3.3.1 / Icon set: Font Awesome 4.2 / Awesomeness: 82%

Luna 1.0 Preview 1 brough along a familiar design if you’re used to todays versions of Luna. The interface was made darker and flatter.

Backstage 5.2

backstage5.2

Framework: Bootstrap 3.3.1 / Icon set: Font Awesome 4.2 / Awesomeness: 84%

Luna 1.0 Preview 2 made panel headings more distict and stand out and brought minor visual changes. It was basically the last major itteration of the Backstage for the Luna 1.0-branch. 1.0.7 brought the “brand”-update, which included our lighter blue brand color, the one still in use today.

Backstage 5.3

backstage5.3

Framework: Bootstrap 3.3.5 / Icon set: Font Awesome 4.3 / Awesomeness: 87%

Which brings us to todays Backstage. While both Bootstrap and Font Awesome have been updated since the original Backstage 5.3 release (as part of Luna 1.1), the design has remained the same and no big changes where applied. It’s our best Backstage yet that’s publicly available. But we have one version that’s even better: Backstage 6 “Astrid” right now in development.

Lessons learned

After a little less then 3 year of iteration changes and 2 major revamps (Backstage 2 and 5), you might think that we’ve learned our lessons on how to make a great administration interface. And yes, we did. And all of that is going to come together in the 6th version of the Backstage, and the third major revamp (though, since it is a rebuild from scratch, you might say it’s the first major revamp). It’s going to be gorgeous. We’ll have a blog post up about Luna 2.0 Preview 1 early next year, so stay tuned!

What’s in a codename?

So today, I discovered that there is a Wikipedia article about ModernBB (which also covers Luna). Awesome! Thumbs up for the guy that’s keeping the information on it up-to-date. Anyway, I decided to read through the whole lemma, and then, I came across this:

Similar to other software, like WordPress, main releases are named with code names. However, the logic used for ModernBB’s code names is unknown. Some releases share the same code name.

It sure knew to steal my attention. Why? Because it’s right. There is no logic in the ModernBB codenames. Will there be any kind of logic in Luna codenames? Probably, but remember, they are what the name says: codenames. Nothing more, nothing less.

ModernBB Codenames
While ModernBB 1.6 is called Blythe, it didn’t had a codename until ModernBB 2.0 was named Zoe. Both codenames came from the same source: Hasbro (that big entertainment company, you know, like Monopoly and stuff). 1.7 just took the 1.6 codename due to it not being such a big release. However, releases being small isn’t the only reason we stick to a codename. 2.1 and 2.2 where both named Zoe, too. There is no reason for that naming convention.

ModernBB 3.0 was named Odd. Because it was version 3, and uneven number, which is also called “odd”. Also, “Odd” is a name in some countries. ModernBB 3.1 and 3.2 where both named Mellow. These 2 releases sharing a name, did have a reason. Both releases putted the focus on revamping the front-end design. Its codename wasn’t ment to be the word “mellow”, through. It actualy comes from “marshmallow”. But we thought that was to long and shortened it to “Mallow” and then we switched the a for an e. I didn’t even realize at the moment it was an actual word.

ModernBB 3.3 was named Vanellope, after the Vanellope project I did in the months prior to it, of which it also got a lot of code. Anyway, that project’s name on its own was from Wreck-it Ralph, a Disney movie. One of the characters was named “Vanellope von Sweetz” (or something). ModernBB 3.4 was named Neon, and at that point, we did plan to introduce a logic in naming our releases: after the elements. Didn’t happen, through. The next version, ModernBB 3.5, was named Kate. ModernBB 3.6 and 3.7 are both named Blue. We just took names, there really is no reason behind these names. 3.6 and 3.7 share the same name because we don’t think it’s worth it to give it new names.

Luna Codenames
Luna continues to use codenames. Aero is an example, the codename for Luna 1.0. “Luna” as a name itself was a codename until it became our final name. We currently call our 1.1 milestone Luna 1.1 Bittersweet Shimmer. Another update, that currently doesn’t have a version number is Luna Denim. There is an updated planned in between Bittersweet Shimmer and Denim, so that’s going to be something with a C. Anyway, for the people that didn’t notice it: Aero, Bittersweet Shimmer and Denim are all colors. In alphabetic order. So there you have our logic. Finally.

Evolving ModernBB: The Backstage

As al of you might know – or not – ModernBB 3.3 will contain a new fresh design for the Backstage, because the head of Studio 384 told us so. Well not entirely, I made up some design guidlines and tought “I should add those to ModernBB and ModernCount too…”. Anyway, a couple of days ago, we showed you how the profile interface evolved, let’s do that again, but now for the Backstage (also the index page). Later on, I’m planning to talk about our default design in general too.

backstage20b1

I didn’t make a screenshot of the ModernBB 1.6 Control Panel design (no Backstage back in those days, neither at this level of development). But I can tell you: it looked prety stuped, the same content as above, but with another layout. Anyway, as you can see, the Control Panel/Dashboard (as it was called during ModernBB 2 beta 1) only contained a list of stuff you could do, and it gave you the ModernBB version and a link to the server statistics. Kind of useless (and one of the reasons that ModernBB exist, the same page and content is used in FluxBB). Anyway, I am proud of the navbar design, Aurora was born (the name of the style).

backstage20b2

ModernBB 2 beta 2 added a lot of functionality to this page. We added a link to the back-up page, show new reports and the forums default statistics. On top of the page, we also added a “Welcome to ModernBB” alert. And the automatic update check was introduced on this page too. The “Extensions” link is now also disabled when no extensions are available. Also, beta 2 introduced the “Backstage” name. Note the silly introduction under “Welcome to your Backstage”. We updated Aurore to version 1.1! Yay!

backstage20b3

While functional an improvement, I wasn’t too happy with the ModernBB 2 beta 2 Backstage. Beta 3, the unexpected extra beta, that also throw the old front-end over board, redesigned the Backstage completely. We started using Bootstrap panels and introduced Aurora 2.0. A huge improvement. As you can see, it’s a very flat design. And the navbar is very similar to the ModernBB 3.0/3.1/3.2 design.

backstage20rc1

But neither was I happy with Aurore 2.0, and thus, the Aurore 1 design was reïntroduced in Aurore 3. Aurore 3 was a serious clean-up from the previous versions of Aurore. And another good indication that I’m very bad at versioning, we’re now at ModernBB 2 RC 1, and are already running arround with Aurore 3…

backstage21b

Aurore 3.1 was part of ModernBB 2.1 (we didn’t change to much anymore after RC1, of course). As you can see, titles where now blue (the statics panels content are titles).

backstage22b

ModernBB 2.2 introduced Aurore 3.2, which included a feature that, starting from that release, is used everywhere in ModernBB: panel title buttons. Take a look at the report panel, the “View all” link has been replaced with a nice button on the right hand side of the panels titlebar. We also updated the alert styles.

backstage30a1

While only been seen in 1 development release, Aurore 2 was the inspiration for the Aurore 4 design. This time, we went with some nice gradients. We started using icons in the navbar, added titles to all Backstage pages that didn’t had one yet, and kicked out the full “Time to update” warning. Intresting about this design is, while introduced in ModernBB 3, it was supposed to come to ModernBB 2 in an unreleased ModernBB 2.3. Version 2.3 of ModernBB has been in development, but never made it, due to the works on ModernBB 3. Aurore 4 supported accent colors, through only “ModernBB Blue” and “Blue” are available. After Aurore 4, not to much has changed about the Backstage. ModernBB 3.1 and 3.2 are still using the exact same design, it hasn’t been touched ever since.

ModernBB 3.3 will introduce Aurore 5, in contrast with Aurore 1, 2, 3 and 4, it has been build from the ground up. It will support a brand new design. Accent colors will be used more intensive, as you will get support for ModernBB Blue, Yellow, Red and Lime. I think a lot of people are going to like it. With Aurore 5, we’re going back to flat design, like Aurore 2, but flatter. I don’t have a screenshot now, if you want to see it, you should try out the version3.3 branch.

ModernBB 3.0 “Odd” now available

modernbb300

We’re three and a half month after the release of ModernBB 2.2, and we have a new major update ready for you! I’m proud to announce the availability of ModernBB 3.0. As always, you can find the latest version of ModernBB at our download page!

What’s new?

  • New Backstage: The Backstage design has been Improved to be more clear, more structured and more awesome. Give it your own touch with a new setting in your profile, allowing you to change the accent color.
  • Reset: you can now reset your forum with soft and hard reset!
  • Kindness and friends: Kindness has returned. The style that was available for ModernBB 2.0 but was removed in 2.1 is back. The other 3 styles also had some major improvements.
  • WYSIWYG: The editor has been replaced with a brand new one, the new TinyMCE based editor allows you to see what you’re going to post.
  • New parser abilities: The parser is now capable of understanding all h1 – h6 tags and a new c-tag, wich allows to use inline code.
  • New components: Bootstrap and jQuery have been updated to the latest release and TinyMCE is a new component in the software (causing it to be rather big than usual).
  • Many, many more…

Of course, we recommend you to update to the latest version of ModernBB. It’s important to make a backup before you update your forums to ModernBB 3.0. Note that ModernBB 3.0 requires PHP 5.1 and a database running MySQL 5.0 or higher or SQLite 2.

Vanellope: 2 months of awesomeness behind us

vanellope10d

So, 2 months ago, we made the first commit to Vanellope. Today, we’re working hard on this project to hit a usable state somewhere in June. That is only 3 months from now. So, let’s hope we will get there in time. Through I’m afraid we won’t. But hey, stay optimistic! We’re still in scheme, and release is still planned for early 2015. But let’s go over the current state. Also, if you’re more intrested in how it is going with ModernBB 3, you should read the last paragraphe of this post.

Vanellope Alpha 1 Development
Anyway, for Vanellope, we’ve decided to drop all code we made a week ago. Yes, everything is gone again. Anyway, we’re retriving a lot of it, like the design and basic features like the update check, new style page and more. We’re back to our original plan, to make this a clean rewrite. Sad as it is, the plugin system we hoped to get in there, won’t be happening and is now on track for a future release, through I can’t tell if that will be Luna, Yellow or any later release. We’re probably going to make it the main focus for one of the updates that are coming up.

Anyway, like said before, we’re still on track to get Vanellope out of development at the begin of 2015. Our first public alpha release is planned for June 2014, while the first beta should follow in August, and the first RC in November 2014. The final? Early January 2015 is your time! Stay tuned for more specific dates, through. When we hit the Alpha 1 milestone, we will give an updated on the dates.

Development of Vanellope is going fast. We’ve got our design, and it shines. We’re now working on the Backstage, setting up pages for the settings we’re going to support, the main structure of it and so on. We’re also working on a new installation script and a nice update script. Together, those 2 milestones form “phase 1” of the development cycle for Alpha 1, “phase 2” is the whole front-end: forums, categories, topics, profiles and so on. PHase 2 is supposed to start somewhere in April or May.

ModernBB 3 Final
In the world of the already released versions, development of ModernBB 3 has been quite these times. I know this, and I’ll be working on this in the near future, I hope to close some tickets this week and am now planning to release ModernBB 3 at the end of the month.

Vanellope – it could happen

vanellope_planning
So, we’ve been working on this for a while now, let’s do a quick recap of everything that happened the past 1,5 months, because it is prety big, what has happened. We’ll talk about development, planning, branding and more.

Branding
So yeah, we’re now calling Project Luna “Vanellope”. Nothing new here, we’ve been doing that on our site for a while now, yesterday however, we pushed this also to the actual project (which was using both Luna and Vanellope as branding). Since we already have a codename that’s also name Vanellope (update 1.1), we’ll give version 1.1 codename Luna instead, just to make it more clear. The repository will also be moved in the near future. You won’t find it anymore at github.com/ModernBB/Vanellope, but at github.com/Vanellope/Vanellope. We have got our hands on the Vanellope username on GitHub. 🙂 We’ll fix that last branding issues on our site in the upcoming week.

Planning
So, a couple of days ago, the Vanellope project page on ModernBB.be was updated with Yellow, update 1.2. This will be the second update for Vanellope, planned to launch in the summer of 2015. That’s a while from now… Just like Luna (which is now update 1.1), this release will add features that didn’t made it to our first stable release. Update 1.3 and update 1.4 will be released in Fall 2015 and Winter 2015/2016 respectivly, from there on, we want to have 3 major updates each year (kind of WordPress-like).

Version 1.0 itself didn’t change that much on our schedual. In fact, it stayed the same, we’re still planning to launch our first alpha somewhere this summer, probably in June. The beta, RC and final stage are also still on their usual dates. Anyway, we’ve also some news on when we won’t support ModernBB anymore: support will end after the Luna update has been released. That’s a year from now. Meanwhile, we’ll finish ModernBB 3.0 next month and might release another ModernBB 3.1 update.

Development
This is a very exciting part of the past month. Development of Vanellope has taken of over a month ago, and we’ve made already more then 150 commits to the repository. Slowly, we are making progress in rewriting the whole ModernBB source, into a much more advanced piece of software. Currently, we’re working on striping down the features and making the core more simple. Then we’ll add everything again. Currenlty, we’re spending a lot of time on the design, the front-end is being reimagened and so is the Backstage (however, we’re not quit happy with it’s design). The front-end is looking good for now. Anyway, we do recommend to not use the Vanellope software on this early stage of development.

ModernBB 3.0 beta now available

modernbb30b
So, I’m a day to late, but anyway, we’re making a blog post about it. Yesterday, I tagged ModernBB 3.0 beta! The first, and last beta version of ModernBB 3 is now available for download. It’s not a stunning update compared to alpha 3, so we’re not going big over the changes. For developers, it might be a good time to check you plugins, since everything that started with pun_ is renamed to luna_.

ModernBB 3.00 alpha 3 now available

modernbb30d
I’m glad to announce that ModernBB 3.00 alpha 3 (version 3.00-dev.1701) is available from now on. This is our third ModernBB 3 release, and like the name says, it’s an alpha release. So we do recommend to not update your installation in a productive environment. Anyway, let’s talk about what’s new, and the future of ModernBB 3.

ModernBB 3.00 Alpha 3
This final alpha version (the next one will be the beta) mainly focused on improving the new WYSIWYG editor. We’ve added a lot of bugfixes and improvements to this new feature. We’ve also included the stable releases of Bootstrap 3.1 and jQuery 2.1. Further on, the responsive design has been Improved. We made some improvements to the Backstage, updated the email page and fixed some bugs. It’s also possible to disable the statistics on the front page. That’s it, nothing to special in this alpha.

Roadmap ahead
Now, our next release will be the first and last beta release of ModernBB 3.0 (not a typo, I realy mean 30, not 3.00). 2 weeks ago, I announced that you could get your hands on ModernBB 3 on 29 March, now this is 9 March. Tickets that don’t make it in the upcoming 2 weeks won’t be part of ModernBB 3, since the beta will be our feature-freezz. Then, 2 weeks later, our RC will folow, followed by ModernBB 3.0.0 on the 9th day of March.

Meanwhile, we are working on Luna. Our next big project and the replacement of ModernBB in the future. I’m not going to talk to much about that release in this blog post, may be for another time…

Roadmap changes: 3, Luna and Vanellope

luna_planning
Earlier today, we’ve made some big changes to our roadmap and website in general which you might want to check out. What’s going on? Well, we’re changing plans, like we do so much, for ModernBB 3 and Luna. Also, meet Vanellope. Let me introduce you to our updatet roadmap.

ModernBB 3
First things first, ModernBB 3. Today, we’ve decided to launch only 1 beta and 1 release candidate of ModerBB 3 before the final will be released, instead of 3 betas and 2 RCs. We don’t feel like we needed all the time we had planned in first. Of course, this could be the result of features I’m not going to develop for ModernBB 3 anymore. So, you can expect ModernBB 3 to launch this 9th March 2014, if not even earlier. In the upcoming days, we might put it on 2nd March 2014.

From there on, we will start developing ModernBB 3.05, the first minor feature release for ModernBB 3, however, do not expect to much from it. The reason behind the change of release dates is that I don’t want to spend much time anymore on the ModernBB project, in fact, I’m pulling the plug. ModernBB 3 will be supported until the next release, when that happens, it’s goodbye ModernBB.

Meanwhile…
By now, you might start to get confused. We’re pulling the plug? It’s over for ModernBB? What…? Well, yes, and I’ve announced this a while ago already, but not with those words. I’m not planning to go anything further with ModernBB. So, what about Luna then? Well… you might want to read the updated paper (link comes later in this post). Because…:

Luna
It’s no longer ModernBB “Luna” 4.00, no, just Luna. We’re seriously concidering to drop the ModernBB brand in the future and replace it by a better brand that better fits (not sure what yet). Anyway, as we announced already, Luna will be build up from the ground. Not only will it have a brand new core, we will also start back at version 1. We’ve already started with the development of Luna. The repository is ready, we’re collecting all packages we need for the development to begin and will soon (if not today, then tomorrow) enter the design stage.

Well, Luna will be an awesome project I think. But since the brand might get ditched, where will you be able to download it? Well, just here, at modernbb.be. But we should, of course, move to another address as soon as our brand change and redirect people to that address. Our goal with Luna stays the same: get a modern and basic forum system on its feets. However, we’re not going with the classic forum concept. But mix it a bit more to make it a social experience too. How this will work out will be reveiled later on (I don’t know either how I’m going to do this anyway). Anyway, read our updated paper for more about Luna.

Vanellope
Vanellope will be what comes after Luna. It will be our first feature update, version 1.1 (we will go with semantic versioning again). This release will be a polishing release. It’s supposed to improve upon everything we have by then and make it more feature complete. Since this release is prety far away, I don’t have much to talk about for now. Anyway, for the people that might wonder: where does that codename come from? Well, it’s from Wreck-It Ralph (that 2012 Disney movie). The full name is actualy Vanellope von Sweetz, but who cares.

ModernBB 3.00 alpha 2 now available

modernbb30d
I’m glad to announce that ModernBB 3.00 alpha 2 (version 3.00-dev.1644) is available from now on. This is our second ModernBB 3 release, and like the name says, it’s an alpha release. So we do recommend to not update your installation in a productive environment. Anyway, let’s talk about what’s new and when alpha 3 will be released.

New in ModernBB 3.00 Alpha 2
The update check has been Improved and now uses caching to save results, instead of loading it again and again. We also cleaned up the statistics page in the Backstage. You will also find a new page called “ModernBB software updates” where you will be able to update in later versions. It also includes 4 new maintenance options, 2 of which now work. Those are Soft reset and Hard reset.

On the front-end side of things, we’ve added an option to disable your forums description without leaving the  description field blanc. Topics now also use a h2-title to make it more clear what topic you are reading. On the index page, the last active topics title has been added. When moderating a topic, you will now be able to select an “All” option to show everything. We’ve also closed the ticket regarding the login and update screen design. When editing a post, you will now see an updated design. Further on, the error() function now trows a nicer error design. Finaly, Randomness has been updated with some small fixes.

This release also includes a new WYSIWYG editor to replace the normal editor from ModernBB 2.x. It uses TinyMCE 4.0.12. Regarding this, the feature is not finished yet, so the tickets are still open. Anyway, the parser now supports al title tags, from H1 to H6. We also fixed some integration issues. We’ve got also some improvements for security for this release, as the confirm_refferer() function has returned (it was removed in 2.0). We also updated the maintenance page.

Other smaller improvements are some updates to breadcrumbs, the inclusion of TinyMCE 4.0.12 as a package. You can no longer resize textareas verticaly. It’s now also possible again to save te Antispam API. Finaly, we dropped support for Internet Explorer 8.

Roadmap changes
We’ve got still a lot of work to do. For the planning we had, we had still more than 3 months to settle everything right. Well, I’m gonna reduce that time. While you would have to wait until 24 April 2014 before you could get your hands on our final ModernBB 3.00 release, you will now be able to get it 1 month earlier, on 29 March 2014. This happened because we won’t release an Alpha 4, nor a Beta 3. Meanwhile, the next alpha release should be here the 1st February, and improve the editor, and should enable updating with 1 single click, let’s hope the best for it!