Sudden Bizarre Error

Technical Support
  • Restarting NodeBB doesn't seem to help.

    2019-10-21T19:20:23.943Z [4567/16936] - error: /categories
    Failed to lookup view "header" in views directory "/var/www/html/community/build/public/templates" {"view":{"                                       defaultEngine":"tpl","ext":".tpl","name":"header","root":"/var/www/html/community/build/public/templates"},"s                                       tack":"Error: Failed to lookup view \"header\" in views directory \"/var/www/html/community/build/public/temp                                       lates\"\n    at Function.render (/var/www/html/community/node_modules/express/lib/application.js:580:17)\n                                           at /var/www/html/community/src/middleware/header.js:222:13\n    at nextTask (/var/www/html/community/node_mo                                       dules/async/dist/async.js:5324:14)\n    at next (/var/www/html/community/node_modules/async/dist/async.js:533                                       1:9)\n    at /var/www/html/community/node_modules/async/dist/async.js:969:16\n    at /var/www/html/community/                                       src/middleware/header.js:214:4\n    at /var/www/html/community/node_modules/async/dist/async.js:473:16\n    a                                       t next (/var/www/html/community/node_modules/async/dist/async.js:5329:29)\n    at /var/www/html/community/nod                                       e_modules/async/dist/async.js:969:16\n    at done (/var/www/html/community/src/plugins/hooks.js:95:5)"}
    Error: Failed to lookup view "header" in views directory "/var/www/html/community/build/public/templates"
        at Function.render (/var/www/html/community/node_modules/express/lib/application.js:580:17)
        at /var/www/html/community/src/middleware/header.js:222:13
        at nextTask (/var/www/html/community/node_modules/async/dist/async.js:5324:14)
        at next (/var/www/html/community/node_modules/async/dist/async.js:5331:9)
        at /var/www/html/community/node_modules/async/dist/async.js:969:16
        at /var/www/html/community/src/middleware/header.js:214:4
        at /var/www/html/community/node_modules/async/dist/async.js:473:16
        at next (/var/www/html/community/node_modules/async/dist/async.js:5329:29)
        at /var/www/html/community/node_modules/async/dist/async.js:969:16
        at done (/var/www/html/community/src/plugins/hooks.js:95:5)
    
  • Try running ./nodebb build and starting.

  • That seemed to work. Looks like there's a plugin causing the site to bug out.


Suggested Topics


  • Email test ssl error

    Solved Technical Support
    0 Votes
    2 Posts
    20 Views

    The error mysteriously disappeared and was replaced by an authentication error. I managed to have my Postmark account unlocked (btw, their support team was way much better than that of Sendgird, which still hasn't responded for 2 days since I requested till I am typing right now) and found that to use Postmark in Nodemailer you have to set the server api token as both the username and the password. This is quite counter intuitive, in my opinion.

    And I finally figured out that, the test email button works on your last saved settings, not what you are editing in the input boxes right now.

    So now Postmark is working. Thank God.

  • How to fix this error?

    Unsolved Technical Support
    0 Votes
    2 Posts
    103 Views

    @Peter-0 said in How to fix this error?:

    Time Zone: ""

    Seems to me that you didn't set a timezone on your os?

  • 0 Votes
    7 Posts
    1k Views

    I don't even know how to view my current version... Looked in the admin panel and on ssh I type ./nodebb --version or version and nothin.

    After that, I can establish whether I need any further upgrades or not but as it stands, I did a ./nodebb upgrade which was successful.

    I'm going to also have to check and see if I had used GitHub to get NodeBB to begin with, I can't remember if I did.

  • 0 Votes
    6 Posts
    2k Views

    @countach that's nothing to be worried about for now. It's something that needs to be taken care of on the theme's end. Post an issue on the theme's repository.

  • 0 Votes
    16 Posts
    6k Views

    This is fixed on master, thanks for reporting.