Community

How about give reputation system more choice?

General Discussion

Suggested Topics

  • Fei XieF

    Separate System config data from User data

    General Discussion
    0 Votes
    7 Posts
    2324 Views
    BartVBB

    For a large part this is an architectural issue.
    It would extremely useful if it were possible to test a plugin on the production database in a development or staging environment.

    That's not possible when NodeBB gets the list of activated modules from the database.

    We have a similar problem like this with Drupal7. It's close to impossible to test something on the production data without making a copy (which is extremely unpractical with a large DB) because of the tight coupling between configuration and content.

    Haven't used it yet but Drupal 8 has improved on that issue quite a bit:

  • ?

    Remove Reputation Display in Profiles

    General Discussion
    0 Votes
    3 Posts
    1586 Views
    yariplusY

    @Joenel-de-Asis172 That is actually the best way to do it. 👍

    The other way would be to remove that html from the profile template in your theme. However, unless you are making your own custom theme, your changes may get overwritten when the theme updates.

    So CSS is the way to go.

  • Jesse PulferJ

    Gamification

    General Discussion
    7 Votes
    9 Posts
    7063 Views
    psychobunnyP

    Should be compatible with 0.8x but I haven't updated the package.json yet. For now you can install manually. Although there's still quite a lot of work to be done before its complete!

  • exodoE

    [nodebb-plugin-reputation-rules] Reputation Rules Plugin for NodeBB

    NodeBB Plugins
    10 Votes
    53 Posts
    9955 Views
    TheBronxT

    @phenomlab as I said we would first have to decide what to put there instead of the hardcoded formula. A fixed number? a percentage of user's reputation? another formula that I would have to parse?

    What would you prefer?
    Cause if the problem is that the users complain and you just want to completely remove this limit, well, a toggle to disable this limitation would be the ideal solution.
    If instead you like having a limit but you just want a fixed one, like 100, well, then let's have an input there to set the limit that overrides the formula.
    Or you could also say: I like that the limit depends on how much reputation the user has but instead of a 10% of that reputation I want a 20%.
    Or even more flexible and complex, I want my own formula.

    In summary, what is your use case? What do you want to do with this limit?

  • Netto HikariN

    Update and Plugin System

    General Discussion
    -1 Votes
    4 Posts
    1950 Views
    julianJ

    Hi @Netto-Hikari, thanks for your feedback about our upgrade process 😄 We definitely try to make the upgrade process fluid and straightforward, but if files have been changed, then yes, there will be problems as git will not know how to handle changed files.

    Re:

    When it comes to upgrades, I just simply follow the docs and it always says that I have to commit the changes before.

    Did you mean Step 3? As far as I know, the only thing we ask admins to do before upgrading is back up their data. If you have never changed any of the core files, git should never complain.

    If this ever happens, and you are absolutely sure you didn't change anything, then you are advised to run the following:

    $ git fetch # to grab the latest code (but not apply it) $ git reset --hard origin/v0.5.x # force your local files to match the NodeBB repository *EXACTLY* $ ./nodebb upgrade # then proceed with upgrade as usual

    ^ Hooray, more unsolicited advice from strangers on the internet 😄

    After running those commands, future attempts to git pull should not have git complain.

Copyright © 2023 NodeBB | Contributors