clarkwinkelmann I will add google adsense. I blocked the user list page with /robots.txt from accessing bots. But since google ad will appear on this page, my site may be spammed by google.

7 days later

I wonder what has to be changed to offer ejinLikeCount in the drop down list.

In the UserDirectory.php I found:

        'username_az' => 'username',
        'username_za' => '-username',
        'newest' => '-joinedAt',
        'oldest' => 'joinedAt',
        'seen_recent' => '-lastSeenAt',
        'seen_oldest' => 'lastSeenAt',
        'most_discussions' => '-discussionCount',
        'least_discussions' => 'discussionCount'

But there are several other places to be changed. Anyone tried that already to offer a sort by "LIKES" (ejinLikeCount) from the "api/users".

a month later
2 months later

Pika They are going through all of their extensions and updating them. They have a big list and since they are also the core team, it will take them some time. They will get to it and will post when it is compatible. They have already updated a lot of extensions so I am sure they will be getting to this one soon. I am waiting for this one also so am excited too.

5 days later

Version 0.4.0

  • Added beta 14 support
  • Added setting for default sorting

You might need to remove this extension to perform the Flarum update due to the major update. You can safely uninstall it with composer remove fof/user-directory and re-install it once the update is completed.

clarkwinkelmann changed the title to FriendsOfFlarum User Directory .

DursunCan as I explained in FriendsOfFlarum/sitemap18 it must be caused by one of the other extensions you have installed that didn't use the new View extender from beta 14.

The fact it happens on multiple extensions seems to confirm that theory. The problematic extension will be an extension that was enabled before those FoF extension. Likely not an FoF extension since we have taken special care to have them properly updated for beta 14.

    DursunCan I have added a comment over there.

    If looking for the string in the source code doesn't work, the way to isolate the issue would be to disable community extensions one by one (except user-directory or another one with the hint issue), until the issue disappears. Then we will know the last extension that was disabled was causing the issue.

    I'm trying to install it but i get these errors
    Your requirements could not be resolved to an installable set of packages.

    Problem 1
    - Can only install one of: fof/components[0.2.0, 0.1.1].
    - Can only install one of: fof/components[0.2.0, 0.1.1].
    - Can only install one of: fof/components[0.2.0, 0.1.1].
    - fof/user-directory 0.4.0 requires fof/components 0.2.0 -> satisfiable by fof/components[0.2.0].
    - Installation request for fof/user-directory 0.4.0 -> satisfiable by fof/user-directory[0.4.0].
    - Installation request for fof/components (locked at 0.1.1) -> satisfiable by fof/components[0.1.1].

    Installation failed, reverting ./composer.json to its original content.

    21 days later
    • [deleted]

    • Edited

    Bug in Beta 14 version

    If you attempt to go to the direct URL of the page without navigating through the site

    [2020-12-07 18:43:15] flarum.ERROR: InvalidArgumentException: No hint path defined for [fof.user-directory]. in /home/domain/public_html/vendor/illuminate/view/FileViewFinder.php:112

      [deleted] this error is usually caused by a different extension that's loaded before the one that triggers the error.

      I have noticed FoF Upload has incorrect view path definition, so it might be the cause.

        9 days later
        19 days later

        how can i install compatible version for beta-13 ?
        it is giving error wants beta-15 but i dont want to update beta-15 yet 😃