• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Last pull from master - new topics are null

Scheduled Pinned Locked Moved Bug Reports
25 Posts 6 Posters 8.3k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Leonardo Galani
    wrote on last edited by
    #1

    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 šŸ™‚

    1 Reply Last reply
    0
  • nhl.plN Offline
    nhl.plN Offline
    nhl.pl
    wrote on last edited by nhl.pl
    #2

    It's worth to mention that MongoDB 3.0.2/3.1.1 and Redis 3.0.0 are already available.

    1 Reply Last reply
    1
  • L Offline
    L Offline
    Leonardo Galani
    wrote on last edited by
    #3

    Thanks..

    i wondering how to remove those /topic/something from my database....

    1 Reply Last reply
    0
  • nhl.plN Offline
    nhl.plN Offline
    nhl.pl
    wrote on last edited by
    #4

    You can use RockMongo to browse your DB and see how raw data looks.
    http://docs.mongodb.org/ecosystem/tools/administration-interfaces/

    1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #5

    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?

    1 Reply Last reply
    0
  • L Offline
    L Offline
    Leonardo Galani
    wrote on last edited by
    #6

    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... šŸ˜ž

    scottalanmillerS 1 Reply Last reply
    0
  • nhl.plN Offline
    nhl.plN Offline
    nhl.pl
    wrote on last edited by
    #7

    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.

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    wrote on last edited by
    #8

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

    Screen Shot 2015-05-27 at 3.41.09 AM.png

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

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    replied to Leonardo Galani on last edited by
    #9

    @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.

    1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #10

    @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.

    scottalanmillerS 1 Reply Last reply
    0
  • barisB Offline
    barisB Offline
    <baris> NodeBB
    wrote on last edited by
    #11

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

    scottalanmillerS 1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    replied to julian on last edited by
    #12

    @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

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    replied to <baris> on last edited by
    #13

    @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?

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Ali Gamers
    wrote on last edited by Ali
    #14

    Having same issue as well.
    MongoDB version: 3.0.2

    scottalanmillerS 1 Reply Last reply
    1
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    replied to Ali on last edited by
    #15

    @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.

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    wrote on last edited by
    #16

    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)

    1 Reply Last reply
    0
  • barisB Offline
    barisB Offline
    <baris> NodeBB
    wrote on last edited by
    #17

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

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    wrote on last edited by
    #18

    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.

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    wrote on last edited by
    #19

    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

    1 Reply Last reply
    0
  • scottalanmillerS Offline
    scottalanmillerS Offline
    scottalanmiller Community Rep
    wrote on last edited by
    #20

    /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

    1 Reply Last reply
    0

Copyright Ā© 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development