Forum as thread/topic name more than once in category


  • GNU/Linux

    Hi, Just noticed that NodeBB would reboot if I named another thread topic 'Forum' a second time in a category.. first time seems its ok, second time I get reboot of the server every time then have to purge the thread.. lol

    Truly strange behaviour, haven't experience it on 0.6.*


  • Admin

    I can't reproduce this can you post your server logs when the crash happens?


  • GNU/Linux

    Actually occurs when you 'click' on the Thread named 'Forum' to open it (The second Thread named 'Forum' in the Category)
    This is a thread in my 'FAQs & Guidelines' Category (naturally prefixed with Forum in the title)

    15/3 14:10 [7856] - info: NodeBB Ready
    io: 1 emit [ 'event:connect' ]
    io: 1 emit [ 'event:user_status_change', { uid: 1, status: 'online' } ]
    15/3 14:10 [7856] - verbose: [meta/css] stylesheet.css committed to disk.
    io: 1 emit [ 'disconnect',
      { reason: 'transport close',
        rooms: [ 'YDukvcdaiSebO5rJAAAA', 'uid_1', 'online_users', 'admin' ] } ]
    io: 1 emit [ 'event:user_status_change', { uid: 1, status: 'offline' } ]
    io: 1 emit [ 'event:connect' ]
    io: 1 emit [ 'event:user_status_change', { uid: 1, status: 'online' } ]
    io: 1 emit [ 'event:connect' ]
    io: 1 emit [ 'event:user_status_change', { uid: 1, status: 'online' } ]
    io: 1 emit [ 'disconnect',
      { reason: 'transport close',
        rooms: [ '0lmFnx6niz-6bQCfAAAC', 'uid_1', 'online_users' ] } ]
    io: 1 emit [ 'event:connect' ]
    io: 1 emit [ 'event:user_status_change', { uid: 1, status: 'online' } ]
    [cluster] Child Process (7856) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    

    Above is me restarting the server , waiting until it's ready and then clicking on the Thread named just plain 'Forum'.
    As you can see it restarts the server every time I do this.


  • GNU/Linux

    @baris this is happening quite a bit I've noticed now not just how I've dscribed ? Topic badges ?
    Is there a situation when there are too many & 's or html codes that will cause it to break ?

    Just did a --reset all

    Allowed plugin one by one. All plugins enabled and everything is working again 100% hmm


 

Suggested Topics

| |