Skip to content

Can you adjust Admin settings on your NodeBB?

Bugs
5 2 2.0k 1
  • wrote on last edited by
    #1

    I made post on NodeBB community under the Bug thread: about not being able to adjust or save repuation related action values in admin>settings>reputation
    It wont accept any less than zero anywhere.
    The reply was to raise a bug issue on github which I did.
    However I note in my console log I get errors:
    error loading admin/settings/reputation
    Error: Cannot find module ‘./settings/reputation’
    Its as if its looking for a file thats not in my set up?

    Can a bug this fundemental really still exist for everyone?
    If anyone could try adjusting a setting on your admin panel,
    E.g minimum reputation needed to chat -1
    will yours save the page with any negative value in any field?

  • wrote on last edited by
    #2

    Just an update,
    it looks like a fix has been added for this issue (for 3.2.0 milestone), it has “the regression label” on the fix,
    What does Regression label mean in this context?
    When likely can I upgrade to the mentioned 3.2.0 ?

  • Just an update,
    it looks like a fix has been added for this issue (for 3.2.0 milestone), it has “the regression label” on the fix,
    What does Regression label mean in this context?
    When likely can I upgrade to the mentioned 3.2.0 ?

    wrote on last edited by
    #3

    @Panda I don’t see this as a bug to be fair. Why would you set a negative value on any of these when 0 would suffice?

  • @Panda I don’t see this as a bug to be fair. Why would you set a negative value on any of these when 0 would suffice?

    wrote on last edited by Panda
    #4

    @phenomlab because if you have a forum (like political) where people have different opinions and may downvote a response, just being at a negative rep shouldnt necessarily block someone from all features.
    This wouldnt apply on a page like this where people only upvote others, Im thinking in the case of a more volatile or debating forum

    Of course one option would be to remove downvoting, which seems to be the case on sudonix 🙂
    Anyway it used to work, and suddenly broke. I figured out thats what the Regression tag means!

  • @phenomlab because if you have a forum (like political) where people have different opinions and may downvote a response, just being at a negative rep shouldnt necessarily block someone from all features.
    This wouldnt apply on a page like this where people only upvote others, Im thinking in the case of a more volatile or debating forum

    Of course one option would be to remove downvoting, which seems to be the case on sudonix 🙂
    Anyway it used to work, and suddenly broke. I figured out thats what the Regression tag means!

    wrote on last edited by phenomlab
    #5

    @Panda as, yes, now I understand and that makes 100% sense. It means those who get down voted can still have an opinion and use common services.

    And yes, you’re right. Rather than down vote, just ignore if you don’t agree.


Related Topics
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    6k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • 4 Votes
    7 Posts
    3k Views
    crazycells
    @phenomlab oh no, that is 1 cent on the video, but you are right, symbols are similar… I just converted it to $1 , since it is more intuitive in daily life…
  • Nodebb 3.2.2

    Bugs nodebb 3.2.2
    27
    1
    11 Votes
    27 Posts
    11k Views
    phenomlab
    @crazycells yes, I’ve just seen that and modified the post. It seems to only happen if you have a space between the “greater than” symbol and the actual text. Clearly a markdown thing.
  • Removing blue 'moved' tag from post

    Solved Configure nodebb
    16
    2
    3 Votes
    16 Posts
    5k Views
    Panda
    @phenomlab Ah, got it working! I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters. So made the new fork title longer and button responded.
  • Changing Background on NodeBB

    Solved Customisation background image nodebb
    4
    0 Votes
    4 Posts
    2k Views
    phenomlab
    @cagatay You’d target the body tag and use the below line of CSS background: url(/assets/customcss/backgrounds/default/default.png) no-repeat center center fixed; Obviously, you need to change the path to suit where your image is being stored. More info around the background property can be found here https://www.w3schools.com/cssref/css3_pr_background.php
  • Error install plugin

    Solved Customisation plugin nodebb
    8
    1
    1 Votes
    8 Posts
    6k Views
    DownPW
    @pobojmoks Not WP plugin but nodeBB but it a known bug
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    17k Views
    DownPW
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • [NODEBB] Help for my custom CSS

    Solved Customisation nodebb css bugfix
    258
    49 Votes
    258 Posts
    173k Views
    cagatay
    mark hi, Refused to apply style from ‘https://efelsefe.com/assets/customfonts/FontAwesome-6-Pro/pro/css/v4-font-face.css’ because its MIME type (‘text/plain’) is not a supported stylesheet MIME type, and strict MIME checking is enabled. I keep getting this error.