Last pull from master - new topics are null

[julian]

Hm.. it sounds like the slug is getting saved as "null" instead.

Quite weird, I don't know how we can reproduce it on our end. Can you let usknow git hash and theme versions?

[Leonardo Galani]

It happend when i did a pull from 0.7 and was using mongo 2.6.9... all new posts were breaking .. then @nhl-pl told to move to mongo 3.. and it all worked fine BUT those "ghosts" threads still there.. cant find them on topics and posts collections...

[nhl.pl]

Could you please post a screenshot, logs/errors or link to your forums (via chat)?

Nulled topics sounds like topics without a first post or deleted topics which can be recovered.

[scottalanmiller]

Just updated a community to 0.7.0 and am getting this too now. Any new topic creation just gives this...

This is happening at http://community.kiddingaroundeurope.com/

[scottalanmiller]

@Leonardo-Galani so is the "official" process to just go to MongoDB 3? I want to update but we have several communities sharing the platform and it isn't casual to just update the backend behind them all.

[julian]

@baris can confirm, but I don't think we require MongoDB 3.0. For that specific bug, please make sure your mongodb module version is > 2.0.0.

[baris]

Yeah mongodb 3.0 is not a requirement, this might be caused by the nodejs module dependency.

[scottalanmiller]

@julian said:

@baris can confirm, but I don't think we require MongoDB 3.0. For that specific bug, please make sure your mongodb module version is > 2.0.0.

We are on 2.6.5

[scottalanmiller]

@baris said:

Yeah mongodb 3.0 is not a requirement, this might be caused by the nodejs module dependency.

Any guess what one that might be? Want to take a peek at the system?

[Ali]

Having same issue as well.
MongoDB version: 3.0.2

[scottalanmiller]

@Ali said:

Having same issue as well.
MongoDB version: 3.0.2

Oh that's not good. I thought MongoDB 3 was going to be the fix.

[scottalanmiller]

I tried updating the plugins and....

Error: Failed to lookup view "500" in views directory "/opt/kae/public/templates"
at EventEmitter.app.render (/opt/kae/node_modules/express/lib/application.js:555:17)
at ServerResponse.res.render (/opt/kae/node_modules/express/lib/response.js:938:7)
at ServerResponse.res.render (/opt/kae/src/middleware/middleware.js:324:10)
at /opt/kae/src/routes/index.js:227:9
at /opt/kae/src/middleware/middleware.js:181:12
at /opt/kae/node_modules/async/lib/async.js:589:17
at done (/opt/kae/node_modules/async/lib/async.js:126:15)
at /opt/kae/node_modules/async/lib/async.js:32:16
at /opt/kae/node_modules/async/lib/async.js:586:21
at EventEmitter.app.render (/opt/kae/node_modules/express/lib/application.js:557:14)

[baris]

What is your mongodb dependency version? npm ls mongodb Also post npm ls connect-mongo

[scottalanmiller]

I just did a full, fresh install of NodeBB and was able to fix things that way. Not sure what was wrong, but that addressed both issues.

[scottalanmiller]

Broken version:

/opt/kae# npm ls mongodb
[email protected] /opt/kae
├─┬ [email protected] extraneous
│ └── [email protected]
└── [email protected] extraneous

npm ERR! extraneous: [email protected] /opt/kae/node_modules/connect-mongo
npm ERR! extraneous: [email protected] /opt/kae/node_modules/mongodb
npm ERR! not ok code 0

[scottalanmiller]

/opt/kae# npm ls connect-mongo
[email protected] /opt/kae
└── [email protected] extraneous

npm ERR! extraneous: [email protected] /opt/kae/node_modules/connect-mongo
npm ERR! not ok code 0

[baris]

Yeah nodebb 0.7.0 expects the mongodb dependency to be 2.0.0+ So if you do npm ls mongodb in the fresh install it will report it as 2.0.x.

[scottalanmiller]

@baris said:

Yeah nodebb 0.7.0 expects the mongodb dependency to be 2.0.0+ So if you do npm ls mongodb in the fresh install it will report it as 2.0.x.

Thanks. Good to know.

[scottalanmiller]

Now that that is fixed, how to delete the dead thread?

http://community.kiddingaroundeurope.com/topic/null/testing-new-posts

[baris]

You will have to remove it from the database manually.

db.objects.remove({_key: "topic:null"}); //remove object
db.objects.remove({_key: "topics:recent", value: null}); //remove from recent
db.objects.remove({_key: "cid:1:tids", value: null}); //remove from category
db.objects.remove({_key: "uid:3:topics", value: null}); //remove from user

I picked the category id and user id from the api return at http://community.kiddingaroundeurope.com/api/recent