Thanks a lot @MJ.

Works fine!

@pitaj Thanks! With node v8.7.0 and npm v5.4.2, I was able to run ./nodebb upgrade and now I'm a proud member of the nodebb v1.7.4 club.

If I've understood things correctly, you have to activate the emoji-extended plugin, then the emoji-static plugin.

Once you restart your Nodebb, you should seen under Plugins > an emoji static option.

There you'll find a help file to tell you how to set up your own pack.

You have to create an index.json file.

Nevertheless, I'm trying it out now, but I can get it to work...

Finally made it from v0.6.0 to v1.4.1

This was my upgrade route (hosted on DigitalOcean and with a mongo database - shell 2.6.7, node v0.10.38)

*v0.6 to v0.6.1
git fetch
git reset --hard origin/v0.6.x
git describe --tags
./nodebb upgrade

*v0.6.1 to v0.7.0
git checkout v0.7.0
./nodebb upgrade

npm install touch
npm install minimist
npm install colors

*v0.7.0 to v0.7.3
git reset --hard origin/v0.7.x 
git describe --tags
./nodebb upgrade

node app --upgrade

*install nvm
curl https://raw.githubusercontent.com/creationix/nvm/v0.11.1/install.sh | bash
*Restart terminal
nvm install v0.10.39

* Change index.js in /root/"yourfoldername"/node_modules/connect-mongo from
*module.exports = require('./src');
*to
*module.exports = require('connect-mongo/es5');

*edit /etc/mongod.conf, to uncomment auth = true line 

service mongod restart

mongo
use admin
db.createUser({user: "adminname", pwd: "yourpassword", roles: ["readWrite"]})

use *name of the db where nodebb is installed*
db.updateUser( "adminname",
               {
                 roles : [
                           { role : "dbAdmin", db : "*name of the db where nodebb is installed*"  },
                           { role : "readWrite", db : "*name of the db where nodebb is installed*"  }
                         ]
                }
             )

./nodebb upgrade
./nodebb start
./nodebb stop

*v0.7.3 to v0.8.x
git checkout v0.8.x
git pull
./nodebb upgrade

./nodebb start
./nodebb stop

*v0.8.2 to v0.9.x
git checkout v0.9.x
git pull
./nodebb upgrade

./nodebb start
./nodebb stop

*v0.9.4 to v1.4.1
git checkout v1.x.x
git pull

nvm install v6.2.1
nvm use v6.2.1

./nodebb upgrade

*edit /etc/mongod.conf, to uncomment noauth=true line 

This should help to avoid any issue with mmmagic, kerberos, bluebird and the key_1_value_-1 already exist error.

Et voilà !

Thanks again for your help Julian !

I believe that if you go in your profile in the set up page, the first box and option of that page is to force links to open in a new tab.
It would be nice to set up that option as default from the admin panel, but for now that works well.

Hi @jimmyc2018

I had the same issue once upgrading my nodebb installation from v1.4.2 to v1.5.1
The trick that worked out for me was to remplace the ip address in the "url" segment by my domain name in the config.json file.

Have you tried that out?

Check out this topic https://community.nodebb.org/topic/11324/error-listen-eaddrinuse-0-0-0-0-4800-looks-like-your-connection-to-nodebb-was-lost-please-wait-while-we-try-to-reconnect/9

changing for example,

"url": "http://localhost:4800", or "http://124.129.xxx.36:4800"

to

"url": "http://www.yourdomainname.com",

@NoduleJS I believe if you add this in your control panel in the CSS custom section, your .gifs should show up fine.

.emoji-customizations {
    height: 100%;
}

@yariplus You're right sorry! I checked yesterday quickly on my nodebb set-up and didn't think I had activated any special plugin for that. But after double checking, you're right it's the center align plugin that allows me to do this.

https://github.com/Stonebound/nodebb-plugin-align-center#readme

@JsonHive sorry for not being more clear at first.

And if you need alternatives

Installer NodeBB sur Ubuntu 16.04 server FR

@NoduleJS Yes, I believe you can.
If you use this plugin: https://github.com/NodeBB/nodebb-plugin-emoji#readme
Once installed, you'll have access in your control panel to options in order to set up your own emoticons.
I've added only .gifs and then a simple CSS rule to render their layout does the trick.

