Skip to content

NodeBB v3 Chat Very Slow

Moved Performance
47 3 20.9k 1
  • wrote on last edited by
    #28

    That’s a regression bug I think. You now have to press ALT + ENTER to get an extra line appear

  • Here I think

    f291b2b3-ef26-4d42-8ae8-41d972314900-image.png

    wrote on last edited by
    #29

    @DownPW said in NodeBB v3 Chat Very Slow:

    Here I think

    f291b2b3-ef26-4d42-8ae8-41d972314900-image.png

    yes you are right @DownPW
    @phenomlab how can i expand it?

  • wrote on last edited by
    #30

    Odd, node like that on nodebb communauty

  • Odd, node like that on nodebb communauty

    wrote on last edited by
    #31

    @DownPW as I said previously, likely a regression introduced by 3.2.0

  • wrote on last edited by
    #32

    But nodebb forum communauty is on 3.2.0 no ?
    If yes, they don’t have this problem

  • wrote on last edited by
    #33

    They deactivate background and box shadow on nodebb communauty :

    image.png

  • They deactivate background and box shadow on nodebb communauty :

    image.png

    wrote on last edited by
    #34

    @DownPW None of those will impact the box size. Let me have a look.

  • wrote on last edited by
    #35

    yep not box size but we don’t see the bug

  • yep not box size but we don’t see the bug

    wrote on last edited by
    #36

    @DownPW what exactly is the bug? I’ve tested it, and it behaves normally from what I see (unless I completely missed something)?

  • wrote on last edited by
    #37

    Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

  • Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

    wrote on last edited by
    #38

    @DownPW Yes, that’s input:focus - it’s used to style much larger boxes on focus, but I’ll need to create an exemption here.

  • wrote on last edited by
    #39

    Nodebb communauty :

    image.png

  • Nodebb communauty :

    image.png

    wrote on last edited by phenomlab
    #40

    @DownPW @cagatay Thanks for reporting. Should match now.

    f99597be-2d44-4c14-a46d-c803de6d9347-image.png

  • wrote on last edited by
    #41

    yep better 🙂

    Solution ?

  • yep better 🙂

    Solution ?

    wrote on last edited by phenomlab
    #42

    @DownPW As you indicated, but I need to make this more specific because it disables a wanted UI experience elsewhere

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        /*box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important; */
        border-color: transparent !important;
    }
    

    Starting with this CSS

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #43

    Have you find better solution or this is the final @phenomlab ?

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #44

    @DownPW this is the final solution from my perspective. The above code resolves the issue here.

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #45

    @DownPW i m also using last codes on my web site.

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #46

    I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
  • I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
    wrote on last edited by
    #47

    @DownPW Seems fine.


Related Topics
  • 4 Votes
    3 Posts
    2k Views
    crazycells
    thanks @DownPW ! this is definitely very helpful.
  • www. Infront stops website access?

    Solved Configure nodebb
    10
    1 Votes
    10 Posts
    3k Views
    phenomlab
    @Panda because there is no match for the DNS entry specified. The receiving web server parses the headers looking for a destination hostname to match, and anything the web server is unable to resolve will be sent back to the root.
  • Interesting Widget code, but can't fetch API

    Solved Customisation nodebb
    26
    2 Votes
    26 Posts
    11k Views
    phenomlab
    @Panda said in Interesting Widget code, but can’t fetch API: How did you drop that widget into the post there? I hadnt seen this BSgenerator anywhere on sudonix site, do you use it somewhere already? Yes, here https://sudonix.org/topic/414/corporate-bullshit-generator?_=1687774393044 It’s not a “post” or “topic” in the common sense. It is actually a page in it’s own right and leverages nodebb-plugin-custom-pages. This in turn creates a new “route” which behaves like a page, meaning it is then exposed for widgets. @Panda said in Interesting Widget code, but can’t fetch API: Also can you explain more what you mean by calling the code externally. In my API call example, how would I go about doing that? By this, I mean create all the required code in an external JS file that is reachable by the NodeBB instance - so, in “public” for example - or in my case /public/js. The widget then “calls” that file and because it runs outside of the scope of NodeBB, you just need to return the values to the widget. Hope this makes sense?
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • NodeBB v3.0.0-rc.1

    Performance nodebb v3.0.0
    1
    1 Votes
    1 Posts
    701 Views
    No one has replied
  • Optimum config for NodeBB under NGINX

    Performance nginx performance
    4
    3 Votes
    4 Posts
    2k Views
    phenomlab
    @crazycells hi - no security reason, or anything specific in this case. However, the nginx.conf I posted was from my Dev environment which uses this port as a way of not interfering with production. And yes, I use clustering on this site with three instances.
  • 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/
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    4k Views
    phenomlab
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.