@sebastian-marinescu alternatively you could set defaultPlugins as an environment variable, then run ./nodebb setup [config json]. I'll re-add an actual option for passing in a set of default plugins.
Can't set up NodeBB from branch that's not master
Having issues doing a git pull for the vanilla theme alone, its asking for a repo to be added to the command, and adding 0.5 1 does nothing.
git clone https://github.com/NodeBB/nodebb-theme-vanilla.git
@a_5mith, thanks for that.
I'm trying to SSH from my S4 on a single bar of service. Can't browse github effectively
@Ted Wish I could do anything with my S4, I've had it repaired once already, still doesn't work. They're dragging their feet on replacing it.
@a_5mith, sorry to hear that. Mine's been pretty well without issue. I have a regional carrier though, so a small public arguement in store would guarantee an immediate replacement under my insurance.
./nodebb upgrade npm WARN package.json [email protected] No README data npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No repository field. [email protected] node_modules/uglify-js ├── [email protected] ├── [email protected] ├── [email protected] ([email protected]) └── [email protected] ([email protected]) npm WARN package.json [email protected] No README data npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No repository field. npm ERR! git Appears to be a git repo or submodule. npm ERR! git /root/nodebb/node_modules/nodebb-theme-vanilla npm ERR! git Refusing to remove it. Update manually, npm ERR! git or move it out of the way first. npm ERR! System Linux 3.13.0-24-generic npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "i" "nodebb-theme-vanilla" "nodebb-theme-lavender" "nodebb-widget-essentials" npm ERR! cwd /root/nodebb npm ERR! node -v v0.10.30 npm ERR! npm -v 1.4.21 npm ERR! path /root/nodebb/node_modules/nodebb-theme-vanilla npm ERR! code EISGIT npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /root/nodebb/npm-debug.log npm ERR! not ok code 0 info: NodeBB v0.5.0-2 Copyright (C) 2013-2014 NodeBB Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: Warning: Redis server does not require a password, but a password was supplied. info: Beginning database schema update info: [2014/2/19] Updating MOTD to use the HTML widget - skipped info: [2014/2/20] Adding Recent Replies, Active Users, and Moderator widgets to category sidebar - skipped info: [2014/2/20] Adding Forum Stats Widget to the Homepage Footer - skipped info: [2014/2/20] Updating Lavender MOTD - skipped info: [2014/2/20] Activating NodeBB Essential Widgets - skipped info: [2014/2/22] Added categories to sorted set - skipped info: [2014/3/18] Migrating Markdown settings to new configuration - skipped info: [2014/3/21] Removing gids and pruning groups - skipped info: [2014/3/31] Re-adding copyright message into global footer widget - skipped info: [2014/4/1] Moved home sidebar widgets into draft zone - skipped info: [2014/4/2] Moved deprecated vanilla footer widgets into draft zone - skipped info: [2014/5/13] Updating privilege settings - skipped info: [2014/5/16] Removing allowGuestPosting option - skipped info: [2014/5/16] Tags upgrade - skipped info: [2014/6/6] Topic upgrade - skipped info: [2014/6/17] Category post count upgrade - skipped info: [2014/7/23] Upgrading db dependencies - skipped info: [2014/7/24] Upgrading chats to sorted set - skipped info: [upgrade] Schema already up to date!
~/nodebb# ./nodebb dev Launching NodeBB in "development" mode. To run the production build of NodeBB, please use "forever". More Information: https://docs.nodebb.org/en/latest/running/index.html info: NodeBB v0.5.0-2 Copyright (C) 2013-2014 NodeBB Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Sat Aug 23 2014 12:19:42 GMT-0400 (EDT) info: Initializing NodeBB v0.5.0-2 info: * using configuration stored in: /root/nodebb/config.json info: * using redis store at info: * using themes stored in: /root/nodebb/node_modules info: Base Configuration OK. Warning: Redis server does not require a password, but a password was supplied. morgan deprecated morgan(options): use morgan("default", options) instead src/logger.js:128:22 morgan deprecated default format: use combined format src/logger.js:128:22 info: [notifications.init] Registering jobs. info: [user.startJobs] Registering User Jobs info: Enabling 'trust proxy' info: [plugins] Initializing plugins system info: [themes] Using theme nodebb-theme-vanilla info: Middlewares loaded. info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-mentions info: [plugins] Found 2 js file(s) for plugin nodebb-plugin-mentions info: [plugins] Found 1 CSS file(s) for plugin nodebb-widget-essentials info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-markdown info: [plugins] Loaded plugin: nodebb-plugin-mentions info: [plugins] Loaded plugin: nodebb-plugin-soundpack-default info: [plugins] Loaded plugin: nodebb-widget-essentials info: [plugins] Loaded plugin: nodebb-theme-vanilla info: [plugins] Loaded plugin: nodebb-plugin-markdown info: [plugins] Sorting hooks to fire in priority sequence info: [plugins] Plugins OK info: [meta/css] Minifying LESS/CSS info: [sounds] Sounds OK info: [themes] Compiling templates info: [themes] Successfully compiled templates. info: NodeBB attempting to listen on: info: NodeBB is now listening on: info: [meta/js] Successfully minified. info: [meta/js] Retrieved Mapping. info: [meta/js] Compilation complete
@a_5mith, looks like issue is still persisting. Even tried to redo setup, no avail. I did notice that Bootswatch themes seem to work with Mobile browsers when applied - sort of. The color is there at least.
Any other ideas?
crawls out of bed
groggily reads post
Oh, the buster problem. Usually the issue I found was a misplaced
;that messed up the code to the point that the buster wouldn't bust. I say usually because it's been a few different problems for me that has caused the buster not to bust in the past, and I've been able to solve it a couple of different ways:
- check and see if there are any misplaced colons or semicolons, or any misplacements in the CSS at all
- revert to a previous version and make the changes you did after that
- wave your wand three times and say the magic words, then restart your NodeBB and check again
Let me know if any of these work, especially the third option because I think it's the best.
@Tanner, there's no custom CSS, so it seems to be something from 0.5.1 of NodeBB.
Also, I'm gonna try my hand at a plugin you requested. We'll see how it works out.
@Ted It could still be a mixup in the CSS either way, even if there's no custom work or not. Could be a plugin, could be the theme, but that's been the major cause of my problems to date.
@Tanner, tee total fresh install, with no plugins. Must be something with the theme then.
I'll scan through in a bit and see if I can spot the issue. Since you've sounded off here, I'm going to try to do the same for you.
@Ted I'll also see if I can reproduce the issue with a fresh install and let you know what I come up with in terms of a solution.
So I looked through the recent commits to the 0.5.1 lavender theme and couldn't find a wayward colon, semi or not.
Is anyone else having this issue? If not, I'll just try again from the snapshot before NodeBB.
Our local dev environments are fine (although I do switch back and forth between
0.5.1)... Let me start from scratch later today and see.
@julian, I think I fixed this issue. I rolled back to a snapshot before I installed NodeBB and re-cloned the 0.5.1 branch and it installed without an issue and I have sweet, glorious CSS!