How to update from 1.8.15 to 2.0.0-rc.2? Is suggested?

peopleinside

The issue

Soon Flarum 2.X will be the standard, the stable version.
Today RC2 of Flarum 2.X has been released and I read is safe and usable for production so for my personal community.

I see maybe just the FOF Cookie extension has not yet migrated to Flarum 2.X and I dont know if will be and when but seems GitHub repo has been prepared for Flarum 2.x

I'm asking if you uggest to try to upgrade and how to do.
RC2 is not stable in the code so I think I maybe need do ome server file edits to allow the upgrade and there is a official suggested procedure?

Also there is a way I can understand how much my existing and active extension will have issue without look for compatibility one by one?

Flarum information

Flarum core: 1.8.16
PHP version: CLI: 8.5.6, Web: 8.5.6
PHP memory limit: CLI: -1, Web: 1024M
MySQL version: 10.11.14-MariaDB-0ubuntu0.24.04.1
Loaded extensions: Core, date, lexbor, openssl, pcre, zlib, filter, hash, json, uri, Zend OPcache, pcntl, random, Reflection, SPL, session, standard, sodium, libxml, mysqlnd, PDO, xml, apcu, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, imap, intl, ldap, exif, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, readline, shmop, SimpleXML, soap, sockets, sqlite3, ssh2, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, yaml, zip, redis
+-------------------------------------+---------+--------+-------+
| Flarum Extensions                   |         |        |       |
+-------------------------------------+---------+--------+-------+
| ID                                  | Version | Commit | Notes |
+-------------------------------------+---------+--------+-------+
| flarum-flags                        | v1.8.2  |        |       |
| flarum-approval                     | v1.8.2  |        |       |
| flarum-suspend                      | v1.8.6  |        |       |
| flarum-tags                         | v1.8.8  |        |       |
| flarum-sticky                       | v1.8.2  |        |       |
| flarum-lock                         | v1.8.2  |        |       |
| fof-forum-widgets-core              | 1.0.0   |        |       |
| fof-impersonate                     | 1.2.0   |        |       |
| fof-byobu                           | 1.4.7   |        |       |
| flarum-mentions                     | v1.8.5  |        |       |
| flarum-subscriptions                | v1.8.1  |        |       |
| v17development-seo                  | v2.0.9  |        |       |
| sycho-profile-cover                 | v1.3.5  |        |       |
| peopleinside-fla-powcaptcha         | 2.3     |        |       |
| peopleinside-antiflood              | 1.1.5   |        |       |
| nearata-copy-code-to-clipboard      | v2.2.1  |        |       |
| kilowhat-audit-free                 | 1.7.0   |        |       |
| katosdev-automore                   | 1.0     |        |       |
| ianm-twofactor                      | 1.2.2   |        |       |
| huseyinfiliz-diff                   | 1.0.1   |        |       |
| fof-username-request                | 1.2.5   |        |       |
| fof-user-bio                        | 1.4.3   |        |       |
| fof-terms                           | 1.5.0   |        |       |
| fof-synopsis                        | 1.0.1   |        |       |
| fof-subscribed                      | 1.1.5   |        |       |
| fof-split                           | 1.1.1   |        |       |
| fof-online-users-widget             | 1.0.0   |        |       |
| fof-nightmode                       | 1.6.0   |        |       |
| fof-moderator-notes                 | 1.3.1   |        |       |
| fof-merge-discussions               | 1.4.3   |        |       |
| fof-links                           | 1.4.0   |        |       |
| fof-linguist                        | 1.1.6   |        |       |
| fof-ignore-users                    | 1.2.1   |        |       |
| fof-forum-statistics-widget         | 1.3.2   |        |       |
| fof-formatting                      | 1.1.2   |        |       |
| fof-follow-tags                     | 1.2.9   |        |       |
| fof-drafts                          | 1.2.14  |        |       |
| fof-disposable-emails               | 1.0.0   |        |       |
| fof-default-user-preferences        | 1.2.2   |        |       |
| fof-cookie-consent                  | 1.1.3   |        |       |
| fof-anti-spam                       | 1.1.4   |        |       |
| flarum-statistics                   | v1.8.1  |        |       |
| flarum-pusher                       | v1.8.1  |        |       |
| flarum-markdown                     | v1.8.1  |        |       |
| flarum-likes                        | v1.8.1  |        |       |
| flarum-lang-italian                 | 1.19.3  |        |       |
| flarum-lang-english                 | v1.8.0  |        |       |
| flarum-emoji                        | v1.8.1  |        |       |
| flarum-bbcode                       | v1.8.0  |        |       |
| clarkwinkelmann-mass-actions        | 1.1.2   |        |       |
| clarkwinkelmann-first-post-approval | 1.0.1   |        |       |
| clarkwinkelmann-emojionearea        | 1.1.1   |        |       |
| clarkwinkelmann-circle-groups       | 1.0.1   |        |       |
| blomstra-user-filter                | 0.1.4   |        |       |
| blomstra-database-queue             | 1.1.0   |        |       |
+-------------------------------------+---------+--------+-------+
Base URL: https://community.marcoborla.it
Installation path: /home/marcoborla.it/domains/community.marcoborla.it/public_html
Queue driver: database
Session driver: file
Scheduler status: Attivo
Mail driver: smtp
Debug mode: off

