Skip to content

NodeBB v2.4.0

Solved General
  • Latest v2.4.0 I upgraded today.

    Always expect errors now it is a given…This is latest and do not know why. As always more chance of a reply with Sudonix. 🙂 Basically my custom page stopped working.

    0fda0c2d-cf1b-45f0-80b1-f247edca68ae-image.png

    2022-08-13T06:53:24.550Z [4567/48639] - error: GET /serverinfo
    Error: Failed to lookup view "serverinfo" in views directory "/home/smiley/nodebb/build/public/templates"
    at Function.render (/home/smiley/nodebb/node_modules/express/lib/application.js:597:17)
    at ServerResponse.render (/home/smiley/nodebb/node_modules/express/lib/response.js:1039:7)
    at /home/smiley/nodebb/src/middleware/render.js:107:11
    at new Promise (<anonymous>)
    at renderContent (/home/smiley/nodebb/src/middleware/render.js:106:10)
    at renderMethod (/home/smiley/nodebb/src/middleware/render.js:75:15)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async ServerResponse.renderOverride [as render] (/home/smiley/nodebb/src/middleware/render.js:96:5)
    2022-08-13T06:54:02.575Z [4567/48639] - error: GET /serverinfo
    Error: Failed to lookup view "serverinfo" in views directory "/home/smiley/nodebb/build/public/templates"
    at Function.render (/home/smiley/nodebb/node_modules/express/lib/application.js:597:17)
    at ServerResponse.render (/home/smiley/nodebb/node_modules/express/lib/response.js:1039:7)
    at /home/smiley/nodebb/src/middleware/render.js:107:11
    at new Promise (<anonymous>)
    at renderContent (/home/smiley/nodebb/src/middleware/render.js:106:10)
    at renderMethod (/home/smiley/nodebb/src/middleware/render.js:75:15)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async ServerResponse.renderOverride [as render] (/home/smiley/nodebb/src/middleware/render.js:96:5)
  • Latest v2.4.0 I upgraded today.

    Always expect errors now it is a given…This is latest and do not know why. As always more chance of a reply with Sudonix. 🙂 Basically my custom page stopped working.

    0fda0c2d-cf1b-45f0-80b1-f247edca68ae-image.png

    2022-08-13T06:53:24.550Z [4567/48639] - error: GET /serverinfo
    Error: Failed to lookup view "serverinfo" in views directory "/home/smiley/nodebb/build/public/templates"
        at Function.render (/home/smiley/nodebb/node_modules/express/lib/application.js:597:17)
        at ServerResponse.render (/home/smiley/nodebb/node_modules/express/lib/response.js:1039:7)
        at /home/smiley/nodebb/src/middleware/render.js:107:11
        at new Promise (<anonymous>)
        at renderContent (/home/smiley/nodebb/src/middleware/render.js:106:10)
        at renderMethod (/home/smiley/nodebb/src/middleware/render.js:75:15)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async ServerResponse.renderOverride [as render] (/home/smiley/nodebb/src/middleware/render.js:96:5)
    2022-08-13T06:54:02.575Z [4567/48639] - error: GET /serverinfo
    Error: Failed to lookup view "serverinfo" in views directory "/home/smiley/nodebb/build/public/templates"
        at Function.render (/home/smiley/nodebb/node_modules/express/lib/application.js:597:17)
        at ServerResponse.render (/home/smiley/nodebb/node_modules/express/lib/response.js:1039:7)
        at /home/smiley/nodebb/src/middleware/render.js:107:11
        at new Promise (<anonymous>)
        at renderContent (/home/smiley/nodebb/src/middleware/render.js:106:10)
        at renderMethod (/home/smiley/nodebb/src/middleware/render.js:75:15)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async ServerResponse.renderOverride [as render] (/home/smiley/nodebb/src/middleware/render.js:96:5)
    
    

    @Sampo2910 can you try removing the custom pages extension, rebuild, then reinstall and rebuild again ?

    I’ve had this happen to me before.

  • @Sampo2910 can you try removing the custom pages extension, rebuild, then reinstall and rebuild again ?

    I’ve had this happen to me before.

    @phenomlab As always…Thank you.

    Worked for me.

  • undefined phenomlab marked this topic as a question on 13 Aug 2022, 19:11
  • undefined phenomlab has marked this topic as solved on 13 Aug 2022, 19:11


1/3

13 Aug 2022, 12:28


Threaded Replies

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • 0 Votes
    4 Posts
    264 Views
    @Madchatthew said in TNG + Nodebb: you have to try and use duck tape and super glue to change something to make it do what you want it to do I couldn’t have put that better myself.
  • Nodebb design

    Solved General 11 Jul 2023, 10:13
    1 Votes
    2 Posts
    370 Views
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • 2 Votes
    6 Posts
    682 Views
    @Sampo2910 no problems. Happy to help. Just remember that this particular method isn’t the best in the sense that it may not get update notifications. The general recommendation here would be to move back to the official npm repo as soon as the GitHub version has been merged. For the meantime, it’ll work fine though.
  • 1 Votes
    4 Posts
    370 Views
    @Madchatthew No issues. Thanks
  • 2 Votes
    4 Posts
    517 Views
    @qwinter it’s workable I think, but not perfect - then again, unless you write a specific plugin to perform such a task, what is. As you pointed out, you have versioning of sorts with the historical access to reach post.
  • 2 Votes
    20 Posts
    2k Views
    @elhana-fine Yes that will happen of course if you still choose to restart the NGINX service after making a change and the test fails. The test on it’s own will state the error and the line number allowing you to fix that first
  • Forum not loading

    Solved Configure 6 Dec 2021, 14:26
    0 Votes
    27 Posts
    2k Views
    @phenomlab Brilliant!! Thanks ever so much!! Now I need to try pull in new members
  • 0 Votes
    1 Posts
    318 Views
    No one has replied