v1.8.0 - Quoll
The Release
We are delighted to announce the release of the final scheduled installment in the 1.x series, marking the culmination of an extensive period of development and refinement. This release is primarily dedicated to addressing various bugs and bolstering performance, ensuring a smoother and more reliable experience for our users. As we bid farewell to the 1.x series, we would like to express our gratitude to our loyal users for their invaluable support and collaboration. Now, let's delve into the key highlights of this release:
You can now mention tags in posts (flarum/framework3769).
Users can be given permission to delete their own posts (flarum/framework3784).
New users can be created from the user admin page (flarum/framework3744).
Extensions can be enabled/disabled from a CLI command (flarum/framework3816).
Improved post creation time (flarum/framework3808).
And a whole lot of performance improvements and bugs fixed
This release closes the successfully funded bounty for mentioning tags, as well as a high-voted proposal for the new permission added in this release. We want to highlight this to make you consider posting your idea in depth inProposals so it maybe gets picked up either as aBounty or as a high-voted proposal - you can see this here: https://discuss.flarum.org/t/proposals?sort=votes
For Developers
Extensions compatible with 1.7 should still operate on Flarum 1.8 without any changes. However, depending on what JavaScript changes your extension makes and how it makes them, we recommend looking through some of the frontend facing changes made: https://github.com/flarum/framework/issues?q=is%3Aopen+is%3Aissue+label%3Ajavascript.
Additionally, this release introduces conditional extenders, which allow you to add extenders based on a condition, such as whether an extension is enabled: flarum/framework3759.
Checkout the full upgrade guide. Feel free to provide feedback or report any encountered issues!
Upgrading
Before you upgrade, make sure to create a backup of your
public/assetsdirectory, yourcomposer.jsonand your database!
Before starting the upgrade process, ensure you are on Flarum 1.0.0 or above in your Admin Dashboard or by typing php flarum info. If you're not, use the previous release announcement for upgrading from an earlier version.
To upgrade from 1.0 or 1.7 to 1.8, take a look at our upgrade guide documentation. The process should be much easier compared to previous major version upgrades, due to the lack of breaking changes.
If you run into any issues, please open a new discussion under the tagUpgrading. 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.8.0, and any errors to their fullest.
Thanks to our Sponsors
Financial donations keep Flarum alive and kicking. The following companies and people deserve credit for making Flarum sustainable:
- Glowing Blue AG.
- Sridhar Kamma.
- Lincoln Russell.
- Bart van Bragt.
- Circuit Dojo.
- David Wheatley.
- Rad Web Hosting.
- Seaborn.
- Timotheus Pokorra.
- JrdnHnz.
- Jai Gupta.
- Guoqing Zou.
- Miguel A. Lago.
- Alexander Skvortsov.
- Jeannes Bryan.
Thank you to all the Supporters, backing us through Discuss:
@v17development and @waca !
Thanks for being awesome 
!
Acknowledgements
Flarum wouldn't be the same without our over one hundred contributors, along with their generous time commitments! For this release we specifically thank these wonderful people:
- The non-team contributors that usually tackle unplanned, but extremely welcomed bugs or overhauls. We absolutely love contributions that help us move forward, so thank you very much:
@n-peugnet @rob006 @datlechin @iPurpl3x @rafaucau @exside. - The core and staff team contributors, people that have vast knowledge of the code base who sacrifice their free time to bring the awesome Flarum software to you, for free. Thank you so much:
@askvortsov @SychO @davwheat @luceos @IanM @clarkwinkelmann @OrdinaryJellyfish - The community staff is the foundation to a warm and welcoming community. Many cheers for all you do:
@jordanjay29 @GreXXL - The well-oiled machine that is the translation team, keeping up with new languages, their maintainers and the translations perfectly well. Very, very much appreciated:
@GreXXL @Justoverclock @rob006 - All our additional staff who all help us where we need it most:
@tankerkiller125 @datitisev @Deebug @katos @victorparedes. - A great shout out to everyone who's submitted carefully described issues and suggestions, especially:
@iPurpl3x, UserZHTW, flawedworld, tarjeiba, @Eldenroot, @Nearata, @n-peugnet, fakerybakery, @matteocontrini, @jslirola, @Darkle, rebelC0der. - And the whole community sharing their passion for Flarum, urging us on!
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 becoming a Supporter or Sponsor on Discuss, backing us on Open Collective or on GitHub.
By supporting new features with your pledge in ourProposals.
By contributing to the source code, hop onto any of our open issues.
By creating your own Flarum extensions and sharing them with the world!
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!
For installation instructions check our installation documentation. If you are interested in developing extensions for Flarum, check the extend section there.
️
