Buy Hosting

Website auto stop

Unsolved Bug Reports

Suggested Topics

  • T

    When reloading a website while writing a post, the title of the post doesn't get saved

    Bug Reports
    0 Votes
    2 Posts
    273 Views
    PitaJP

    You should really be submitting bug reports to the NodeBB GitHub page, or the respective plugin page

  • O

    bug in 1.5.1 ,cpu 100% and Paging auto jump

    Bug Reports
    0 Votes
    5 Posts
    2k Views
    barisB

    bug in category page navigation · Issue #5752 · NodeBB/NodeBB

    turn on pagination inside a category go to page 4 then scroll down and enter a topic click back to go to page 4 (the page scrolls down to the clicked topic) now click page 1 page 1 loads and then to goes to page 4 and scrolls to topic

    favicon

    GitHub (github.com)

  • П

    NodeBB v1.0.4-auto.2 many crashes

    Bug Reports
    0 Votes
    1 Posts
    837 Views
    П

    NodeBB v1.0.4-auto.2

    29/5 02:45 [782] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 29/5 02:45 [779] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. (node) warning: possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit. 29/5 02:45 [774] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. Trace at Socket.addListener (events.js:252:17) at Socket.Readable.on (_stream_readable.js:673:33) 29/5 02:45 [779] - info: [app] Database connection closed. 29/5 02:45 [774] - info: [app] Database connection closed. at Socket.once (events.js:278:8) 29/5 02:45 [779] - info: [app] Web server closed to connections. 29/5 02:45 [774] - info: [app] Web server closed to connections. at Socket.unref (net.js:1013:10) 29/5 02:45 [779] - info: [app] Shutdown complete. 29/5 02:45 [774] - info: [app] Shutdown complete. at Connection.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/connection.js:453:23) at /home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:189:7 at Array.forEach (native) at Pool.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:182:15) at Server.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/topologies/server.js:1072:31) at Server.close (/home/wing/nodebb/node_modules/mongodb/lib/server.js:417:17) 29/5 02:45 [782] - info: [app] Database connection closed. 29/5 02:45 [782] - info: [app] Web server closed to connections. 29/5 02:45 [782] - info: [app] Shutdown complete. [cluster] Child Process (774) has exited (code: 0, signal: null) [cluster] Child Process (779) has exited (code: 0, signal: null) [cluster] Child Process (782) has exited (code: 0, signal: null)
  • HolyPhoenixH

    [Nodebb website] Cannot Mark All posts as read

    Bug Reports
    0 Votes
    2 Posts
    1k Views
    barisB

    Thanks for reporting fixed in https://github.com/NodeBB/NodeBB/commit/aa30973f0a628bd2de91741c483b2a23a28e913d

  • S

    When you update Nodebb to latest code,guest and normal user can't see the website.

    Bug Reports
    0 Votes
    8 Posts
    3k Views
    julianJ

    @song19891121 The permissions were refactored so that by default, if a category has no permissions checked (in the Access Control modal), nobody can access it.

    This is a departure from the previous behaviour, which was:

    Registered users can access and post Guests can access but cannot post

    Which was confusing for some.

    Long story shot

    The upgrade script should transparently convert your existing permissions properly, but clearly there are some bugs. When you upgrade, go through all of your categories and ensure the permissions are set correctly.

Copyright © 2023 NodeBB | Contributors