Flarum 1.8.18 Released
Another small maintenance release for the 1.x series. No security fixes this time, and nothing new to configure — just a handful of bug fixes, plus one small quality-of-life setting.
There's no urgency to upgrade unless one of the fixes below affects you, but it's a safe update with no breaking changes.
Bug fixes
- No-JS discussion pages showed the wrong posts. The server-rendered version of a discussion (what crawlers and no-JavaScript visitors see) decided which posts to print by scanning the whole API response for anything post-shaped. With Mentions enabled, posts that merely quoted a post on the page were dragged in too, so pages ended up showing posts that belong to other pages — and a numbered URL rendered a window that didn't match the page it claimed to be. It now asks the posts endpoint for exactly the page it should render. flarum/framework4852
- Losing your connection mid-request. The frontend now handles a dropped network connection gracefully instead of failing in a confusing way. flarum/framework4843
- Deprecation warning on the users list (and other searches). Loading a search with an empty query passed
null into str_getcsv(), which is deprecated on modern PHP and — on stricter setups — could surface as an error. Empty queries are now handled cleanly. flarum/framework4812
- [Mentions] Deleted-post fallback. Fixed a case where an unsynced post could incorrectly fall back to the "deleted" rendering during formatting. flarum/framework4826
New setting
- Turn off sticky pinning on All Discussions. You can now disable stickied discussions being pinned to the top of the All Discussions page, if that layout doesn't suit your community. flarum/framework4607
A note on 1.x
Flarum 2.0 is in its release-candidate phase and stable really isn't far off at all — that's where all the active work is now. The 1.x series is officially on life support: from here on it receives critical and security fixes only (no new feature or non-critical fixes will be accepted), winding down toward end of life around the end of the year. We'll post separately about the dates involved here shortly.
We've also documented this in the install guide, along with a note that 1.x is best run on PHP 8.3 and the error_reporting setting we recommend for running an older stack on modern PHP.
If you're still on 1.x, now is a good time to plan the move to 2.0 - take a look at the2.x secondary tag here on discuss to surface a wealth of 2.x related content. Extension developers: if your 2.0 update isn't out yet, that's the priority.
Versions released
flarum/core — 1.8.18flarum/sticky - 1.8.3flarum/mentions - 1.8.6
How to update
composer update
php flarum migrate
php flarum cache:clear
php flarum assets:publish
Back up your database first, and test on staging if you can.
Full changelog
Added
Fixed
