Flarum 2.0.0-beta.8 released - 2.0 is now feature complete

Wlork

I can't install the update....

Terminal tells me 'Nothing to modify in the lock file'

IanM

Wlork what are your composer constraints and minimum stability set to? Maybe you already pulled in the 2.x-dev versions (currently identical to the tagged beta.8)

Wlork

IanM what are your composer constraints and minimum stability set to? Maybe you already pulled in the 2.x-dev versions (currently identical to the tagged beta.8)

"require": {
        "acpl/mobile-tab": "*",
        "datlechin/flarum-copy-links": "*",
        "datlechin/flarum-link-preview": "*",
        "flarum/approval": "*",
        "flarum/bbcode": "*",
        "flarum/core": "^2.0",
        "flarum/emoji": "*",
        "flarum/extension-manager": "*",
        "flarum/flags": "*",
        "flarum/lang-english": "*",
        "flarum/likes": "*",
        "flarum/lock": "*",
        "flarum/markdown": "*",
        "flarum/mentions": "*",
        "flarum/nicknames": "*",
        "flarum/pusher": "*",
        "flarum/statistics": "*",
        "flarum/sticky": "*",
        "flarum/subscriptions": "*",
        "flarum/suspend": "*",
        "flarum/tags": "*",
        "flectar/flarum-turnstile": "*",
        "fof/default-group": "*",
        "fof/discussion-templates": "*",
        "fof/discussion-thumbnail": "*",
        "fof/discussion-views": "*",
        "fof/follow-tags": "*",
        "fof/formatting": "*",
        "fof/ignore-users": "*",
        "fof/linguist": "*",
        "fof/links": "*",
        "fof/move-posts": "*",
        "fof/pages": "*",
        "fof/reactions": "*",
        "fof/rich-text": "*",
        "fof/terms": "*",
        "fof/upload": "*",
        "fof/user-bio": "*",
        "huseyinfiliz/modern-footer": "*"
    },

    "config": {
        "preferred-install": "dist",
        "sort-packages": true
    },

    "minimum-stability": "beta",
    "repositories": [],
    "prefer-stable": true
}

IanM

Wlork seems fine..

composer update -W
php flarum migrate
php flarum cache:clear
php flarum assets:publish

Should be all you need here..

serdo

When will the stable version 2 be released?

IanM

serdo Hard to say, probably somewhere between June and August

Wlork

IanM Should be all you need here..

Unfortunately, no 😕 Even with “-W”, I still get the same message

IanM

Wlork Can you please show the output from php flarum info

Wlork

IanM Can you please show the output from php flarum info

Flarum core: 2.0.0-beta.7
PHP version: CLI: 8.2.30, Web: 8.2.30
PHP memory limit: CLI: 1024M, Web: unable to detect
MySQL version: 11.4.10-MariaDB
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bz2, calendar, ctype, curl, hash, filter, ftp, gettext, json, iconv, SPL, pcntl, random, readline, Reflection, session, standard, mbstring, shmop, SimpleXML, tokenizer, xml, litespeed, bcmath, dom, fileinfo, gd, igbinary, imagick, imap, intl, ldap, exif, mcrypt, memcached, msgpack, PDO, mysqlnd, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, redis, soap, sockets, sodium, sysvmsg, sysvsem, sysvshm, tidy, xmlreader, xmlwriter, xsl, zip, Zend OPcache, SourceGuardian
+--------------------------+---------------+--------+-------+
| Flarum Extensions        |               |        |       |
+--------------------------+---------------+--------+-------+
| ID                       | Version       | Commit | Notes |
+--------------------------+---------------+--------+-------+
| flarum-flags             | v2.0.0-beta.7 |        |       |
| flarum-tags              | v2.0.0-beta.7 |        |       |
| flarum-approval          | v2.0.0-beta.7 |        |       |
| flarum-suspend           | v2.0.0-beta.7 |        |       |
| flarum-markdown          | v2.0.0-beta.7 |        |       |
| flarum-lock              | v2.0.0-beta.7 |        |       |
| flarum-mentions          | v2.0.0-beta.7 |        |       |
| flarum-subscriptions     | v2.0.0-beta.7 |        |       |
| fof-user-bio             | 2.0.0-beta.3  |        |       |
| fof-upload               | 2.0.0-beta.3  |        |       |
| fof-terms                | 2.0.0-beta.5  |        |       |
| fof-rich-text            | 2.0.0-beta.3  |        |       |
| fof-reactions            | 2.0.0-beta.4  |        |       |
| fof-pages                | 2.0.0-beta.2  |        |       |
| fof-move-posts           | v2.0.0-beta.4 |        |       |
| fof-links                | 2.0.0-beta.2  |        |       |
| fof-linguist             | 2.0.0-beta.1  |        |       |
| fof-ignore-users         | 2.0.0-beta.3  |        |       |
| fof-formatting           | 2.0.0-beta.2  |        |       |
| fof-follow-tags          | 2.0.0-beta.6  |        |       |
| fof-discussion-views     | 2.0.0-beta.1  |        |       |
| fof-discussion-thumbnail | 2.0.0-beta.1  |        |       |
| fof-discussion-templates | 2.0.0-beta.1  |        |       |
| fof-default-group        | 2.0.0-beta.1  |        |       |
| flarum-sticky            | v2.0.0-beta.7 |        |       |
| flarum-statistics        | v2.0.0-beta.7 |        |       |
| flarum-lang-english      | v2.0.0-beta.7 |        |       |
| flarum-extension-manager | v2.0.0-beta.7 |        |       |
| flarum-emoji             | v2.0.0-beta.7 |        |       |
| flarum-bbcode            | v2.0.0-beta.7 |        |       |
| datlechin-link-preview   | v2.0.0-beta.2 |        |       |
| datlechin-copy-links     | v2.0.0-beta.1 |        |       |
| acpl-mobile-tab          | 2.0.0-beta.10 |        |       |
+--------------------------+---------------+--------+-------+