Thank you 🙏🏽

KBExit

peopleinside the documentation on the flarum.org site covers all of your questions. Have you taken a look there?

GreXXL

peopleinside many of the extensions you use are already ported to v2. Certainly not all of them. Upgrading to v2 is pretty much the same as every Flarum update - you just need to have compatible extensions.

If you decide to stick with 1.8.x until all extensions are available I highly recommend you update to 1.8.16 though.

peopleinside

the documentation on the flarum.org site covers all of your questions. Have you taken a look there?

I will check better. A lot of content it's not always easy to follow for who is not expert 😊 but maybe I understand I can't upgrade to 2.x with extension that are not compatible.

In the doc I dont find a way to check not one by one every extension I have to understand what extensions will have issues on the migration. Maybe it's just me... that never found or maybe there is not a way.

Maybe also then I just have to check and edit the composer.json then run the below SSH command showed in the guide. This is what I understand.

I'm a little bit scared about this migration maybe also because some extension I use are not yet compatible.. so I read they must be removed not only deactivated.

If you decide to stick with 1.8.x until all extensions are available I highly recommend you update to 1.8.16 though.

Thank you, as in my php flarum info pasting I'm already on that version 😊

KBExit

peopleinside In the doc I dont find a way to check not one by one every extension I have to understand what extensions will have issues on the migration. Maybe it's just me... that never found or maybe there is not a way.

composer why-not flarum/core 2.0.0

peopleinside Maybe also then I just have to check and edit the composer.json then run the below SSH command showed in the guide. This is what I understand.
Update your composer.json. Set the version string of all extensions (including bundled ones like flarum/tags, flarum/mentions, flarum/likes, etc) to *. Then set flarum/core to ².0:
"flarum/core": "^2.0",
"flarum/tags": "*",
"flarum/mentions": "*",
Set minimum-stability to beta. While Flarum 2.0 is in beta, your composer.json must have:
"minimum-stability": "beta"

For further reference and clarification of all possible confusions, here is an example composer.json file for rc:

