Migrating from SMF
-
@19eighties You would access the site with
http://u1kkea75fe43.19eighties.koding.io:4567
The first line (base URL) should be
http://u1kkea75fe43.19eighties.koding.io
, the defaults are fine for the rest of the options.You can do
sudo nano config.json
in your NodeBB folder to check what your settings are, they should look like this:{ "base_url": "http://u1kkea75fe43.19eighties.koding.io", "port": "4567", "secret": "random-string-of-characters", "bind_address": "0.0.0.0", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "", "database": "0" }, "bcrypt_rounds": 12, "upload_path": "/public/uploads", "use_port": true, "relative_path": "" }
Then once you've confirmed it's right, you can run ./nodebb start and visit the above URL with the port number included. If it's not loading, try running ./nodebb dev. Just to make sure you've not got any errors.
-
Thanks!
I have a couple more questions:
-
One thing I started looking into, was the importer plugin. I have it currently installed, when I run it, it looks like there is a pull-down for selecting which import to run, however, it does not populate with any options (FYI). Can I write the git address for the SMF plugin below?
-
Also wondering, is there a shoutbox plugin available?
-
How are layouts, CSS, elements customized?
-
-
@19eighties said:
- One thing I started looking into, was the importer plugin. I have it currently installed, when I run it, it looks like there is a pull-down for selecting which import to run, however, it does not populate with any options (FYI). Can I write the git address for the SMF plugin below?
Paging @bentael for this one.
- Also wondering, is there a shoutbox plugin available?
Yepp,
npm install nodebb-plugin-shoutbox
- How are layouts, CSS, elements customized?
In the ACP you can define custom CSS or custom javascript above the head. Alternatively you can fork a theme and make your changes that way.
Basically this forum uses Lavender which uses Vanilla as a fallback for any missing files.
-
I was tinkering a little more... Basically updating some of the plugins, which said were out of date, so I could play with the widgets. It seems like there is an issue though, in the console the
./nodebb dev
process is scrolling constantly and restarting, so it seems like it is stuck in a loop.`` 2014-11-17T21:35:00.412Z - info: Enabling 'trust proxy'
[cluster] Child Process (3917) listening for connections.
2014-11-17T21:35:00.499Z - info: [themes] Using theme nodebb-theme-lavender
2014-11-17T21:35:00.542Z - info: [plugins] Initializing plugins system
2014-11-17T21:35:00.544Z - info: Middlewares loaded.2014-11-17T21:35:00.550Z - warn: [plugins/nodebb-widget-essentials] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
2014-11-17T21:35:00.550Z - warn: [plugins/nodebb-widget-essentials] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-widget-essentials".2014-11-17T21:35:00.551Z - info: [plugins] Found 1 CSS file(s) for plugin nodebb-widget-essentials
2014-11-17T21:35:00.553Z - info: [plugins] Found 3 js file(s) for plugin nodebb-theme-lavender
2014-11-17T21:35:00.555Z - info: [plugins] Loaded plugin: nodebb-widget-essentials
2014-11-17T21:35:00.575Z - info: [plugins] Loaded plugin: nodebb-plugin-import
2014-11-17T21:35:00.576Z - info: [plugins] Loaded plugin: nodebb-theme-lavender
2014-11-17T21:35:00.580Z - error: TypeError: object is not a function
at Object.Widget.init (/home/19eighties/nodebb/node_modules/nodebb-widget-essentials/library.js:44:3)
at /home/19eighties/nodebb/src/plugins.js:489:23
at /home/19eighties/nodebb/node_modules/async/lib/async.js:125:13
at Array.forEach (native)
at _each (/home/19eighties/nodebb/node_modules/async/lib/async.js:46:24)
at Object.async.each (/home/19eighties/nodebb/node_modules/async/lib/async.js:124:9)
at Object.Plugins.fireHook (/home/19eighties/nodebb/src/plugins.js:487:12)
at Plugins.reloadRoutes (/home/19eighties/nodebb/src/plugins.js:135:11)
at /home/19eighties/nodebb/node_modules/async/lib/async.js:656:23
at fn (/home/19eighties/nodebb/node_modules/async/lib/async.js:641:34)
TypeError: object is not a function
at Object.Widget.init (/home/19eighties/nodebb/node_modules/nodebb-widget-essentials/library.js:44:3)
at /home/19eighties/nodebb/src/plugins.js:489:23
at /home/19eighties/nodebb/node_modules/async/lib/async.js:125:13
at Array.forEach (native)
at _each (/home/19eighties/nodebb/node_modules/async/lib/async.js:46:24)
at Object.async.each (/home/19eighties/nodebb/node_modules/async/lib/async.js:124:9)
at Object.Plugins.fireHook (/home/19eighties/nodebb/src/plugins.js:487:12)
at Plugins.reloadRoutes (/home/19eighties/nodebb/src/plugins.js:135:11)
at /home/19eighties/nodebb/node_modules/async/lib/async.js:656:23
at fn (/home/19eighties/nodebb/node_modules/async/lib/async.js:641:34)
2014-11-17T21:35:00.584Z - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
2014-11-17T21:35:00.584Z - 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/19eighties/nodebb/app.js:344:36)
at process.<anonymous> (/home/19eighties/nodebb/app.js:181:7)
at process.EventEmitter.emit (events.js:95:17)
at process._fatalException (node.js:272:26)
[cluster] Child Process (3917) has disconnected
[cluster] Child Process (3917) has exited (code: 7, signal: null)
[cluster] Spinning up another process... `` -
@19eighties What version of NodeBB are you running? There's a slight issue at the minute bridging the gap between 0.6.0s breaking changes, and maintaining support for 0.5.x branches. 0.5.x could ask you to currently update to a plugin that only works with 0.6.0.
-
@a_5mith Not sure now since I cannot get it started again. I did see some plugins that gave me a warning that they were not compatible with the version I had installed. I followed the guide you gave me earlier. I guess it was not the latest version.
Edit: v0.5.x according to the koding install guide.
-
@19eighties Ok, for 0.5.x.
npm i [email protected]
will get Widget Essentials working again. Depending on how many plugins you've updated, you may have to go through and drop down the versions of each of the plugins dependant on their supported version.A quicker method to get your NodeBB up and running again would be to run
./nodebb reset plugins
, which will temporarily disable all running plugins. However as widget essentials is slightly different, you'll need to run the above command. If you get any other errors after doing that, paste it here and I'll get you the correct versions.Alternatively you can find the plugin on Github, look at the commit history, and look for the commit that's before support for 0.6.0.
-
@19eighties Stable should be fine for production, 0.6.0 is still in development phase, so there's a few breaking issues, I'm running it on http://35hz.co.uk, but only because I'm brave. When 0.6.x is stable and people upgrade from 0.5.x, the whole plugin issue will be less of an issue. But it's quite difficult backporting these sorts of compatability so that plugins aren't updated when they shouldn't be. People will naturally see an update and do just that.
-
@a_5mith Nice landing page. I noticed when an image is uploaded for a category, it is not automatically re-sized to more appropriately fit the box.
I think it would take a while for me to get comfortable using this forum software as an admin. I like a lot of the features though.
-
@19eighties Define "banner". You can add an image to the category. But I doubt that's what you mean. You can also add widgets to category headers if that's your thing.
-
@19eighties v0.5.4 (aka v0.5.x) is stable, and ready to roll. v0.60 is the master branch on GitHub, and is actively being developed.
-
@19eighties said:
- One thing I started looking into, was the importer plugin. I have it currently installed, when I run it, it looks like there is a pull-down for selecting which import to run, however, it does not populate with any options (FYI). Can I write the git address for the SMF plugin below?
Sometimes npm api does not return anything to populate the list, will fix this soon - for now, you can just write
nodebb-plugin-import-smf
which will install the latest from the npm registry, if you want a specific fork or version, you can use the full git url, i.e.git://github.com/a5mith/nodebb-plugin-import-smf#master
, basically any valid repository urlAlso, if you install it once, or if you decide to manually clone it into the
node_modules
and you do not want the import plugin to touch it or try to install it again, there is an option"Skip Module Install"
which you can check to skip the install process, but you still have to leave the name of the module in the input field, i.e.nodebb-plugin-import-smf