Categories drop-down empty after migration to 1.16.x

Technical Support
  • Hi Community,

    I've recently upgraded from 1.12.x to 1.16.x and I've done it first on a testing environment and, upon success, on production environment.

    Today, after a few days from the upgrade, I've realized that on the production instance the list of categories from category-drop down menu, is completely missing either on front-end (typical case when you want to move a thread) and on back-end (typical case when you want to set privileges).

    Production instance(left) Vs Test instance (Right)
    comparins_prod-test.jpg
    I've no clue what could be the case and how to get it fixed.

    Thanks, Riccardo


Suggested Topics


  • Upgrading from 1.19.5

    Unsolved Technical Support
    9
    0 Votes
    9 Posts
    198 Views

    Ah yes, it seems I overlooked that when I deactivated all the plugins and only reactivated the persona theme.

    Seems to be working to a fashion, just need to get some plugins I rely on updated.

  • 0 Votes
    2 Posts
    1k Views

    There are not hierarchical permissions in NodeBB. If you would like to see hierarchical permissions, you could open an issue on our Github page and request such a feature.

    I do believe we have a way of copying permissions between groups, so that could help you out in doing what you want.

  • 0 Votes
    4 Posts
    1k Views

    And solved. Thanks again @PitaJ

  • 1 Votes
    7 Posts
    2k Views

    Fixed in latest master, the labels were swapped, so "Access" was actually controlling "Create", and vice versa.

  • 0 Votes
    1 Posts
    2k Views

    I noticed that whenever I reload nodebb, I get error messages like this one in the log:

    31/7 23:47 [12036] - error: Error: Failed to lookup view "500" in views directory "/var/www/node/nodebb/public/templates" at EventEmitter.render (/var/www/node/nodebb/node_modules/express/lib/application.js:579:17) at ServerResponse.render (/var/www/node/nodebb/node_modules/express/lib/response.js:961:7) at ServerResponse.res.render (/var/www/node/nodebb/src/middleware/middleware.js:337:10) at /var/www/node/nodebb/src/routes/index.js:223:9 at /var/www/node/nodebb/src/middleware/middleware.js:192:12 at /var/www/node/nodebb/node_modules/async/lib/async.js:589:17 at done (/var/www/node/nodebb/node_modules/async/lib/async.js:126:15) at /var/www/node/nodebb/node_modules/async/lib/async.js:32:16 at /var/www/node/nodebb/node_modules/async/lib/async.js:586:21 at /var/www/node/nodebb/node_modules/templates.js/lib/templates.js:160:12 Error: Failed to lookup view "500" in views directory "/var/www/node/nodebb/public/templates" at EventEmitter.render (/var/www/node/nodebb/node_modules/express/lib/application.js:579:17) at ServerResponse.render (/var/www/node/nodebb/node_modules/express/lib/response.js:961:7) at ServerResponse.res.render (/var/www/node/nodebb/src/middleware/middleware.js:337:10) at /var/www/node/nodebb/src/routes/index.js:223:9 at /var/www/node/nodebb/src/middleware/middleware.js:192:12 at /var/www/node/nodebb/node_modules/async/lib/async.js:589:17 at done (/var/www/node/nodebb/node_modules/async/lib/async.js:126:15) at /var/www/node/nodebb/node_modules/async/lib/async.js:32:16 at /var/www/node/nodebb/node_modules/async/lib/async.js:586:21 at /var/www/node/nodebb/node_modules/templates.js/lib/templates.js:160:12

    I think it is users trying to access the page while reloading, but it made me wonder if there is a way to prevent this from happening? Also, I have currently three worker threads enabled. Shouldn't they be restarted successively so every request can be handled?