herp derp, just had to rerun setup and like magic it's back.
Purupuru
Posts
-
I broke it Endless loop now -
I broke it Endless loop nowI couldn't even reset the theme until I went back to 0.6.1 (it would just say nothing reset). I've gone back to 0.6.1, and reset theme to vanilla, but when ./nodebb start, now this:
jarvis@AVENGURZ:~/nodebbdir$ ./nodebb start Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output jarvis@AVENGURZ:~/nodebbdir$ url.js:107 throw new TypeError("Parameter 'url' must be a string, not " + typeof url) ^ TypeError: Parameter 'url' must be a string, not undefined at Url.parse (url.js:107:11) at Object.urlParse [as parse] (url.js:101:5) at getPorts (/home/jarvis/nodebbdir/loader.js:184:22) at Loader.start (/home/jarvis/nodebbdir/loader.js:141:13) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:610:21 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:249:17 at iterate (/home/jarvis/nodebbdir/node_modules/async/lib/async.js:149:13) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:160:25 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:251:21 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:615:34
Then it just stops and makes me cry
-
I broke it Endless loop nowI had upgraded to 0.6.1 successfully, but all my plugins didn't make it, so I tried to go back to 0.5.7 (it seemed like a good idea at the time) and it said nope. I can't even get it to resolve, gives connection refused error.
It just loops stuff like this over and over again:
Clustering enabled: Spinning up 1 process(es). 2015-05-07T19:16:43.530Z - info: Time: Thu May 07 2015 15:16:43 GMT-0400 (EDT) 2015-05-07T19:16:43.536Z - info: Initializing NodeBB v0.5.7 2015-05-07T19:16:43.536Z - info: * using configuration stored in: /home/jarvis/nodebbdir/config.json 2015-05-07T19:16:43.537Z - info: * using redis store at 127.0.0.1:6379 2015-05-07T19:16:43.537Z - info: * using themes stored in: /home/jarvis/nodebbdir/node_modules 2015-05-07T19:16:44.632Z - info: [notifications.init] Registering jobs. 2015-05-07T19:16:44.636Z - info: [user.startJobs] Registering User Jobs 2015-05-07T19:16:44.638Z - info: Enabling 'trust proxy' [cluster] Child Process (25352) listening for connections. 2015-05-07T19:16:44.771Z - info: [themes] Using theme nodebb-theme-dark-rectangles 2015-05-07T19:16:44.774Z - error: TypeError: Cannot read property 'id' of undefined at Object.Meta.themes.setPath (/home/jarvis/nodebbdir/src/meta/themes.js:113:59) at routeCurrentTheme (/home/jarvis/nodebbdir/src/middleware/index.js:45:14) at module.exports (/home/jarvis/nodebbdir/src/middleware/index.js:110:2) at require.exec.cwd (/home/jarvis/nodebbdir/src/webserver.js:62:16) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:592:17 at done (/home/jarvis/nodebbdir/node_modules/async/lib/async.js:135:19) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:32:16 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:589:21 at /home/jarvis/nodebbdir/src/meta/themes.js:61:6 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:254:17 TypeError: Cannot read property 'id' of undefined at Object.Meta.themes.setPath (/home/jarvis/nodebbdir/src/meta/themes.js:113:59) at routeCurrentTheme (/home/jarvis/nodebbdir/src/middleware/index.js:45:14) at module.exports (/home/jarvis/nodebbdir/src/middleware/index.js:110:2) at require.exec.cwd (/home/jarvis/nodebbdir/src/webserver.js:62:16) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:592:17 at done (/home/jarvis/nodebbdir/node_modules/async/lib/async.js:135:19) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:32:16 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:589:21 at /home/jarvis/nodebbdir/src/meta/themes.js:61:6 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:254:17 2015-05-07T19:16:44.777Z - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 2015-05-07T19:16:44.778Z - info: [app] Database connection closed. net.js:1236 throw new Error('Not running'); ^ Error: Not running at Server.close (net.js:1236:11) at shutdown (/home/jarvis/nodebbdir/app.js:344:36) at process.<anonymous> (/home/jarvis/nodebbdir/app.js:181:7) at process.emit (events.js:95:17) at process._fatalException (node.js:272:26) [cluster] Child Process (25352) has disconnected [cluster] Child Process (25352) has exited (code: 7, signal: null) [cluster] Spinning up another process... 2015-05-07T19:16:44.943Z - info: Time: Thu May 07 2015 15:16:44 GMT-0400 (EDT) 2015-05-07T19:16:44.946Z - info: Initializing NodeBB v0.5.7 2015-05-07T19:16:44.947Z - info: * using configuration stored in: /home/jarvis/nodebbdir/config.json 2015-05-07T19:16:44.947Z - info: * using redis store at 127.0.0.1:6379 2015-05-07T19:16:44.947Z - info: * using themes stored in: /home/jarvis/nodebbdir/node_modules 2015-05-07T19:16:46.010Z - info: [notifications.init] Registering jobs. 2015-05-07T19:16:46.013Z - info: [user.startJobs] Registering User Jobs 2015-05-07T19:16:46.016Z - info: Enabling 'trust proxy' [cluster] Child Process (25360) listening for connections. 2015-05-07T19:16:46.150Z - info: [themes] Using theme nodebb-theme-dark-rectangles 2015-05-07T19:16:46.154Z - error: TypeError: Cannot read property 'id' of undefined at Object.Meta.themes.setPath (/home/jarvis/nodebbdir/src/meta/themes.js:113:59) at routeCurrentTheme (/home/jarvis/nodebbdir/src/middleware/index.js:45:14) at module.exports (/home/jarvis/nodebbdir/src/middleware/index.js:110:2) at require.exec.cwd (/home/jarvis/nodebbdir/src/webserver.js:62:16) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:592:17 at done (/home/jarvis/nodebbdir/node_modules/async/lib/async.js:135:19) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:32:16 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:589:21 at /home/jarvis/nodebbdir/src/meta/themes.js:61:6 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:254:17 TypeError: Cannot read property 'id' of undefined at Object.Meta.themes.setPath (/home/jarvis/nodebbdir/src/meta/themes.js:113:59) at routeCurrentTheme (/home/jarvis/nodebbdir/src/middleware/index.js:45:14) at module.exports (/home/jarvis/nodebbdir/src/middleware/index.js:110:2) at require.exec.cwd (/home/jarvis/nodebbdir/src/webserver.js:62:16) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:592:17 at done (/home/jarvis/nodebbdir/node_modules/async/lib/async.js:135:19) at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:32:16 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:589:21 at /home/jarvis/nodebbdir/src/meta/themes.js:61:6 at /home/jarvis/nodebbdir/node_modules/async/lib/async.js:254:17 2015-05-07T19:16:46.157Z - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 2015-05-07T19:16:46.157Z - info: [app] Database connection closed.
Did I break it forever?
I see some errors calling the theme nodebb-theme-dark-rectangles, but I had removed it. So is it just looping because herp derp no theme set at all anymore?
-
[Solved] Emojis won't parse to image following full reset@a_5mith That did it, thank you!!
-
[Solved] Emojis won't parse to image following full resetUggghhh, I can't get any emoji plugin to work on my NodeBB install. They don't even parse to a broken image, they just stay as the text that was originally entered in editor, draft, and published post. The autocomplete box shows up fine, the big text area displays them all fine. The text just stays text. I had some trouble with a SSO and ended up not being able to login at all, so at one point, I did a full reset of everything. So maybe I forgot to turn back on some other plugin that is default to on in a fresh install?
I've tried every emoji plugin, none of them work, all on, all but one off, removing them all, putting just the extended, deleting nodebb.min.js. Turning off, uninstalling, re-installing, re-turning on. I don't get any errors (but could very well be looking in completely wrong place, I'm noob, so I'm looking through Firebug, running ./nodebb log, looking at npm-debug).
Have updated, run in developer and forever mode, changed theme, restart x 100, running around like headless chicken, no results yet.
Where else to look for a potential trouble maker?