{
    "name": "flarum/flarum",
    "description": "Delightfully simple forum software.",
    "type": "project",
    "keywords": [
        "forum",
        "discussion"
    ],
    "homepage": "https://flarum.org/",
    "license": "MIT",
    "authors": [
        {
            "name": "Flarum",
            "email": "info@flarum.org",
            "homepage": "https://flarum.org/team"
        }
    ],
    "support": {
        "issues": "https://github.com/flarum/core/issues",
        "source": "https://github.com/flarum/flarum",
        "docs": "https://docs.flarum.org/"
    },
    "require": {
        "datlechin/flarum-passkey": "*",
        "ernestdefoe/favorite-team": "*",
        "ernestdefoe/flarum-facebook-post": "*",
        "ernestdefoe/gridiron-nation": "*",
        "ernestdefoe/group-messages": "*",
        "ernestdefoe/og-image": "*",
        "ernestdefoe/picks": "*",
        "ernestdefoe/recruiting": "*",
        "ernestdefoe/social-groups": "*",
        "ernestdefoe/theme-toggle": "*",
        "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/messages": "*",
        "flarum/nicknames": "*",
        "flarum/realtime": "*",
        "flarum/statistics": "*",
        "flarum/sticky": "*",
        "flarum/subscriptions": "*",
        "flarum/suspend": "*",
        "flarum/tags": "*",
        "fof/anti-spam": "*",
        "fof/badges": "*",
        "fof/drafts": "*",
        "fof/formatting": "*",
        "fof/horizon": "*",
        "fof/linguist": "*",
        "fof/move-posts": "*",
        "fof/pages": "*",
        "fof/polls": "*",
        "fof/reactions": "*",
        "fof/redis": "*",
        "fof/rich-text": "*",
        "fof/share-social": "^2.0@beta",
        "fof/sitemap": "*",
        "fof/split": "*",
        "fof/terms": "*",
        "fof/upload": "*",
        "fof/user-bio": "*",
        "fof/user-directory": "*",
        "forumaker/profile-cover": "*",
        "huseyinfiliz/stickiest": "2.0.0-beta.2",
        "ianm/follow-users": "*",
        "ianm/log-viewer": "*",
        "ianm/syndication": "*",
        "illuminate/queue": "<13.10",
        "league/flysystem-aws-s3-v3": "*",
        "pianotell/flarum-ext-flamoji": "*",
        "ralkage/flarum-ext-word-counter": "*",
        "ramon/classifieds": "*",
        "resofire/pwa": "*"
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true
    },
    "repositories": {
        "flarum": {
            "type": "composer",
            "url": "https://floxum.com/composer"
        }
    },
    "minimum-stability": "beta",
    "prefer-stable": true
}

After you complete those changes:

composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php flarum migrate
php flarum cache:clear

Post edited with corrections*

peopleinside

Thank you.
I will see, I'm looking also right now.
Little bit scared but I know backup always so if something get wrong I can have a small downtime but resolve.
Thank you again.

KBExit

peopleinside if you do run into any issues, I do my best to check in and apply aid where needed.

peopleinside

Oh this is kind thank you.
For now, I'll consider which extensions I should opt out of and what that entails. Thank you very much!

peopleinside

