Skip to content

NodeBB v3 Chat Very Slow

Moved Performance
47 3 20.9k 1
  • After upgrading 3.2.0, the typing field is narrowed.

    wrote on last edited by
    #26

    @cagatay In where, and what ?

  • wrote on last edited by
    #27

    Here I think

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

  • 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;
    }
    

Related Topics
  • External Links - New Window

    Solved Customisation nodebb links settings
    8
    2 Votes
    8 Posts
    2k Views
    phenomlab
    @Sampo2910 search the forum here for ogproxy which is the client side version of that plugin I wrote. It’s in use here on this forum.
  • 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.
  • SEO and Nodebb

    Performance nodebb seo
    2
    2 Votes
    2 Posts
    2k Views
    phenomlab
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • adding some console.log to Nodebb

    Solved Customisation nodebb
    4
    1 Votes
    4 Posts
    2k Views
    phenomlab
    @eeeee if you’re using the console, you could try node app.js > app.log 2>&1 This would redirect stdout to a file named app.log and redirect stderr to stdout. I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log. Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.
  • 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.
  • Plugin reaction Bug

    Solved Customisation plugin nodebb reaction
    15
    1
    0 Votes
    15 Posts
    6k Views
    phenomlab
    @DownPW That was going to be my next suggestion
  • ineffecient use of space on mobile

    Solved Customisation nodebb
    10
    2
    7 Votes
    10 Posts
    4k Views
    crazycells
    @phenomlab Thanks
  • Fontawesome 5

    Unsolved Customisation fonts css nodebb
    14
    1 Votes
    14 Posts
    6k Views
    phenomlab
    @pwsincd hi. Just following up on this thread (I know it’s old) but was curious to understand if it’s still an issue or not ?