Skip to content

NodeBB 1.19.3

Solved Performance
33 2 16.5k 1
  • wrote on last edited by DownPW
    #20

    yes it still here

    EDIT:

    I have remove the directory when I have the problem of install with 1.18.x

    But when I upgrade to 1.19.3, he have reinstalled by default

  • yes it still here

    EDIT:

    I have remove the directory when I have the problem of install with 1.18.x

    But when I upgrade to 1.19.3, he have reinstalled by default

    wrote on last edited by
    #21

    @DownPW I see this

    a325f036-d5d1-44b8-b583-fd6a913a1b43-image.png

  • @DownPW I see this

    a325f036-d5d1-44b8-b583-fd6a913a1b43-image.png

    wrote on last edited by
    #22

    @phenomlab on your website ?

  • @phenomlab on your website ?

    wrote on last edited by
    #23

    @DownPW No - on yours.

  • wrote on last edited by
    #24

    ha lol ok

  • wrote on last edited by DownPW
    #25

    @phenomlab

    because you are guest maybe because not me

  • wrote on last edited by
    #26

    test admin:nodebb

  • test admin:nodebb

    wrote on last edited by
    #27

    @DownPW Same error when logged in

    a42f594b-29be-4ddc-b52f-587f2c8948c9-image.png

  • @DownPW Same error when logged in

    a42f594b-29be-4ddc-b52f-587f2c8948c9-image.png

    wrote on last edited by DownPW
    #28

    @phenomlab

    yes I think there is a problem with that plugin.
    Maybe open a topic with this on nodeBB communauty

  • @phenomlab

    yes I think there is a problem with that plugin.
    Maybe open a topic with this on nodeBB communauty

    wrote on last edited by
    #29

    @DownPW agreed. What happens actually if you change the loading order of that plugin ? You can do that from the ACP -> Plugins

  • wrote on last edited by
    #30

    I put emoji plugin on first load and this :

    7a964714-be9a-4617-9092-225c039e0a9b-image.png

  • I put emoji plugin on first load and this :

    7a964714-be9a-4617-9092-225c039e0a9b-image.png

    wrote on last edited by
    #31

    @DownPW makes no difference then.

  • wrote on last edited by DownPW
    #32

    yes

    dfb0fe53-2897-4660-9390-ab75eee678bd-image.png

    The path doesn’t exist (Assets/plugins/…)

    e2ff90ba-6379-4c9d-bb52-167f0df89166-image.png

    EDIT:

    Sorry Existing path:
    http://192.168.1.53:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u

    e4fd5733-8993-4dbb-8115-d87e8c5bc50e-image.png

  • wrote on last edited by DownPW
    #33

    @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

    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

  • DownPW DownPW has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • 4 Votes
    3 Posts
    2k Views
    crazycells
    thanks @DownPW ! this is definitely very helpful.
  • NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    47
    11 Votes
    47 Posts
    21k Views
    phenomlab
    @DownPW Seems fine.
  • 36 Votes
    55 Posts
    30k Views
    phenomlab
    @DownPW I see why. The code relies on the existence of [component="topic/quickreply/container"] However, this by definition means that the below has to be enabled [image: aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png] It will then work [image: 7fb38631-e0f3-46ef-b652-00929d927b13-image.png] For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component. The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on
  • Fresher in Nodebb install

    General nodebb
    24
    15 Votes
    24 Posts
    11k Views
    phenomlab
    @Hari I’ve been reading a lot about APO. Looks impressive.
  • ineffecient use of space on mobile

    Solved Customisation nodebb
    10
    2
    7 Votes
    10 Posts
    4k Views
    crazycells
    @phenomlab Thanks
  • NodeBB slow after DB recovery

    Solved Performance performance nodebb
    1
    5 Votes
    1 Posts
    967 Views
    No one has replied
  • NodeBB Discord Plugins

    Unsolved Customisation nodebb discord plugin
    7
    0 Votes
    7 Posts
    4k Views
    phenomlab
    @RiekMedia 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 ?
  • 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.