v1.0.0 - Kangaroo
- 🧔 A new user slug driver was introduced which uses the user Id.
- 🔐 Hardened headers against actors with bad intent.
- 📃 The admin area now has an extensible users list.
- 👆 New mentions system, detaching itself from usernames.
- 🤖 Many improvements to canonical URL generation.
- ⏩ Many improvements to performance in core and bundled extensions, including tags.
- 😎 Many improvements to accessibility.
- 🌐 Moved to the ICU format for translations, which paves the way for genderization in translations among others.
- 🔃 The pusher extension now also makes non public discussion realtime.
- 📃 Asset publishing separated from the
migrate command into
- 🔍 Fixed searching discussion titles.
- 🐛 Tons of fixes.
by Austin Elder from Unsplash
Eleven years ago, Toby Zerner set out with a mission: to build a forum for the future. The result, esoTalk, was a good product, and an excellent playground for learning and trying ideas. After a few years, esoTalk evolved into something bigger: a revolutionary new design, based around simplicity, elegance, and ease of use. This was the birth of Flarum.
Now, seven years and sixteen beta releases later by over hundred contributors, Flarum finds itself in an exciting period! Adoption of our software has skyrocketed, a substantial extension ecosystem has emerged, and even enterprises are migrating over. Although Toby has moved on to other entrepreneurial projects, the Flarum team is larger and more active than ever, with over a dozen people working passionately to advance the project. In 2019, the Flarum Foundation was brought into existence to safeguard the future of Flarum as a free and open-source product. We’ve also converted to a steady 2-3 month release cycle, and with that we managed to release the first stable version!
Our team at Flarum believes that the time has come to challenge the traditional forum design and architecture. While forums at their core have remained very much the same over the years, we see that people want something more, and we're here to build it. Flarum has been created specifically to engage and enhance community interactions in a digital world and to develop lean, extensible software that improves the experience of the admin, moderator, extension developer, and most importantly, the user.
Flarum is not just another forum software, it is much more an incredibly flexible framework that allows its users to add every feature imaginable to their installations. To this point, Flarum has been explicitly built with extensibility and ease of use in mind, while building upon modern software standards to ensure that this remains within our core ethos: Simple, Modern, and Fast.
📣 The Release
To us, beta never meant that Flarum would break while using it. It meant that extensions might no longer work when upgrading. Only twice have we seen a release that completely made almost all extensions incompatible, those being beta 8 and 14.
With stable out, we will do our best to postpone changes that break extensions to the next major release (v2.0.0) which we currently plan to release in about a year. The stable release as such will mark a time for 🌱 growth and 📈 stability.
That alone is a huge gain of this release, but let's not stray from everything else that has been done; because 78 issues were taken care of! We listed the most noticeable changes at the top, if you want to dive into all the changes please visit the changelog files on our repositories.
👨💻 For Developers
Ahead of the release we announced major changes in a dedicated discussion, this seems to have had a very positive effect on the number of compatible extensions. We recommend (extension) developers towards the upgrade guide for a complete list of changes.
Before you run the upgrade, make sure to create a backup of your
public/assets directory, your
composer.json and your database!
Before starting the upgrade process, ensure you are on 0.1.0-beta.16 in your Admin Dashboard or by typing
php flarum info, use the previous release notes for upgrading from an earlier version.
To upgrade from 0.1.0-beta.16 to stable, take a look at our stable upgrade guide documentation.
If you run into any issues, please open a new discussion under the Support tag. Ignore similar discussions, and open a new one anyhow. Make sure to mention the output of
php flarum info,
composer why-not flarum/core v1.0.0 and any errors in their fullest.
Reaching stable wouldn't have been possible without the sacrifice made by over hundred contributors! For this release we specifically thank these wonderful people:
To every Open Collective supporter and Github Sponsor, but especially:
And finally, to you for your ongoing support and enthusiasm that keeps us all going!
🆘 Support the Project
We need your support to:
- Guarantee continued development on the software.
- Create a valuable ecosystem around the project.
- Ensure healthy extensions are available.
You can support us:
- 👕 By getting some swag from our merchandise store!
- 💵 By backing us on Open Collective or on GitHub.
- 👩💻 By contributing to the source code, hop onto any of our open issues.
- 🌎 By translating Flarum and extensions into your own language.
- 💝 By sharing your love for Flarum with friends, family and on the internet.
- 💬 By hanging out with us, here on discuss!
🔮 What now?
The coming weeks we'll allow our team to relax as everyone has been pressing hard for this release for months on end! For this reason we have sent all our team members some well deserved swag in celebration of stable and as a thank you for their contributions to the project.
Our next release will be a minor patch version addressing any bugs we missed in 1.0. In the meantime, we'll be doing a lot of internal discussion and planning to put together roadmaps and strategy moving towards v2.