Apricot I’m sure there’s a reason for it and maybe it’s to keep people from installing not even an alpha version of the software and coming here complaining that it’s not working right or it’s buggy or they can’t install extensions. Again I’m sure there’s a reason why they don’t.

    GreXXL Hmm, it seems that the last time I checked, I somehow missed the 2.0 branch. Now I see it.
    Maybe it’s because it’s cluttered with a lot of different branches, and 2.0 wasn’t the default at that time, so I just missed it in among a pile of stale branches

      qianmoQ ® When it’s ready. They haven’t given a time frame yet and last I checked the demo was broken.

        I think they mentioned the optimistic release date will be in 2025. Pessimistic is… when ready 😉

        5 days later

        Hey everyone 👋

        Some of you might have noticed that discuss misbehaved for those that weren't logged in.

        Last night we published an update to test our upcoming 1.8.6 release, which contains mostly QoL changes for developers. We didn't notice the issue right away, but once reports came in we tried to resolve the issue first and foremost. Currently we have reverted back to 1.8.5 instead.

        My apologies for any inconvenience.

        We've redeployed the upcoming 1.8.6 version onto discuss. This version will be announced later. Should you notice any issues, please do report that to us 👍️

        5 days later

        ⭐️ New 1.x core and bundled extensions release ⭐️

        Today we released some minor updates and fixes for our 1.x branch. The vast majority of the changes are to aid developers to customize our software easier than ever, and of course we have a sprinkling of fixes for you too!

        Fixes
        Changes
        Added

        Versions

        Today's release bumps the versions of core and most bundled extensions, see below:

        • flarum/core - v1.8.7
        • flarum/akismet - v1.8.1
        • flarum/approval - v1.8.2
        • flarum/emoji - v1.8.1
        • flarum/extension-manager - v1.0.4
        • flarum/flags - v1.8.1
        • flarum/likes - v1.8.1
        • flarum/lock - v1.8.1
        • flarum/markdown - v1.8.1
        • flarum/mentions - v1.8.4
        • flarum/nicknames - v1.8.1
        • flarum/pusher - v1.8.1
        • flarum/statistics - v1.8.1
        • flarum/sticky - v1.8.1
        • flarum/subscriptions - v1.8.1
        • flarum/suspend - v1.8.2
        • flarum/tags - v1.8.2

        Many of these changes were made possible thanks to the input of @glowingblue 💝

          IanM
          Thank you! Just a curiosity: The extension manager was not seeing the core update, only extension.
          Run the global update from the extension manager has upgraded Flarum.

          What happen?
          When I read some extension update has been released I checked today for updates in the extension manager.
          The extension manager just showed two extensions to update but not the Flarum core.
          I decided to run the global update and Flarum was also upgraded but the upgrade of Flarum has not been showed as available update in the extension manager.

          • IanM replied to this.

              peopleinside releasing and tagging core and extensions is a manual task, so you probably just caught me whilst I was still tagging each extension.

              We always tag the core release last of all, after each extension, so I think you were probably just a little to fast in this case 🙂

                  When I log in in the admin and load admin#/basics a blank page empty is showed.
                  This issue is present in more then one community. It's a bug of the new flarum core version?
                  Are you able to replicate?

                  Browser console have to say:

                  TypeError: t.tag is undefined
    c render.js:141
    c render.js:160
    c render.js:66
    l render.js:50
    c render.js:103
    c render.js:62
    l render.js:50
    c render.js:134
    c render.js:63
    l render.js:50
    c render.js:134
    c render.js:63
    l render.js:50
    c render.js:134
    c render.js:63
    c render.js:162
    c render.js:66
    l render.js:50
    c render.js:103
    c render.js:62
    h render.js:487
    h render.js:419
    p render.js:302
    exports render.js:964
    s mount-redraw.js:14
    m router.js:114
    promise callback*t router.js:126
    F router.js:95
    s render.js:30
    exports render.js:971
    mount mount-redraw.js:45
    y router.js:160
    mount Application.tsx:332
    mount AdminApplication.tsx:96
    boot Application.tsx:303
    <anonymous> admin:1441
mount-redraw.js:15:23

                    peopleinside this will be triggered by a particular extension. Unfortunately it's not possible to work out which one by the error you have shared. Can you please try turning off extensions one at a time to see which one is causing the issue?

                        Thank you, heroes!
                        The update has been applied, no issues so far, and it seems faster?

                        peopleinside same problem

                        TypeError: Cannot read properties of undefined (reading 'view')

                         at render.js:141:24
    at render.js:160:3
    at c (render.js:66:8)
    at l (render.js:50:5)
    at render.js:103:4
    at c (render.js:62:15)
    at l (render.js:50:5)
    at render.js:134:5
    at c (render.js:63:14)
    at l (render.js:50:5)
s @ mount-redraw.js:15

                            In the Flarum logs I can find:

                            [2024-10-08 10:06:01] flarum.ERROR: Symfony\Component\Console\Exception\NamespaceNotFoundException: There are no commands defined in the "drafts" namespace. in [...]/vendor/symfony/console/Application.php:650
                            Stack trace:
                            #0 [...]/vendor/symfony/console/Application.php(701): Symfony\Component\Console\Application->findNamespace()
                            #1 [...]/vendor/symfony/console/Application.php(259): Symfony\Component\Console\Application->find()
                            #2 [...]/vendor/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun()
                            #3 [...]/vendor/flarum/core/src/Console/Server.php(42): Symfony\Component\Console\Application->run()
                            #4 [...]/flarum(22): Flarum\Console\Server->listen()
                            #5 {main}
                            The other error in browser developer console that I see is:

                            Errore nella mappatura delle origini: No sources are declared in this source map.
                            URL risorsa: /assets/admin-it.js?v=99897b2b
                            URL mappa delle origini: /assets/admin-it.js.map

                            More info: https://firefox-source-docs.mozilla.org/devtools-user/debugger/source_map_errors

                            • IanM replied to this.

                              After update, Basic into admin dashboard its empty.

                                When this kind of issues are released with a new Flarum version, there is no way to roll back?
                                I suppose not, for now Flarum admin base settings should stay inaccessible until a fix will be released :-)