Skip to content

Nodebb 3.2.0

Bugs
20 4 6.8k 2
  • Hi Mark.

    There is a problem after upgrading to v 3.2.0 on first post as below;

    39005d2a-11b3-4531-afe2-6298e2ac4afb-image.png

    Post link is;

    https://efelsefe.com/topic/1581/ölçmek

    wrote on last edited by
    #2

    @cagatay Can you explain the issue in more detail? Apart from some minor CSS alignment, it’s not obvious.

  • wrote on last edited by
    #3

    i think my css codes should be cleared.
    vote area not working for example as for the first post.
    and that photo was taken by andorid phone.

  • i think my css codes should be cleared.
    vote area not working for example as for the first post.
    and that photo was taken by andorid phone.

    wrote on last edited by
    #4

    @cagatay In the console, I see Adding required classes for messenger type view which would have been a modified class that referred to the messenger type view I created for 1.x of the NodeBB software. As previously stated, it’s not valid for 3.x so will need to be removed.

    I’ll login to your site now and take a look.

  • @cagatay In the console, I see Adding required classes for messenger type view which would have been a modified class that referred to the messenger type view I created for 1.x of the NodeBB software. As previously stated, it’s not valid for 3.x so will need to be removed.

    I’ll login to your site now and take a look.

    wrote on last edited by cagatay
    #5

    @phenomlab thank you for your prompt response.

  • @phenomlab thank you for your prompt response.

    wrote on last edited by
    #6

    @cagatay No problem. Reload your site and test.

  • wrote on last edited by
    #7

    yes, everything is okey now, but changed my icon for upvote and downvote 🙂

  • yes, everything is okey now, but changed my icon for upvote and downvote 🙂

    wrote on last edited by
    #8

    @cagatay Yes, you’ll need to set those back to what you want them to be.

    I had to remove all of your CSS, and replace it with a working copy I have. This issue stems from new classes and viewports being introduced in 3.2.0 and because you had overriding classes from the previous 1.x version, it caused the issues you were experiencing.

    The upside of this is that this CSS code is bleeding edge - the downside is that any customisations you made will need to be put back.

  • wrote on last edited by
    #9

    thank you Mark.

  • wrote on last edited by
    #10
    This post is deleted!
  • wrote on last edited by
    #11

    For my part, since I upgraded to 3.2.0, the page takes longer to load than before and I see this socket error :

    ba99dc1a-ba4a-4b23-ace0-6cf17975439f-image.png

  • For my part, since I upgraded to 3.2.0, the page takes longer to load than before and I see this socket error :

    ba99dc1a-ba4a-4b23-ace0-6cf17975439f-image.png

    wrote on last edited by
    #12

    @DownPW can you try disabling Cloudflare and let me know if that resolves the issue?

  • wrote on last edited by DownPW
    #13

    @phenomlab

    If is here, already disable.

    image.png

    Same in incognito

    if i disable OGproxy (ACP/custom JS), it’s better (more fast) but I have the error.

  • @phenomlab

    If is here, already disable.

    image.png

    Same in incognito

    if i disable OGproxy (ACP/custom JS), it’s better (more fast) but I have the error.

    wrote on last edited by
    #14

    @DownPW OGProxy has no bearing on sockets. The only thing that could possibly slow down a reverse proxy is a slow DNS lookup. What happens if you change the DNS to (for example) 8.8.8.8 or 1.1.1.1 ?

    Do you have any firewall device in between the internet and your server?

  • wrote on last edited by DownPW
    #15

    @phenomlab

    hmmm no and no. I have test on 2 diffèrent physical site (home and work)
    Since upgrade, I haven’t constated this.

    I haven’t this error on my VM in local (no domain)
    I have deactivate proxied on DNS entry on Cloudflare = same

  • @phenomlab

    hmmm no and no. I have test on 2 diffèrent physical site (home and work)
    Since upgrade, I haven’t constated this.

    I haven’t this error on my VM in local (no domain)
    I have deactivate proxied on DNS entry on Cloudflare = same

    wrote on last edited by
    #16

    @DownPW I’ll have a look at this tomorrow. I assume this is your Dev server?

  • wrote on last edited by
    #17

    Yes dev serv

  • @phenomlab

    hmmm no and no. I have test on 2 diffèrent physical site (home and work)
    Since upgrade, I haven’t constated this.

    I haven’t this error on my VM in local (no domain)
    I have deactivate proxied on DNS entry on Cloudflare = same

    wrote on last edited by
    #18

    @DownPW Just checked your site this morning. I see no slowness at all, and there are no socket errors for me 🙂

  • wrote on last edited by
    #19

    hi @phenomlab , I think there is a bug on /groups page, “verified” group looks weird.

    https://sudonix.org/groups

  • hi @phenomlab , I think there is a bug on /groups page, “verified” group looks weird.

    https://sudonix.org/groups

    wrote on last edited by phenomlab
    #20

    @crazycells yes, I’m aware of that. Need to fix

    EDIT- fixed. Caused by the same CSS that is used to absolutely position the “verified” group badge in the posts view. Amended this CSS so that is specifically targets the post stream as below

        li[component="post"] a[href*="/groups/verified"] {
            position: absolute !important;
            left: 8px;
            z-index: 2;
            margin-top: 1px;
            border-radius: 999px !important;
            line-height: 14px;
            display: block;
            height: 22px;
            margin-left: 0px !important;
        }
    

Related Topics
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k 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.
  • nodebb error logs

    Bugs nodebb
    6
    2
    4 Votes
    6 Posts
    2k Views
    ahmed
    I just wanted to ask because I don’t have much knowledge about the new installation. Thank you for the explanatory answer.
  • 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.
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    3k Views
    phenomlab
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • NodeBB upgrade now cant post

    Solved Bugs nodebb
    5
    2 Votes
    5 Posts
    2k Views
    phenomlab
    @Panda yes, for some reason, that is the case. If you need an urgent response, it’s probably better to post here because of the time difference.
  • NODEBB: Nginx error performance & High CPU

    Solved Performance performance nodebb nginx
    69
    4
    14 Votes
    69 Posts
    63k Views
    DownPW
    @phenomlab Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made # I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000 If you have other Redis optimizations. I take all your advice https://severalnines.com/blog/performance-tuning-redis/
  • 0 Votes
    5 Posts
    2k Views
    phenomlab
    @qwinter this particular site uses the code I wrote if you want to see it in action. It’s a information and intelligence gatherer I designed for collecting various information security articles from around the globe and consolidating them in one place. Essentially, each “post” is in fact generated by the script, and the NodeBB API. https://hostrisk.com/
  • Adjusting the size of boxes in posts-list class

    Solved Customisation nodebb
    3
    3 Votes
    3 Posts
    2k Views
    crazycells
    @phenomlab thanks a lot, this combination works best .posts-list .posts-list-item .content { overflow: auto; max-height: 600px; }