meihuak can you confirm that Flarum's native search now works properly, even with less search character? Because if that doesn't work then this extension doesn't either.

    a month later

    Justoverclock yeah, you can refund them and they can donate it to Flarum (if they still want that) or you keep the money and donate it to the project. I'm trying to stay out of the way as much as I can as refunding is something you can tackle from your end through stripe.

      luceos yeah i mean something to fix this problem. @meihuak says that don't want a refund. Of course i can donate the amount to flarum

        meihuak this is related to Flarum api, not directly to my extension. So here we need a core dev that can help you, can you open an issue on GitHub into the Flarum framework repository?

          4 months later

          1.3.4

          fixes and improvements

          • Added avatar tooltip
          • Avatar now point to user profile
          • added option to show/hide excerpt tooltip
          13 days later

          Hi @Justoverclock

          I have a suggestion to improve this extension. I've recently been testing another one that contains a great feature to replace user avatars with the most recent comment.

          Is it possible to include this feature here? Right now my forum is using this on the front page, but when you go to a discussion and check the related ones, you can't see the same behavior, obviously.

          https://discuss.flarum.org/d/32368-last-post-avatar

          Thank you.

          Edit: I'm still getting the same problem since I installed it. Sometimes I create a discussion and it shows up as a related one when it shouldn't. Does the SQL query exclude the current discussion?

          8 months later

          how can I remove this extension?

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

          Problem 1
          - Root composer.json requires justoverclock/related-discussions *, found justoverclock/related-discussions[1.3.4] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

            a month later