• @a_5mith

    Finally, I've got it back.


  • @planner yeah

  • Anime Lovers

    Was gamification stuff going to show up soon? Or is that already capable through hooks and we are just waiting on a mod for that?

  • Admin

    Or is that already capable through hooks and we are just waiting on a mod for that?

    Pretty much, yeah. I have two in the works atm, ADR and Badges (badges being higher priority atm), not sure if anybody else has any they're working on

  • NodeBB

    Updated this forum to latest from master, let us know if you find any bugs!


  • @baris

    Can you spot the "bug" in this image, taken from the Unread page. Hint: Check the last update times.

  • NodeBB

    @planner don't see anything wrong with the update times, but there was a problem with the permissions which was letting you see topics from a hidden category, clicking on them would go to 404. Fixed that and updated.

    What's wrong with the update times?


  • @baris

    Because I visit this forum at least 3 times/day and then seeing replied 8 days ago and replied 9 days ago on my Unread page tells me there's something wrong somewhere.

  • NodeBB

    Well if you go /unread again it should be fine, you shouldn't see those topics at all.

  • NodeBB

    Related issue: https://github.com/NodeBB/NodeBB/issues/1978

    This is another breaking change. It effects anyone using the hook filter:user.custom_fields and filter:register.build to add custom data to users on registration.

    If you were using filter:user.custom_fields to add new entries into the user object you can just switch the hook you are using to filter:user.create. No need to change anything else.

    If you are using filter:register.build to add new entries into the registration form and want these entries to get added into the user object you need to use the hook filter:user.custom_fields. In your plugin that adds new entries into the registration form just add a listener for filter:user.custom_fields and add the fields that you added to the form into the array passed in, here is a sample.

    // plugin.json
    {
    ...
    "hooks": [
        { "hook": "filter:user.custom_fields", "method": "addCustomFields"}
    ],
    ...
    }
    
    //plugin code
    function addCustomFields(fields, callback) {
        fields.push('newCustomField1');  // must match the input name you added to regForm
        fields.push('otherCustomField1');
        callback(null, fields);
    }
    

    After this when a new user registers they will have newCustomField1 and otherCustomField1 entries in their user object.

    @bentael nothing needs to be done for spam-be-gone since we don't want the captcha form entries in the database anyways.

    Before this change it was possible to add any field into the registration form client side and it was inserted into the database. Now only the fields that core and plugins specify are inserted.

Suggested Topics

| |