010101 You would be correct, beta.15 primary goal was to replace events with extenders for extension developers to make use of. These extenders will overall make stable.... stable for developers. By getting all these extenders into place we've made some pretty huge progress towards our stable goals.

    [Symfony\Component\Console\Exception\RuntimeException]
    The "--no-install" option does not exist.

    how can i fix that?

      Justoverclock update composer composer selfupdate --2 or drop the --no-install flag if you can't update composer.

          luceos IT doesn't work if composer is installed globally in usr/bin ☹️

              HD3D probably because it's owned by root. Just prefix the command with sudo on shared hosting environments that won't be possible though. Nevertheless we should promote instructions for recent, stable tools, not outdated ones.

              • HD3D replied to this.

                  Finally decided to update.
                  First step was update composer to version 2 and then all run flawlessly.

                  Crossing my fingers to see improvements on SEO and into translations soon 👍️

                  luceos Silly me, I own the vps and I installed got it installed globally from the host, successfully updated to composer 2 with root access 😀

                    askvortsov i'm still on beta13 too. How about:

                    But I cannot update yet mostly for this missing feature: FriendsOfFlarum/gamification24

                    Or anything else that will excludes admins from the badges game or giving them a special one.

                        Kyrne 📛 New nicknames extension (flarum/nicknames)

                        There's a new nickname extension provided by the flarum team, I am using it and it works very well! I used to use the one you linked, but doesn't appear it's actively updated by the dev.

                        Kyrne [optional] If you'd like to add nicknames support:
                        composer require --no-update flarum/nicknames

                                robinodds If I remember correctly we used the same database column as the nicknames changer extension specifically so that you wouldn't lose that data. Simple remove the nickname changer extension using composer and add flarum/nicknames and it should work. Do note that you have to set the nicknames extension as your display name driver under "Appearance" I believe.

                                  KolaBilewu I think the only issue is if your shared host hasn’t updated to composer 2 yet. If they have not... First, make 100% sure you don’t have any extensions installed which do not have a new beta 15 compatible version. Then run composer update ––with–all–dependencies.

                                  If the update fails, there’s still an extension causing a problem so follow this: https://discuss.flarum.org/d/25733-troubleshooting-beta-15-update-non-composer-2-usersupdate-failed

                                    Why do you recommend using --no-install flag in the first place?
                                    Same with --with-all-dependencies, which make sense only if you specify packages list to update. composer update will update everything, so --with-all-dependencies is redundant.

                                      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.