v1.7.0 - Tasmanian Devil

Tasmanian Devil

📣 The Release

Hey folks, the moment we've been waiting for is finally here! Flarum v1.7 is now live, and it's packed with some awesome new features and enhancements. Here are some highlights:

👨‍💻 Introduced support for PHP 8.2!
🚪 New access tokens user management UI.
🔓 Added a global logout to clear all sessions, access tokens, email tokens, and password tokens.
🛠️ Fixed notifications not being sent out on post approval.
🔍 SEO improvements relating to document headers
🧪 Created a Jest configuration package for frontend tests unit and component testing.
🖌️ Improved tag text color contrast for accessibility.
🚀 Introduced frontend extenders.
🧰 Introduced PHPStan support for extensions through a new package.
🔍 Admins can now search users in the admin users list.
👥 Added display name column to admin users list.
📄 Improved page navigation in the admin users list.
🆗 Added UTF8 tag slug support.
🔒️ Security patch.
🧑‍💻 And much much more...

👨‍💻 For Developers

Extensions compatible with 1.6 should still operate on Flarum 1.7 without any changes. However, this release introduces some developer-facing changes, we recommend updating your code accordingly:

Frontend extenders (https://docs.flarum.org/extend/models/#adding-new-models-1, https://docs.flarum.org/extend/models/#extending-models, https://docs.flarum.org/extend/models/#extending-models)
You can see all JS changes that might affect your extension: https://github.com/flarum/framework/issues?q=is%3Aclosed+milestone%3A1.7+label%3Ajavascript

Additionally, this release comes with nice new features:

A PHPStan package to allow static code analysis in your extension through PHPStan (https://docs.flarum.org/extend/static-code-analysis).
A Jest configuration package to allow you to write unit and components tests for your frontend code (https://docs.flarum.org/extend/testing#frontend-tests).

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/assets directory, your composer.json and 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.6 to 1.7, 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 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.7.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
Nathan Sweet
Lincoln Russell
Bart van Bragt
Circuit Dojo
David Wheatley
Rad Web Hosting
Seaborn
Timotheus Pokorra
Pep Oliveras
Edmilerad
JrdnHnz
S4 Hosting
Alexander Skvortsov
Paulina
Jai Gupta
Guoqing
Miguel A. Lago
b0ring

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 @ornanovitch @rob006 @Darkle @OwenMelbz
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 @Prosperous @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:
@ornanovitch
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 our Proposals tag.
👩‍💻 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.