Queue driver: sync
Session driver: file
Mail driver: mail
Debug mode: off

IanM

Wlork there it is....

PHP version: CLI: 8.2.30, Web: 8.2.30

Laravel 13 requires PHP 8.3 minimum, so composer will not see beta 8 as an option for you...

Wlork

IanM Laravel 13 requires PHP 8.3 minimum, so composer will not see beta 8 as an option for you...

Thank you very much, it work 🙂

IanM

Wlork I've updated the release announcement to reflect the PHP requirements 👍️

Forogramero

IanM Is it safe to upgrade to Flarum 2.0??

IanM

Forogramero officially the stance is no, not yet as this is still a beta release. BUT...

The 2.0 API is now frozen and will not change ahead of the 2.0 release this summer. We are already running Flarum 2 right here, and it has been working without any major issues. If all of the extensions that you use are already updated, then the risk is minimized, in my personal opinion.

My suggestion for you would be to start testing Flarum 2 with your configuration and extension set either locally or on a staging server, and see how you get on with it. The more extensions you have, the greater chance of something not quite working right.

Next month we will release "Flarum 2.0 Release Candidate 1" - this is the point where we will change the official advice and say that it is safe to use in production so long as your chosen extensions are available and tested.

IanM

Wlork I did just noticed another thing with your output here:

You seem to be using the mysql driver in your config.php, but have a mariadb instance. Flarum 2.0 distinguishes between the two (there are slight differences internally), so to get the best performance, and avoid any "weirdness", I would strongly suggest updating your config

Wlork

I'm not a fan of the main button (new discussion, reply, etc) text being black in light mode. It's fine in light mode HC because it's HC, but not in light mode. For me, it was better before. Other than that, I really like the new features that have been added

🙂

Now for the FoF extensions... They need to be fixed or made compatible, depending on the case 🙂

IanM I did just noticed another thing with your output here:

You seem to be using the mysql driver in your config.php, but have a mariadb instance. Flarum 2.0 distinguishes between the two (there are slight differences internally), so to get the best performance, and avoid any "weirdness", I would strongly suggest updating your config

Just to make sure I understand correctly, I need to change this line?

'driver' => 'mysql', // the database driver, i.e. MySQL, MariaDB, PostgreSQL, SQLite

Replace "mysql" with "MariaDB", is that right ? 🙂

IanM

Wlork Replace "mysql" with "MariaDB", is that right ?

Yes, in lower case, so mariadb for you...

I'll get the documentation updated to make it clear of what Flarum expects here 🙂

Mayhem

Thank you for all the hard work you’ve put into Flarum!

I had a question regarding the IdWithDisplayNameSlugDriver. Was there a particular reason the URL structure was implemented as:

/<id>-<display-name>

instead of:

/<display-name>-<id>?

From an SEO perspective, placing keywords as early as possible in the URL is generally considered best practice. Modern SEO guidance tends to favor keyword-first slugs because search engines place slightly more contextual weight on earlier path segments, and they also improve readability and click-through rates for users.

This difference is minimal when IDs are small, but it becomes more noticeable as IDs grow larger. For example:

https://example.com/my-seo-title-13121

is typically more descriptive and user-friendly than:

https://example.com/13121-my-seo-title

In the second case, the numeric prefix pushes meaningful keywords further back in the URL, which may slightly reduce clarity for both users and search engines.

I’m curious whether the current ordering was chosen for technical consistency, routing simplicity, backward compatibility, or another architectural reason. If there isn’t a strong constraint, would the project be open to considering a keyword-first format (while still retaining the ID for uniqueness and stability)?

I appreciate any insight you can share on the reasoning behind this.

dragsugur

when can we except ugprade guide from 1.8 to 2.0 i want to start using this 😅 so i can start modifying my own custom stuff

davetodave178

Mayhem There wasn't so much thought going into about the URL structure for the new user slug driver except that it follows the same pattern like for discussions slugs.

So yes as you said it was chosen for the reasons you listed (technical consistency, routing simplicity). I had a look at Google's Documentation for this and it does not address ID position. Some unofficial sources like Stackoverflow tend to favor having the ID at the beginning and I also tend to side with that.

For communities requiring the ID's to be switched around with the slug, I recommend creating custom slug drivers for this in third party extensions