rob006

My opinion is, as long as you are using Composer 2, --no-install is needed because it gets everything updated without installing things before you realize you have an outdated extension. Or an extension that has no beta 15 compatible version. I don't know about with all dependencies. That might not be needed. But the order in which things are updated is very important or else you could get stuck partially done. I think --no-install helps prevent getting stuck. But, many still only have Composer 1 and can't update. Composer 1 is missing the --no-install option.

      010101 --no-install means that all dependencies will be calculated and composer.lock will be generated. If you can't update (because extension does not allow beta 15), composer update --no-install will fail in the same as composer install - nothing will be saved or installed. It does not make anything safer o simpler, since composer update --no-install && composer install works the same as composer update. As long as you don't want to skip installing new dependencies or want to investigate composer.lock before installing them, it makes no sense to use --no-install, it only makes everything more complicated, especially for Composer 1.x users.

          rob006 I think we incorrectly copied this from the beta 14 announcement where it made sense to delay installation for after oauth had replaced the deprecated auth extensions.

          In the end no harm is done, although it adds unnecessary steps.

          Edit; I guess we reused it so that we can add nicknames before completing installation.

              Nice work!
              Can anyone post a screenshot of the admin dashboard? Curious to see how it looks

                luceos Edit; I guess we reused it so that we can add nicknames before completing installation.

                Actually it does not make sense. composer update calculates new composer.lock based on current composer.json. composer require --no-update flarum/nicknames adds flarum/nicknames to composer.json without updating composer.lock. And then composer install installs all packages from composer.lock. So with this order flarum/nicknames will not be installed, because you calculated composer.lock before adding this new extension to composer.json.

                It should be:

                composer require --no-update flarum/nicknames
composer update --prefer-dist --no-dev -a

                But in general I would recommend first upgrading your forum with current set of extension, and after that adding new one:

                composer update --prefer-dist --no-dev -a
composer require flarum/nicknames --no-dev  --update-with-all-dependencies -a

                If anything fails after first step, no changes will be saved (composer.json, composer.lock and installed dependencies will not change), while composer require --no-update flarum/nicknames may potentially change your composer.json to non-installable state.

                  Just upgraded to beta 15! Thanks you to all the Devs on this release, new admin dashboard looks amazing!

                  danielunited you can visit the demo forums to check the new admin panel out 😉 There are also a few (older) screenshots in flarum/core2409

                  Most extensions which already dropped everything deprecated in beta 14 will work on beta 15, but the developers might need to test it and update the Composer requirements.

                  And there are a bunch of new deprecations which would be best dealt with immediately so any issue can be reported to Flarum.

                    I can't view deleted posts (beta 15). The button (elipsis) is not clickable.

                    "8 dakika önce" means "8 minutes ago"

                      yardimlazim when you click it, do you see an error in the dev tools (inspect element) console tab? If so, please share it.

                          askvortsov it is not like a button. I cannot click. So, I do not see an error.

                          Edit: In addition, I cannot click the username and date.

                          Edit2: There is no li tag for name, date or elipsis button.

                            I meant the logs in the "console" tab of inspect element, not the "elements" tab. It might not be an exact html button but it should still be clickable: my guess is that you're encountering some JS error.

                              askvortsov I meant the logs in the "console" tab of inspect element, not the "elements" tab.

                              I know. But, there is no error. Thanks for your help.

                                Hi friends. I'm currently on beta 13, trying to upgrade as per the beta 14 instructions first. Everything looks perfectly fine on the install, but the flarum version stays at beta 13.

                                What might cause this? I'm not sure how to diagnose with no error messages!

                                  After upgrading to this (15) version, I can see the new Extensions view, but there is no way to browse/add new extensions? I can only search in already installed extensions.

                                  • ctml replied to this.

                                    Great update! Where in the admin panel are the settings for slug?
                                    slug_driver_heading: "Slug Driver: {model}"

                                    And when notifications come to email in the body (string: {url}) do not have transliteration
                                    (only https://example.com/d/2/57).