API Update

Feature Requests
  • Hello,

    It would be really really nice if we could have a few more informations on the API.
    For exemple : the number of topic created or total number of user.
    Thoses informations are on /api/admin but we can't get that for our users with JS.

    Is this possible to add that ?
    Or is it already possible to get thoses kind of informations without administration right ?

    Thanks for your time,
    Yoko

  • What you're looking for is implemented in the widget "forum stats", in which you can view the number of posts and number of topics on any page. I'm not a plugin developer (read: javascript noob 8)), but I think it's respectively easy to get this done in a similar fashion.

    I'd recommend looking up the way the module "nodebb-widget-essentials" deals with this. I assume it's easy to API'ify this.


Suggested Topics


  • API token pagination ACP

    Feature Requests
    3
    0 Votes
    3 Posts
    90 Views

    @baris wooow 😮
    Thanks for putting this into a priority 👍

  • Profile custom fields API

    Feature Requests
    1
    1 Votes
    1 Posts
    1k Views

    Hi! I would like to see custom profile fields API. What do i mean:
    http://puu.sh/iKxq0/311f6c3d56.png

    We already have hook for this - filter:user.account, but there is no markup in templates (account/profile.tpl)

    Also it would be nice to add same functionality to account/edit.tpl

  • API reveries

    Feature Requests
    6
    0 Votes
    6 Posts
    2k Views

    @julian said:

    For security, it will be a plugin, and it should be able to mimic anything built into NodeBB.

    That's incredible news - can't wait!

  • 0 Votes
    4 Posts
    2k Views

    This is related to an issue resolved earlier.

    We found that if a topic's posts contained images pointing to a relative path (e.g. ![test](1.jpg), NodeBB would attempt to load them, causing them to load the entire topic again (since the url is site.com/topic/123/1.jpg).

    To combat this, @baris restricted the URL so that the slug must be correct, otherwise the user is sent to 404.

    For lack of a better solution, this was the approach we took, so this seems to be the reason why you're running into this issue now.

  • 0 Votes
    7 Posts
    2k Views

    @psychobunny said:

    TBH I've been an admin/mod in several forums over my life and I always hated the idea of changing usernames in the first place

    ^^ This, usually. It's worse when they start using a new set of graphics to go with their "new persona". To be fair however, I can also remember picking a really stupid username and being glad I could change it. shudders