2015: A year in review and a year in preview

So… I wrote this post at the end of 2016, but forgot to post it. So here we go…

2015 was a big year for us. We release Luna 1.0, a major update to our software. And we also released the final ModernBB release. Let’s take a look at what we did this year:

We released 19 development versions (alphas), 13 pre-release versions (betas and RCs), 4 final versions (Aero, Bittersweet Shimmer, Cornflower Blue and Denim) and 19 updates (x.x.1-releases). In total, we released 55 versions of Luna. We also had 2 ModernBB-releases (version 3.7 and 4.0). This brings us on a total of 57 releases in 1 year. That’s up 17 from last year’s 40 releases and quiet a bit up from 2013’s 23 releases.

I’m also very happy with our download count. Compared to last year, we had a 60% year over year growth for the counted downloads. The bad news is, in the period of June to early November, we – sadly – didn’t count all downloads, so this could have been more.

But what will 2016 bring? Well…

First of all, I hope we’ll be releasing less updates. Sure, updates are fine, but some of the past year’s updates shouldn’t have happened. I hope that Luna 2.0 will bring along a more stable platform then 1.0.0, 1.1.0 and 1.2.0 have been so far (Luna 1.3.0 is doing just fine, though). I’ve also noticed that well, I should be a little bit more critical about contributions made by the community. Don’t get me wrong: I love that people help out with Luna and that’s more then welcome. But some commits shouldn’t have happened either and I’m not to happy about some of the directions Luna has been going into the past year (and Luna 2 will revert these directions).

What I do hope is that 2016 will bring Luna 2.0. This won’t be for the coming months, I can tell that already. The first preview might, though. Luna 2.0 is probably going to be the final major update. Future updates will probably be more focused like the x.1-updates. Don’t worry, we’ll eventually get to Luna 3.0, but I’m hoping to adapt a more rolling-release-ish scheme for updates after the Luna 2.0-update is done. More on that later. I hope we’ll have a great 2016. I’m actually certain of it.

So now that I failed to put this one up on January 1st, 2016, I actually can reflect on what I said back than already. Where we’ve released 57 builds in 2015 in total, this year, we’ve only released 3 versions so far (1.3.1, 1.4-alpha.1 and 1.4-alpha.2). So to that matter, we’re on the right track. I hope 1.4 to be a very stable update from the get-go, despite it having some changes that are potentially dangerous.

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


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


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:


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


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


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.


Backstage 3.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


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


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


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


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


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


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


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


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


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!

Security update Luna 1.0.10 and 1.1.4

2 weeks ago, we got a report from Sfideremo about a security issue in all versions of ModernBB and Luna (and for the FluxBB users out there, you guys are affected too). And thus, we’re releasing a security update for Luna 1.0 and 1.1 (and 1.2, but that’s a different post).

I’m not going into detail on how this security issue works, fact is, this CSFR-bug is rather easy to exploit and allows to lock, pin, unpin and open topics and to subscribe an unsubscribe to forums and mark as read without authorization.

We recommend everyone to update as soon as possible to Luna 1.1.4. If you’re still running Luna 1.0 and you’re not able to update (just yet) to Luna 1.1, we’ve got Luna 1.0.10 for you. In case you’re still running ModernBB now might be a good time to look into upgrading to Luna.

Except for this security issue, Luna 1.1.4 also comes with other changes. These include fixes to Fifteen and Sunrise in both Night mode and responsive design. Further, this updates comes with improvements to translations and fixes to the forum_list_accents() function. Finally, an issue that would cause messages in Inbox to not be marked as “read” even if you’ve clicked on the link has been fixed.

Luna 1.2 users can upgrade to Luna 1.2 Preview 3, which includes all these fixes and more. We’ll post another post about Preview 3 as well as this update contains many more changes.

Special thanks to Sfideremo for reporting this issue and to the FluxBB.org team (which will also release version 1.5.9) to help fixing this bug.