Currently I get this:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires blomstra/database-queue * -> satisfiable by blomstra/database-queue[0.1-beta.1, 0.1-beta.2, 1.0.0, 1.0.1, 1.0.2, 1.1.0].
    - blomstra/database-queue[0.1-beta.1, ..., 0.1-beta.2, 1.0.0, ..., 1.1.0] require flarum/core ^1.0.0 -> found flarum/core[v1.0.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
  Problem 2
    - Root composer.json requires blomstra/user-filter * -> satisfiable by blomstra/user-filter[0.1.0, ..., 0.1.4].
    - blomstra/user-filter[0.1.0, ..., 0.1.4] require flarum/core ^1.2.0 -> found flarum/core[v1.2.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
  Problem 3
    - Root composer.json requires clarkwinkelmann/flarum-ext-mass-actions * -> satisfiable by clarkwinkelmann/flarum-ext-mass-actions[1.0.0, 1.1.0, 1.1.1, 1.1.2].
    - clarkwinkelmann/flarum-ext-mass-actions[1.0.0, ..., 1.1.2] require flarum/core ^1.2 -> found flarum/core[v1.2.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
  Problem 4
    - Root composer.json requires justoverclock/last-post-useravatar * -> satisfiable by justoverclock/last-post-useravatar[0.1.0, ..., 0.1.8].
    - justoverclock/last-post-useravatar[0.1.0, ..., 0.1.8] require flarum/core ^1.0.0 -> found flarum/core[v1.0.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
  Problem 5
    - clarkwinkelmann/flarum-ext-circle-groups[0.1.0-beta.1, ..., 0.1.0-beta.2] require flarum/core ^0.1.0-beta.6 -> found flarum/core[v0.1.0-beta.6, ..., v0.1.0-beta.16] but it conflicts with your root composer.json require (^2.0).
    - clarkwinkelmann/flarum-ext-circle-groups[0.2.0, ..., 0.2.1] require flarum/core ^0.1.0-beta.8 -> found flarum/core[v0.1.0-beta.8, ..., v0.1.0-beta.16] but it conflicts with your root composer.json require (^2.0).
    - clarkwinkelmann/flarum-ext-circle-groups[0.2.2, ..., 0.2.4] require flarum/core ^0.1.0-beta.14 -> found flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but it conflicts with your root composer.json require (^2.0).
    - clarkwinkelmann/flarum-ext-circle-groups 1.0.0 requires flarum/core ^1.0 -> found flarum/core[v1.0.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
    - clarkwinkelmann/flarum-ext-circle-groups 1.0.1 requires flarum/core ^1.2 -> found flarum/core[v1.2.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
    - Root composer.json requires clarkwinkelmann/flarum-ext-circle-groups * -> satisfiable by clarkwinkelmann/flarum-ext-circle-groups[0.1.0-beta.1, ..., 0.2.4, 1.0.0, 1.0.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

I see some incompatible extension. I'm helped by the AI and I'm trying to do the necessary steps.
I'm working on it

KBExit

peopleinside ~~you need to replace this blomstra/database-queue with one that's not abandoned. This is in the Flarum docs as well...~~ correction, just remove it, it's part of code for database queue.

Remove blomstra/database-queue and blomstra/fontawesome — this functionality is now built into flarum/core.

clarkwinkelmann/flarum-ext-circle-groups this is just a cosmetic extension, you can disable it and Clark will update it when he's ready.

justoverclock/last-post-useravatar I have no idea if he's going to update his extensions.

peopleinside

Updated successfully with a lot of issues.
One of the community is now UP but with a lot of issues this means a lot of essentials extensions that I use are not working or not compatible.

The SEO extension is not compatible so no SEO and issues also with external links that without this extension never opens on a new tab.
I'm unable to install and made work the Captcha. I have made two extensions that I discover they are not working on 2.x so I well need look and fix for the future but even I'm unable to use a third part extension to use the Cloudflare captcha.

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - blomstra/turnstile 0.1.0 requires flarum/core ^1.2.0 -> found flarum/core[v1.2.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
    - blomstra/turnstile[0.1.1, ..., 0.1.2] require flarum/core ^1.6.0 -> found flarum/core[v1.6.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
    - blomstra/turnstile[0.1.3, ..., 0.1.6] require flarum/core ^1.8.0 -> found flarum/core[v1.8.0, ..., v1.8.16] but it conflicts with your root composer.json require (^2.0).
    - Root composer.json requires blomstra/turnstile * -> satisfiable by blomstra/turnstile[0.1.0, ..., 0.1.6].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require blomstra/turnstile:*" to figure out if any version is installable, or "composer require blomstra/turnstile:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I tried composer require flectar/flarum-turnstile --with-all-dependencies and this get installed but once active give a Flarum fatal error so removed them.

I will have to see a lot of work and a lot of extensions removed to be able to upgrade to the 2.0 but a lot of function are not active.

😊

Also first post approval is not compatible so I miss some protection functions.
For now I disabled user new registration, as soon I can fix issues I will re-open user registration.

KBExit

peopleinside I wouldn't necessarily say that an extension not being updated is an issue with updating. You decided to update to the 2.0 branch after we discussed extension incompatibility. You took the plunge.

peopleinside I tried composer require flectar/flarum-turnstile --with-all-dependencies and this get installed but once active give a Flarum fatal error so removed them.

I have had no issues with this extension. It would be beneficial to supply the actual logs instead of accepting the surface level issue and quitting.

peopleinside Also first post approval is not compatible so I miss some protection functions.
For now I disabled user new registration, as soon I can fix issues I will re-open user registration.

The Flarum core extension approval works just fine for this, I wouldn't suggest disabling registrations just because of this.

peopleinside

No problem is just a feedback mine that update still can be problematic.
I will see taking my time. No need more support here for now jut saying about some issues that update still have.

I was think to have just one incompatible extension but they are much more.

The Flarum core extension approval works just fine for this, I wouldn't suggest disabling registrations just because of this.

I disabled registration until I'm not able to insert a Captcha on the login page.
My Captcha plugin is not compatible I will look into this issue to get compatible but even the Cloudflare Captcha plugin that I see active here on Discuss I'm not able to install and use.

I will look at the logs or issues later.
Thank you!

KBExit

peopleinside yeah, again, I haven't had any issues with that extension at all. Please supply the necessary logs for us to troubleshoot this through. It can be a number of things and we cannot troubleshoot blindly.

Worth noting, I looked back at your Flarum info, have you completed this step in the upgrade process as well? You use MariaDB.

Update your config.php if using MariaDB. Flarum 2.0 distinguishes between MySQL and MariaDB. If you're using MariaDB, update the driver value in config.php:

<?php return array (
  'debug' => true,
  'offline' => false,
  'database' =>
  array (
    'driver' => 'mysql',
    'driver' => 'mariadb',
    'host' => 'localhost',
    'port' => 3306,

peopleinside

For now I have to disable the flarum-subscriptions (php flarum extension:disable flarum-subscriptions) because my control panel use a version bellow MariaDB 11 so this cause issues and deny me to made post.

This is just one issue with the new Flarum 2.0.
This is a useful info as I can ask to the control panel about future database update procedure and report incompatibility with the new Flarum.

I will continue to investigate other issues.

peopleinside

The Maria DB version (MariaDB 10.11) that I'm using is from Ubuntu and is a long term version. Seems will be supported until February 2028.

Try to update this can broke all my domains, websites and many database just because Flarum 2.0 on his subscription core doesn't support this version of MariaDB. This seems an issue and I can't upgrade with the risk to have all broken.

So I should keep Flarum 2.0 without subscription function and also I have to resolve a lot of issues with extensions that not work anymore or I should decide to return to 1.8.

Seems in both decision I'm not very happy: stay with the old version that really need to be upgraded to have more modern components and to be better supported or stay on the new with a lot of functions missed: no captcha for now until I'm not able to resolve, no SEO, no links in new tab, no mass actions support.

ernestdefoe

peopleinside have you thought about setting up a temp staging area and testing updating to the newer version of Mariah to see if it would break your other sites?

peopleinside

I'm not an expert server and web code developer.
I use Virtualmin panel with Ubuntu.
I have a lot of production websites and email addresses.

I can risk to broke everything.
For now I will keep subscription disable. I hope a patch in the future will add compatibility with the still supported Maria DB version that are used on Ubuntu.

Currently I returned to Flarum 1.8
Too much issues. Now I will be scared about the future.
What I will do when Flarum 2.0 will be the latest and the supported version?

Core Subscription component cannot be used on my server because incompatible with the supported and provided Mysql 10.11.14-MariaDB Ubuntu 24

This cause the impossibility to create any content so the component must be deactivated.

Pusher is not working. I tried to install manually with composer require flarum/realtime but once this is active is not working.

(index):21 [Deprecation] XSLTProcessor and XSLT Processing Instructions have been deprecated by all browsers. These features will be removed from this browser soon. See https://chromestatus.com/feature/4709671889534976.
(anonymous) @ (index):21
/api/discussions:1  Failed to load resource: the server responded with a status of 500 ()

So it causing issue when post a content and even is not alerting when a new content is published.
So I'm not able to see also this working.

I need find a way to made external links opening in a new window / tab a the SEO plugin is not compatible with Flarum 2.0 and I dont see any other solution. Need maybe create from zero an extension.

I need maybe install Flarum 2.0 as test and try to resolve all this issues but without help I dont know if will be possibile.
Need to fix Subreption extension, fix the link behavior and fix also the pusher behavior.

KBExit

peopleinside Pusher is not working. I tried to install manually with composer require flarum/realtime but once this is active is not working.

~~I haven't had the chance to read your entire message,~~ but that is NOT Pusher. Pusher is already included in the core package. Also note, Pusher is a third party websocket.

peopleinside I hope a patch in the future will add compatibility with the still supported Maria DB version that are used on Ubuntu.
The minimum requirement for MariaDB for Flarum 2.x is MariaDB 10.3+ and you can upgrade the version in Ubuntu manually.

Additionally, Flarum is moving towards Database agnostic - meaning multiple DB structures are supported. This includes Postgres, SQLite, MariaDB, and MySQL. And the dev has to be future conscious. Your issue can be resolved manually. MariaDB is backwards compatible. My hosting stack uses MariaDB without issue, you just have to meet the minimum requirement.

peopleinside

A bug has been reported that affect Flarum 2.0 rc2 and Subscription but also any other extensions that can use notification in a server with MariaDB inferior to the version 11.

Thank you for the help on this topic.
I'm still working on a migration detecting issues and trying to resolve where possibile.