Delete User

NodeBB Development

Suggested Topics


  • 0 Votes
    1 Posts
    158 Views

    Hi folks,

    I want to validate ( need to make email confirmed property true) user under filter:register.shouldQueue filter. Is any way to do this ?

    Feedback appreciated
    Thanks

  • 0 Votes
    4 Posts
    2k Views

    Anyone knows if theres the possibility of registering an user link in the dropdown, that will be public only? Like the case for example of the "chat link", but registered vía filter:user.profileLinks hook.

    Since in that hook theres no user info, i cannot check if the user visualizing the page is the users itself that is visualizing his/her profile or if the user its logged in, to restrict the link registration.

    I want to implement the functionality of "ignore users" showing a link that can be used to ignore, unignore from the user profile. But it has no sense to show the link "ignore/unignore user" if it is the user itself or the user visiting the profile is not logged in.

    I know it can be easilly achived by adding one more attribute to the link object and modifying the menu.tpl with minor changes to reflect this behaviour (checking the new field), and without altering the existing behaviour of the theme. If the answer to the previous question is "no", what is needed to get a pull request including this behaviour accepted? Modification in all stable themes? (persona,lavender,vanilla?).
    Or would it be more suitable a request of a new action hook for action:user:viewProfile for example? To be able to make business logic checks with the data, and altering the content sent to the page for example?

    PS: Is there any way of contributing to document the list of hooks with a short explanation of each one? For example when they're fired and wich information do they send? I think it would be a good improvement for the documentation in order to make it easy to the plugin dev to without the need to dive into the core and check each hook one by one looking for one satisfying their needs. I wouldn't mind to throw 2/3 lines explaining the hooks I found useful that i'm seeing on my little plugin experiments from a noob perspective. Ping @administrators

    Thanks again and sorry for modifying the thread question.

  • 0 Votes
    3 Posts
    2k Views

    Those userrs are stored in groups with special names, here are the names assuming the category id is 1.

    cid:1:privileges:find
    cid:1:privileges:read
    cid:1:privileges:topics:create
    cid:1:privileges:topics:reply

    You can get the user ids from these groups by.

    Groups.getMembers('cid:1:privileges:find', 0, -1, callback); This will give you all the user ids that have the find permission for category 1.

    If you want to get their basic info like username picture slug so you can show user icons you can just use Groups.getMemberUsers('cid:1:privileges:find', 0, -1, calllback);

  • 1 Votes
    2 Posts
    922 Views

    My best guess is that between .6 and .7, we made the decision to only show a certain set of profile settings. Prior to this change, any plugin could save any data into the user's account hash, which was a potential security vulnerability.

    Now, you'll have to register a listener to filter:user.updateProfile, and append the field you want to save.

    I think this is what's going on...

  • 0 Votes
    4 Posts
    2k Views

    As for the ACP, it has not been implemented yet. However, the ability to delete a user is one of the features listed for NodeBB0.4.0 on GitHub. Let's just hope that it makes it. You may tack its progress here.

    It's been completed. Check out the latest git pull