0.3.0

  • beta 14 ready 🥳
Updating
composer require fof/username-request
php flarum cache:clear
a month later
a month later

Does this show users previous username in their profile if it's changed to a new one?

    JAC yes there's a new page in the user profile with the history of username changes.

    I'm not sure who can see the page though, because there doesn't seem to be an associated permission.

    • JAC replied to this.

      clarkwinkelmann yes there's a new page in the user profile with the history of username changes.

      I'm not sure who can see the page though, because there doesn't seem to be an associated permission.

      Brilliant, thanks for confirming 🙂

      v0.4.1

      Now supports nickname requests. To require that a request be made to change nicknames, you'll want to set the permission for requesting nickname changes to "Members", and turn the "change own nickname" permission to whatever groups should be able to change nicknames without requesting.

      a month later

      0.4.2

      Thank you @iPurpl3x 👍

      composer require fof/username-request:"*"

      Sorry, I didn't notice it was solved!

      Username request is showing in notification for Admin but when I open it, I am not seeing any request to approve. This happens for users who used oauth to sign up.

        Ffuser1 are you able to reproduce reliably. Are you certain it's related to oauth or just some users? If it's just some users, could they try hard-refreshing the page or using private browsing to see if it solves the issue?

        Are all those users administrators?

        It's applicable to all users not just oauth. Before the last two upgrade I was able to approve (version 0.4.0). This issue started after upgrading to version 0.4.2.
        Normal members and mods requested change, Admin to approve in settings but nothing is showing to approve.
        I've checked and no error in flarum log.

          Ffuser1 you can try composer require fof/username-request:0.4.0. Note that you will need to run composer require fof/username-request or composer require fof/username-request:* again once you want to update, as the Composer update command will have no effect after forcing a fixed version.

          Le us know if that resolves the issue, so we know if that's indeed the new version causing it. I'm personally not using the extension so cannot check right now.

            16 days later

            I noticed that even the admin can request an username change... to himself. It's a bit odd since he can edit whenever he want.

              enricodx this is expected 🙂 if you don't want your Admin group to be able to use this feature, you can simply turn it off via permissions.

              Ffuser1 did you try clearing your Flarum cache? I wasn't able to reproduce this either even when using an OAuth provider such as GitHub. Did you check the browser console for any possible errors?

                Ralkage if you don't want your Admin group to be able to use this feature, you can simply turn it off via permissions.

                Not possible, admin group can do anything. That being said, it's a redundant feature, but useful if admins want to see what the process is like for regular users.

                  askvortsov this is what happens when you skip the first cup of coffee 😆 what you said in the second part was my initial thought and I decided to go against my gut this time 😞 I also keep forgetting that the Admin group runs the show 🤣 thank you for clarifying.

                  9 days later

                  0.5.0

                  Updating
                  composer require fof/username-request:"*"
                  php flarum cache:clear