NodeBB upgrades became worse since 0.7

pichalite

@julian It was actually 500 not 503.

 - error:  Error: Failed to lookup view "500" in views directory "/home/pichalite/nodebb/public/templates"
    at EventEmitter.render (/home/pichalite/nodebb/node_modules/express/lib/application.js:579:17)
    at ServerResponse.render (/home/pichalite/nodebb/node_modules/express/lib/response.js:961:7)
    at ServerResponse.res.render (/home/pichalite/nodebb/src/middleware/middleware.js:337:10)
    at /home/pichalite/nodebb/src/routes/index.js:223:9
    at /home/pichalite/nodebb/src/middleware/middleware.js:192:12
    at /home/pichalite/nodebb/node_modules/async/lib/async.js:589:17
    at done (/home/pichalite/nodebb/node_modules/async/lib/async.js:126:15)
    at /home/pichalite/nodebb/node_modules/async/lib/async.js:32:16
    at /home/pichalite/nodebb/node_modules/async/lib/async.js:586:21
    at EventEmitter.render (/home/pichalite/nodebb/node_modules/express/lib/application.js:581:14)
Error: Failed to lookup view "500" in views directory "/home/pichalite/nodebb/public/templates"

I reset the theme to vanilla too after I got this error to eliminate the possibility of custom theme error.

pichalite

@pichalite the composer has a bug. it does not scroll when I am typing a long message, the page scrolls instead. The composer starts scrolling after it reaches the end of the page.

julian

@pichalite Did you update your theme to specify the proper base theme? https://community.nodebb.org/topic/6098/on-changing-the-default-theme-to-persona

pichalite

@julian I ran ./nodebb -reset -t to eliminate the theme issue and it was reset to vanilla. still got the error.

julian

The error suggests the themes could not compile for whatever reason. Were there any errors on startup?

pichalite

@julian no errors during startup

julian

Plugins reset as well? If this were a core issue, we'd be seeing problems on our builds as well.

Move out your node_modules/ folder and run npm i again.

pichalite

@julian deleted the complete NodeBB folder and set it up. got it working.

Don't have too many plugins installed. In addition to the default ones I have sso plugins for Facebook, google and twitter and the rss plugin that's it.

julian

@pichalite Glad it's working again Seems it was npm's failing to install dependencies correctly?

Scuzz

We have found the upgrade process to fail nearly every time we have ran it.
I usually find a clean install with a DB backup to be the best process when changing versions.

chrismccoy

i tried upgrading using nodebb upgrade, it still shows 0.7.1, its not a git repo, so i cant do a fetch and checkout

julian

@chrismccoy ./nodebb upgrade does not download new code for you. You need to do that yourself

Please check out the "Upgrading NodeBB" page in the documentation

d3athwarrior

Even I was having trouble installing the update using the method listed in the docs.
I did a little searching and found @julian had mentioned a step of installing dependencies after the fetch, etc and prior to running ./nodebb upgrade somewhere in this forum as a reply to a previous update issue.

He had asekd to run npm i to install dependencies and that is what is working for me. I used it to update from v0.7.0.0 to v0.7.1.0 and also to v0.7.2.0.

kps

@julian said:

Move out your node_modules/ folder and run npm i again.

@julian
The composer is not working correctly, on scrolling the page scrolls but not the composer

julian

@kps Default composer on desktop, or mobile?

kps

@julian Desktop

Also I keep getting this warning "warn: [plugins/nodebb-theme-persona] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p nodebb-theme-persona"

Why should that happen ? I havent installed any other theme

Robert

@kps From what I know its basically a warning that the theme/plugin doesn't have the proper version for the current NodeBB version.

scottalanmiller

@pichalite said:

Every time I do an upgrade it does not go well. There is always some kind of error even though I am following the upgrade process from the docs.

Same here. Haven't had one work yet, actually. Not since 0.3 I think.