Hello my magnificent Flarumites!
With our last release, beta 14, having been delayed quite extensively, we knew it was important to get back into our habit of regular release cycles. Well within our estimation we today are proud to ship to you Flarum 0.1.0-beta.15!
“Don’t dream of winning, train for it!” — Mo Farah
Australian Tiger Beetle
🔔 What’s Changed?
The focus of this release was extenders for extension developers and some better internationalization support. A few user-visible highlights:
Aside from a ton of fixes, there are many other improvements and new small features in most of our bundled extensions. Let us know if you discovered one or discover them by looking through the extensions changelog.md or releases page on GitHub.
👨💻 For Developers
If you are a developer please understand there are many breaking changes in this release, make sure to read the full upgrade guide in our docs! Some key points:
- MomentJS BC layer has been removed
- Policy system has been reworked
- Composer options have been added for new Admin UI
Flarum\User\Event\GetDisplayName event has been removed, use the display name driver feature of the
User extender instead
storage_path global helpers have been removed
- Other changes are mentioned in the upgrade guide for this release.
Developers are urged to check the changelogs of relating packages when they discover issues. You can review the Beta 15 Upgrade Guide to ensure your extensions are up to date.
If you have any questions or run into any obstacles in upgrading, please open a new discussion in the Dev tag or find us in #extend on our Discord.
Before you run the upgrade, make sure to create a backup of your
public/assets directory, your
composer.json and your database!
Step 1: Ensure you are on version 0.1.0-beta.14 in your Admin Dashboard or by running
php flarum info (use the previous release notes for upgrading from an earlier version)
Step 2: Uninstall every 3rd party extension that isn't compatible with beta 15 yet. You can check which extensions are compatible at Extiverse (it needs up to one hour after release to display compatible extensions) or use the extiverse helper.
Step 3: Disable the remaining extensions. Re-enabling them one at a time after you update will make it easier to debug if any issues occur.
Step 4: Run the following commands:
Now run the update all versions without installing (yet):
composer update --no-install --with-all-dependencies
[optional] If you'd like to add nicknames support:
composer require --no-update flarum/nicknames
Now install everything you've updated:
composer install --prefer-dist --no-dev -a
Last step is to run the database changes and clear the cache:
php flarum migrate
php flarum cache:clear
Step 5: Use your newly-upgraded Flarum site!
If you run into any problems, please open a new discussion in the Support tag. There may be discussions of similar issues, but open a new one anyway, it helps us get your specific problem resolved faster.
If the problem persists – we're here to help! Make sure to include the output of
php flarum info. Please also include the output of
composer why-not flarum/core v0.1.0-beta.15.
Flarum releases wouldn't be possible without a multitude of people, our thanks go out to all of them! Thank you...
To everyone who contributed code this release, especially @SychO, @ianm, nina-py, sl-kr, azibom, lhsazevedo, @w-4, @rob006, @franga2000, @Swader, @Littlegolden, qiaeru.
To our eagle-eyed bug reporters, especially @franga2000, @matteocontrini, @yulei745, @Rami-Sedhom, idk-pixel, lhsazevedo, @w-4.
To the incredible team behind Flarum, including @Franz, @luceos, @jordanjay29, @datitisev, @clarkwinkelmann, @tankerkiller125, @askvortsov, @SychO, @Liberty, @Digital, @Pollux, @katos, @Kyrne, @FrederikR, @Wadera and @Ralkage;
To every Open Collective supporter and Github Sponsor, but especially Glowing Blue AG, ecomscan, Bitfalls, KAV partners, @BartVB, Sridhar Kamma, Project Alice and Forum WirsanSoizburg.
Your continued support is extremely helpful, being fundamental to stable development for Flarum! Help us become a sustainable project by backing us on Open Collective or on GitHub
And finally, to you for your ongoing support and enthusiasm that keeps us all going!