For now, we can’t tell wheter or not we will release an update for ModernBB. I don’t leave this out of the question, but as we never intended to support ModernBB beyond the 4.0.0-milestone, this is kinda an open field. Reach out to us on our board, Gitter or Twitter so we can know wheter or not there is any demand for it.

Luna 1.1.2 and 1.0.8 now available

Today, we’re happy to release Luna 1.1.2 and 1.0.8. These 2 updates both bring some minor changes to the Luna platform as a whole, including the restructuring that was announced in the previous post.

Luna 1.1.2 and 1.0.8
Luna 1.1.2 and 1.0.8 both include a revamped “About”-page, which now has a more constructive list of changes. Both updates also remove the Slow Ring from the update check and disable the automatic update check when you’re in the Nightly ring. Luna will instead provide a download button to download the latest build from the GitHub repository. Further, some minor bugs where fixed.

Luna 1.1.2
Besides the changes noted above, Luna 1.1.2 has Bittersweet Shimmer-specific fixes too.

GetLuna.org 2.0
Not only did we update our software, we also brought a major revamp to our website. Most pages are gone, we want to be much more straight-forward.

The first big change you’ll see is the removal of the Download and About section. The download section and some pages from about have been merged in the release notes page that you can find in the link under the download buttons on the index. From there, you can also download older versions.

The index now also asks for new developers to join up, so if you want, please contact us. Further, we’ve added the “Donate”-button to the main navigation. After all, Luna exist because of donations, but we’re not getting enough to maintain Luna, not even the host for our site. So we hope that more people will donate, as it would help is much.

Further, we’ve also updated the documentation. It has been split in 4 sections, of which 3 are now available. The 4th “Design guidelines” will be available in the near feature and goes mostly over design. Also, we’re preparing an update to list the new coding conventions for Luna 2.0 soon.

Onwards to better times

The development of Luna has crashed during this summer. First there was the planned development hiatus for my vacation that has been going for every summer now, then there was the death of a close friend of mine.

And all of that has realy dragged down the development of Luna. All time I had between these 2 drops went to ModernBB 4, meanwhile, for Luna 1.0.8, 1.1.2 and 1.2 Preview, almost nothing changed. That’s why its time to make some changes to the way we work, some undoing some of the changes I promised with the launch of Luna (see point 3).

First off – and this change has already taken place – I’ve reorganised the GitHub repositories and accounts that are being managed under the Luna brand (384forFluxBB, Vanellope and GetLuna). The first 2 have been removed, and for GetLuna, we’ve cleaned up a lot of the unused repositories in there, we hope to bring some order in this.

Secondly, releasing a new version of Luna is a real pain. During development, I usually write these changelogs as it goes along and that is something I’m not going to do in the future. This means that the “About”-page in the Backstage for future updates will be emptied and only display credits and the basic log we’ll use on GetLuna.org (this also applies to Luna 1.0 and 1.1).

Additional to that, releasing a new version is not an automated system for Luna, I just never got to set one up. The website is manualy updated with every new release. That’s why the website will get a major revamp, dropping most of the information that requires much resources (including these big changelogs, the features list, the download sections beyond the core and prety much everything in the about section (some of it will be relocated to the index)).

With this simplified website, which will launch alongside Luna 1.0.8 and 1.1.2, I’ll have much less work to do on keeping the website up-to-date and can focus more on the things that matter: Luna itself and the documentation (which will get revamped with the new site).

Thirdly, we’re changing the way we support versions of Luna. With the coming update to Luna 1.0.8, we will end support for Aero. We will only support the most recent version of Luna (which is at this point Luna 1.1). Only if there are security issues, we’ll release an update to the previous version of Luna. Further, after the 1.x.0 release, we won’t add new features like we did with Luna 1.0.1, 1.0.7 and 1.1.1. This will all be exclusive to the next minor update.

These changes will render the Slow ring you can select in the “Luna Software Update” page a potential security risk and thus, this feature will be removed in Luna 1.0.8, 1.1.2 and 1.2 Preview. Now, to sum it up, below are lists of what you can expect today for minor releases, and in red is everything we will stop doing for the future:

Current release -1

  • Minor feature improvements
  • Medium component updates
  • Minor component updates
  • Bug fixes (unless blocking issues)
  • Security fixes

Current release

  • Medium feature improvements
  • Minor feature improvements
  • Medium component updates
  • Minor component updates
  • Bug fixes
  • Security fixes

So mainly, just don’t expect any changes beyond bug fixes in the current branch anymore. Neither should you expect anything at all beyond security fixes in older versions. This basically makes that Luna 1.0.8 will probably be the final Luna 1.0 release, unless an important issue is found.

And to close of: as you’ve read above, this mainly is trying to reduce the work we have with supporting and maintaining Luna. But there is another fundamental change that needs to take place to keep this going, and that’s why the new website will also ask for people that are intrested in not simply using Luna, but also in developing it.

This might sound like something simple to do: add a button and go along with it. However, it’s not that easy. For starters, everyone working on Luna should use the same coding conventions, and since there are no coding conventions, that’s kinda a problem. A problem we’ll fix with Luna 2.0 as we’ll adapt the commonly used WordPress Coding Conventions. Additionaly, I’ll be extending the documentation in the near future to also describe our design conventions and naming conventions (for functions, constants, etc because I would like to seem them match what they are used for (astrid, jewel, zoe, sixteen).

The new website will also put the donate button right in the menu, it’s not used that often and we would like that to change for the obvious reasons that this will make it possible for me to develop Luna as one of my many other projects: as a job.

Luna 1.1.1 and 1.0.7 now available

Today, we happily announce the availability of Luna 1.0.7 and 1.1.1. This is our 7th update to our original code and our first to our first revision (logic right there my friends). However, todays updates bring a couple of great enhancements over version 1.0.6 and 1.1.0.

Luna 1.0.7 and 1.1.0
We’re happy to announce that, finally, Luna supports SQLite 3. Todays update adds the required adapter to our database layer and when installing Luna, you will – if available – see an option to install with SQLite 3. Also, when you remove posts from users, their post count doesn’t decrease, this behavior has now been changed. When you remove posts, the post count will also decrease. Further, we’ve made some improvements to the moderation interface in the Backstage. This looks now much better in both releases, though you’ll get a better interface with Luna 1.1. We also updated Bootstrap from version 3.3.4 to 3.3.5. Finally, we fixed a bug in both versions where the user settings would claim that the user’s email address wasn’t verified.

Luna 1.0.7 only
Luna 1.0.7 also comes with support for PHP 7. We introduced PHP 7 support in Luna 1.1.0, and are now bringing it to Luna 1.0, as we consider it a bug since our system requirements say that we support PHP 5.2 and above.

Luna 1.1.1 only
Luna 1.1 now comes with 2 new options under Settings > Appearance: you can now disable both Night mode and Accent colors. And finally, we’ve also fixed a bug for Luna 1.1.1 where you would get a blank screen when a config.php-file was present but couldn’t be linked to a database.

Get the updates
In case you are on Luna 1.0.6 or below, we recommend you to install Luna 1.0.7. Even better would be if you install Luna 1.1.1 (for everyone on Luna 1.1.0 and below, including FluxBB 1.4, 1.5 and all versions of ModernBB). Todays updates are worth it! Be sure to make a back-up of all your data before upgrading (you never know). Now, onto Luna 1.0.8, 1.1.2, 1.2.0 and 2.0.0 (yes, we’ve quiet some work to do).

Luna 1.0 “Aero” support
With todays update, Luna 1.0.7 might just be the largest update we’ve released so far for Luna 1.0 (while 1.0.1 and 1.0.2 had more changes, these where mainly bug fixes). And perhaps, that raises a question: with Luna 1.1 out, how long will Luna 1.0 be supported? Is the support cycle for older ModernBB-versions something to look at? The answer is no, it isn’t. Unlike ModernBB, we’re planning to support Luna version for quiet some time. Luna 1.0 will be supported for some time in the future, but do not expect us to release any more updates like 1.0.7. This can very well be the last time you see such a big update for Luna 1.0, or a feature update overall as our focus is now shifted to Luna 1.1, 1.2 and 2.0.

We’ll continue to deliver bug fixes and security updates for Luna 1.0, and if these bugs are also in Luna 1.1, the patches can very well be released at the same day, but in the future, you should expect less and less updates to Luna 1.0. We’ll announce when we’re killing of Luna 1.0 in the future, and otherwise, keep an eye on our roadmap page, which will also note the EOL-date (typical the release of the last update), through it’s fair to say that the EOL-date has been altered for a ModernBB release in the past, and we might do it again if something serious is wrong.

Luna 1.0.6 and 1.1 Preview 1.1 now available

Today, we’re releasing 2 new updates for Luna, for both Aero and Bittersweet Shimmer. We release these updates as important security updates due to a bug brought to our attention by Kaaleth (for which thank you).

Luna 1.0.6 and Luna 1.1 Preview 1 Update 1
Luna 1.0.6 and Luna 1.1 Preview 1 Update 1 consist out of the same fix. Moderators where able to change settings they where not authorized to change in the Backstage due to a bug in the navigation in the Backstage. This issue has been resolved.

However, both updates also come with another change: our May 2015 brand update. This brand update has also been applied to our website and blog, and now we’re adding it to our software. New installations will find themselves in a lighter environment as we changed the default accent color from dark to normal blue. Further, some images have been updated to reflect our new color pallet.

Luna 1.1 Preview 1 Update 1 only
For Luna 1.1 Preview 1 Update 1, there is another minor update to the language files. These now contain a series of reported strings that where missing from the file in an earlier update. So there you go, this also has been fixed. More strings might be missing, so please report them.

One-click update for Luna 1.1
Now we’re talking about Luna 1.1 Prevoew 1 anyway, like said yesterday, Luna 1.1 Preview 1 Update 1 would contain the fixed one-click updater. That isn’t the case in this release. The fix didn’t make it and we considered this security update to important to postpone until that was fixed. So now, the fix will be part of Luna 1.1 Preview 1 Update 2. However, Luna 1.1 Preview 1 users can upgrade to Preview 1.1 through the update system!

ModernBB: Luna’s about to replace it for good
Further, I also want to inform you guys that starting with the final release of Luna 1.1 Bittersweet Shimmer, we will officially start to push Luna as a replacement for ModernBB. I know that it is quiet obvious already, but we think that, with Luna 1.1, we are getting to a point where Luna is a very good replacement. Why aren’t we pushing Luna already? Well, I think the fact that we just released the sixth update to Luna 1.0 in 1,5 months is a very good statement. That isn’t much of a problem, through. I mean, Luna 1.0 is after all a “1.0” release. And while we concider it stable, bugs are to be expected. Luna 1.1 will be an even further polished version of Luna 1.0.6.

What does this mean in the big lines? Not much for you guys. The ModernBB.be site will send you to GetLuna.org on more locations (some pages already do so) and the “Download ModernBB 3.7” button will be removed from the front page. Of course, ModernBB downloads will continue to be available and we’ll continue to support ModernBB. Updates to fix bugs and security issues will be released until December 8th, 2015.

However, third-party downloads will be removed from the websites content too (themes, translations and plugins). With other words, the websites content will be limited to the minimum. The documentation will also start to redirect to Luna in the future. And well, we’re starting to draw the line for ModernBB.

Luna 1.0.4 now available

Not even a day has passed since the release of Luna 1.0.3 and Luna 1.0.4 is already available to all of you. Is there a flaw in Luna 1.0.3? Some kind of major bug? No. If you’re using Luna 1.0.3, you’re perfectly fine and have nothing to fear, however, there is an issue with Luna 1.0.3 that managed to get attention.

Since some pre-release version of Luna – I do not recall myself – we’ve been using colornames as the names for color schemes used in Luna and Sunrise. One of these names is “Black”. The corresponding color scheme, however, never uses the color black, but dark shades of grey. And apparently, it’s racist to call it that. So, here by, I would like to apologize to people that might have taken this as a racist remark.

The person/people that informed me about this “inacceptable situation” also asked me to remove all versions of Luna that do call this color scheme “Black”. And my response to that is simple: no, and neither am I going to replace them with updated versions that do not. These versions continue to be available for people that might need them.

Another requirement that was made was that I would track down all Luna-based boards and warn them to update to the latest version of Luna – 1.0.4 that is – because we would have found a “major issue”. And I’m not going to do that either. Luna has a build-in system that warns users for updates and I’m definitely not going to lie about what an update includes, we’re an open source project, users can go and find out for themselves anyway.

I’ve informed this person/these people about my position for the issues in the past to pharagraphs and I hope they understand. They already told me that they are prepared to take legal action and I simply do not have the resources to fight that. So here you go, Luna 1.0.4 is now available.

However, this isn’t the only change in Luna 1.0.4. To make it at least some kind of useful to upgrade, we’ve also included jQuery 2.1.4. This release of jQuery, in comparision with jQuery 2.1.3, should bring improvements to jQuery behavior on iOS devices (iPhone, iPad, iPod).

So, you know where to get the update, go fetch it if you’re still in Luna 1.0.2. If you’re on Luna 1.0.3, you can also update, but it will not benefit existings installations that much. Have fun!

Luna 1.0.3 now available

Today, we’re releasing the third update to Luna 1.0. Todays release is a small enhancement and bug fix release. Make sure to stay up-to-date.

Todays update updates the update system update check. When you’re in the Slow ring and are only receiving updates for Aero, there is a good chance that, after a couple of months and releases, we’ll stop supporting Aero. However, the updates doesn’t know that and thus it will continue to check for updates in Slow. We’re not going to automaticaly change to switch to Normal, but Luna will now display a red warning as soon as it finds out support for the version you’re using has been ended and no releases will be made. But again, it will take a while before you’re going to see this error as we’ve no plans to drop support for Luna 1.0 Aero right now and it will be supported for the forseable future.

Other changes have been made to the Backstage, where more icons have been added to fix some random usage of icons. Other changes that have been made is a fix for when you cancel a quote. We’ve also fixed a bug that shows up when you’re first login attempt fails and the second does not, where you would be redirected to login.php, this now redirects you to index.php. And finally, we’ve changed the location of a button in the admin area of the profile that caused a design glitch on mobile devices.

So, there you go. Be sure to make a back-up just in case. Nothing should go wrong with updates, but you never know. Now, we move on to Luna 1.0.4 and 1.1.

Luna 1.0.2 now available

The second update for Luna 1.0 is available starting today. Like version 1.0.1, Luna 1.0.2 comes with bug fixes and enhancements. You can find the download on the usual locations. So, what’s improved?

When searching for posts, and a topic appears more then once in the search results, they won’t link all to the same page anymore (which is the start post), but to their individual posts that caused the entry in the results. Also, when you would start writting a new message in Inbox, the focus will now be set on the “Send to” field so you can start to type when the page is ready.

Another change we made to Inbox is that, when enabled by the user (and it is enabled by default), users will now receive a mail with a notice that they have received a new Inbox message. Some board might have been sending empty mails when this happened, and in case you did, this should fix that issue too. Further, the installer has been cleaned up a bit.

The delete, soft delete and reset pages have been given a small design improvement to fit better in. And in both the Mainstage as Backstage, we’ve improved the navigation bar design for mobile devices, they now look better. Further 2 bugs, of which one small, have been fixed. The other bug would cause the theme to reset to Luna (the theme) every time you would update to a new version of Luna.

So, there you go. Be sure to make a back-up just in case. Nothing should go wrong with updates, but you never know. Now, we move on to Luna 1.0.3 and 1.1. Luna 1.0.3 will be the first non-weekly update to Luna and will be released when we think its time for it. Meanwhile, we’re working on Bittersweet Shimmer and the update is coming along nicely with major improvements to the default themes, Notification 2.0, night mode and more brand new features, coming to you this June!