I like to use default and cyborg, especially in style, and the compatibility is very good now
All a sudden, despite having made no changes on my nodeBB 1.6.1 the front page is exhibiting weird behaviour on display.
If any one could lead me to what cause this and how to fix it, it be greatly appreciated
Ok things get returned to normal but I suspect the is some security at stake here.
Been the only admin I know that nothing get changed from the BO.
User settings was on allowing them to change their skin.
At some point the only scenario I can think of, it that some user action has invaded the default settings.
I have disabled user skin change.
@torn2 the sounds are loaded from an external CDN. It automatically loads the latest version.
Unfortunately some skins were released with the latest version being made for bootstrap 4.
But we're running version 1.6.1 and haven't upgraded and the skins worked fine. About two days ago they suddenly broke???
Changing the bootstrap url from "/latest" to "/3.3.7" in two places (src/client/account/settings.js and src/middleware/header.js) gave us an immediate fix to this problem.
And just random kudos for how easy it is to find and fix things in NodeBB. Definitely my favorite forum software!
Damn, I lost users because of this, first time I'm a little disappointed by NodeBB
Here is a quick fix for webmasters experiencing this persona skins issue
cd NodeBB-* sed -i 's#bootswatch/latest#bootswatch/3.3.7#g' public/src/client/account/settings.js src/middleware/header.js ./nodebb build ./nodebb restart
Hope this helps
Edit: Sorry I might have been a little rude here, NodeBB rules of course, keep up the great work
@pitaj Latest, 1.7.4
I'm using this script to update
cd NodeBB-1.X.X ./nodebb stop cd .. redis-cli save sudo cp /var/lib/redis/dump.rdb ~/dump-1.X.X.rdb wget https://github.com/NodeBB/NodeBB/archive/v1.X.Y.tar.gz tar czf backup-1.X.X.tar.gz NodeBB-1.X.X mv NodeBB-1.X.X NodeBB-1.X.Y tar xf v1.X.Y.tar.gz cd NodeBB-1.X.Y npm update ./nodebb upgrade or ./nodebb build ./nodebb start
but I would prefer to have just to
git pullof course ^^
@annihil this should work, but definitely back up the whole
nodebbfolder and your database first.
To achieve this, we're going to do the following steps:
- Initialize an empty git repository in the existing directory
- Add the Github repository as a new remote on this local git repo
- Fetch the data from the remote repo
- Ensure that the local repo is equal to the remote
- Switch to the correct branch locally
Okay, now here's the respective CLI commands:
$ git init $ git remote add origin https://github.com/nodebb/nodebb.git $ git fetch $ git reset --hard origin/v1.7.x $ git checkout v1.7.x
Hopefully that works for you. It certainly helps that you're already on latest v1.7.x.