Excellent news! Keep up the good work.
“To Infinity and beyond”!

And if you need alternatives

Installer NodeBB sur Ubuntu 16.04 server FR

Thanks a lot @PitaJ and @baris for your help. Everything looks fine.

@PitaJ Did a new setup with database1, created database 2, did a mongorestore on database 2, changed the config.json to switch to database2 and now I'm trying to run ./nodebb setup but I get the following message Index with name: _key_1_value_-1 already exists with different options

 MongoError: Index with name: _key_1_value_-1 already exists with different options
    at /var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:598:61
    at authenticateStragglers (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:516:16)
    at Connection.messageHandler (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:552:5)
    at emitMessageHandler (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:309:10)
    at Socket.<anonymous> (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:452:17)
    at Socket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:287:12)
    at readableAddChunk (_stream_readable.js:268:11)
    at Socket.Readable.push (_stream_readable.js:223:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

@PitaJ ok I see what you mean.
I followed this https://www.rosehosting.com/blog/how-to-install-nodebb-on-ubuntu-18-04/
I created a new database on this new setup when everything was up and running, I did the mongorestore into that new database then did a ./nodebb setup and then proceed with the update to v1.12.2.
I tried to set up a new nodeBB with a regular database, dump the old one into another database and do the switch in the config.json then.

@PitaJ Hi PitaJ, I'm afraid that I don't have anymore the original Nodebb setup. Before I was centOS and Mongo and with a nodeBB on v1.10.1.
Now I started a new droplet on DigitalOcean with Ubuntu and Mongo. I only have my Mongo dump left for my old setup.
So to answer your question this is a mongorestore in a new database.

@baris you're the man! Thanks so much for taking the time and your help.

This is the result on my snapsnot for my fresh install of nodebb v1.10.1 and with only the mongorestore on it.
Not better, I'm afraid...

> db.objects.findOne({_key: "global"});
{
        "_id" : ObjectId("5dd298e8eb7500a3dd086e72"),
        "_key" : "global",
        "nextEid" : 84,
        "nextCid" : 4,
        "nextUid" : 1,
        "userCount" : 1,
        "nextTid" : 1,
        "topicCount" : 0,
        "nextPid" : 1,
        "postCount" : -1,
        "uniqueIPCount" : 11
}

@baris My highest ID as category was 17, and when I created a new one, the ID was 11. So I created fake categories to get up to number 18 and the category was finally empty when I created it. But as soon as I posted a new topic inside, old posts where linked to this first new post.
When I did the mongorestore should I have dropped the existing database (it was empty and only had the admin user account)?

Here is what I get

> db.objects.findOne({_key: "global"});
{
        "_id" : ObjectId("5dd298e8eb7500a3dd086e72"),
        "_key" : "global",
        "nextEid" : 202,
        "nextCid" : 18,
        "nextUid" : 1,
        "userCount" : 1,
        "nextTid" : 18,
        "topicCount" : 15,
        "nextPid" : 24,
        "postCount" : 3574,
        "uniqueIPCount" : 16,
        "nextNsEmbedRule" : 7,
        "nextPollId" : 1
}

@baris Thanks a lot for your idea. I'll try to find some time this afternoon to see if I can dig out something useful along the lines you've suggested. I'll keep the topic updated with my progress.

Hi @baris thanks for your help.

It's very strange, if I create a new category, it will either take the spot of an existing category with all the topics existing beforehand now linked to this new category.

Or I can create a new category, create a topic inside and end up having the 19 old messages linked to my first post bug.

This weird behaviour happens when I create a new topic in an existing category or a new one. If I reply to an existing thread, everything works fine.

I have the impression that categories ID are all messed up. Sometimes when creating a new category it will have a cover image from an older version of my forum.

Here's all the information I can gather:

• Database Setup

https://i.imgur.com/ncwoStz.png

• The bug in motion

https://gifyu.com/image/vday

Regarding your /api/topic/ request

• here's the JSON file for the topic created on the gif https://api.myjson.com/bins/1gydvy

Thanks again!