Some time ago, Flarum released its first stable version, Flarum 1.0.0 Released. I only want to describe how I felt at the time with one sentence:
After countless calls, it finally arrived
It has been a very, very long time since I first discovered Flarum in 2017. After going through so many beta releases, version 1.0 has finally, finally been released as a stable version.
You can read about my story with Flarum in my post on the iApp community, “2020, the iApp Community Starts Anew, with a Promising Future”. The following is the story of Flarum, translated from the official community:
Eleven years ago, Toby Zerner set out on a mission: to build a forum for the future. The result, esoTalk, was an excellent product and a great place to learn and experiment with ideas. A few years later, esoTalk evolved into something bigger: a revolutionary new design based on simplicity, elegance, and ease of use. This was the birth of Flarum.
Now, after 7 years and 16 beta releases, with more than 100 contributors, Flarum finds itself in an exciting period! Adoption of our software is growing rapidly, a vast extension ecosystem has emerged, and even enterprises are making the move. Although Toby has moved on to other entrepreneurial ventures, the Flarum team is larger and more active than ever, with more than a dozen people passionately working to advance the project. In 2019, the Flarum Foundation was established to protect Flarum’s future as a free and open-source product. We also moved to a stable 2–3 month release cycle, and have now successfully released our first stable version!
The team at Flarum believes it is time to challenge traditional forum design and architecture. Although the core of forums has remained unchanged for years, we see that people want more, and we are here to build it. Flarum is dedicated to engaging and strengthening community interaction in the digital world, and to developing lean, scalable software that improves the experience of administrators, moderators, extension developers, and, most importantly, users.
Flarum is more than just another forum software; it is a highly flexible framework that allows users to add every conceivable feature to their installations. From the beginning, Flarum has been built with extensibility and ease of use in mind, while being based on modern software standards to ensure that it aligns with our core principles: simple, modern, and fast.
Upgrading Flarum
It has been half a month since the release of version 1.0.0, and the stable version has already been updated to 1.0.2. Taking advantage of the Dragon Boat Festival holiday, I decided to upgrade the iApp community.
The official upgrade guide: https://docs.flarum.org/update.html
Uninstalling extensions
First, use the composer why-not flarum/core v1.0.2 command to find out which extensions are causing conflicts.
Then uninstall some incompatible extensions. I only had three; see Extiverse for details about incompatible extensions.
composer remove v17development/flarum-seo datitisev/flarum-ext-dashboard ffans/lang-simplified-chinese v17development/flarum-seo
Modifying the configuration file
Open the composer.json configuration file in the Flarum root directory and change ^0.1.0 to * for all extensions.
Change the version of flarum/core from ^0.1.0 to ^1.0.
Delete the entire "minimum-stability": "beta", line from composer.json.
Running the update
Delete the composer.lock file and run the following commands to update Composer:
composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php flarum migrate
php flarum cache:clear
That’s it—Flarum has been upgraded.
Here are some of the updates in Flarum 1.0.0:
- 🧔 Introduced a new user slug driver that uses user IDs
- 🔐 Strengthened headers against malicious behavior
- 📃 The administration area now has an extensible user list
- 👆 A new mention system that separates mentions from usernames
- 🤖 Many improvements to canonical URL generation
- ⏩ Performance improvements to many core and bundled extensions, including Tags
- 😎 Many accessibility improvements
- 🌐 Migrated translations to the ICU format, paving the way for gendered translations
- 🔃 The Pusher extension can now also handle private discussions in real time
- 📃 Asset publishing has been separated from the migrate command into
assets:publish - 🔍 Fixed searching discussion titles
- 🐛 A large number of fixes