It's new in v1.12.x
if you don't like it. You can remove it in CSS
go to /admin/appearance/customise
add this
.composer .title-container .quick-search-results { display: none!important; }save and check if it's good.
Last pull from master - new topics are null
-
Last pull from master - new topics are coming null (http://domain.com.br/topic/null/tsttst)
mongodb version v2.6.9
Also i cant deleted those buggy topics.. any light.. i did a git pull to get last persona... got a bug instead
-
It's worth to mention that MongoDB 3.0.2/3.1.1 and Redis 3.0.0 are already available.
-
Thanks..
i wondering how to remove those /topic/something from my database....
-
You can use RockMongo to browse your DB and see how raw data looks.
http://docs.mongodb.org/ecosystem/tools/administration-interfaces/ -
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?
-
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...
-
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.
-
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/
-
@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.
-
@baris can confirm, but I don't think we require MongoDB 3.0. For that specific bug, please make sure your
mongodbmodule version is > 2.0.0. -
Yeah mongodb 3.0 is not a requirement, this might be caused by the nodejs module dependency.
-
-
@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?
-
Having same issue as well.
MongoDB version: 3.0.2 -
@Ali said:
Having same issue as well.
MongoDB version: 3.0.2Oh that's not good. I thought MongoDB 3 was going to be the fix.
-
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) -
What is your mongodb dependency version?
npm ls mongodbAlso postnpm ls connect-mongo -
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.
-
Broken version:
/opt/kae# npm ls mongodb
nodebb@0.7.0 /opt/kae
āāā¬ connect-mongo@0.4.1 extraneous
ā āāā mongodb@1.3.23
āāā mongodb@1.4.8 extraneousnpm ERR! extraneous: connect-mongo@0.4.1 /opt/kae/node_modules/connect-mongo
npm ERR! extraneous: mongodb@1.4.8 /opt/kae/node_modules/mongodb
npm ERR! not ok code 0 -
/opt/kae# npm ls connect-mongo
nodebb@0.7.0 /opt/kae
āāā connect-mongo@0.4.1 extraneousnpm ERR! extraneous: connect-mongo@0.4.1 /opt/kae/node_modules/connect-mongo
npm ERR! not ok code 0
