problem with user profile display.

Bug Reports
  • When visiting a profile we have an error. I guess it's related to the fact I upgraded to 0.6.1dev for testing the socket problem and moved back to 0.6.0 as my theme was broken on 0.6.1dev.
    The console output.

    21/1 15:20 [30900] - error: /api/user/juuka
     Error: WRONGTYPE Operation against a key holding the wrong kind of value
        at ReplyParser.<anonymous> (/home/esiao/forum/node_modules/redis/index.js:305:31)
        at ReplyParser.EventEmitter.emit (events.js:95:17)
        at ReplyParser.send_error (/home/esiao/forum/node_modules/redis/lib/parser/javascript.js:296:10)
        at ReplyParser.execute (/home/esiao/forum/node_modules/redis/lib/parser/javascript.js:181:22)
        at RedisClient.on_data (/home/esiao/forum/node_modules/redis/index.js:534:27)
        at Socket.<anonymous> (/home/esiao/forum/node_modules/redis/index.js:91:14)
        at Socket.EventEmitter.emit (events.js:95:17)
        at Socket.<anonymous> (_stream_readable.js:746:14)
        at Socket.EventEmitter.emit (events.js:92:17)
        at emitReadable_ (_stream_readable.js:408:10)
    21/1 15:20 [30900] - error: /api/user/vaan
     Error: WRONGTYPE Operation against a key holding the wrong kind of value
        at ReplyParser.<anonymous> (/home/esiao/forum/node_modules/redis/index.js:305:31)
        at ReplyParser.EventEmitter.emit (events.js:95:17)
        at ReplyParser.send_error (/home/esiao/forum/node_modules/redis/lib/parser/javascript.js:296:10)
        at ReplyParser.execute (/home/esiao/forum/node_modules/redis/lib/parser/javascript.js:181:22)
        at RedisClient.on_data (/home/esiao/forum/node_modules/redis/index.js:534:27)
        at Socket.<anonymous> (/home/esiao/forum/node_modules/redis/index.js:91:14)
        at Socket.EventEmitter.emit (events.js:95:17)
        at Socket.<anonymous> (_stream_readable.js:746:14)
        at Socket.EventEmitter.emit (events.js:92:17)
        at emitReadable_ (_stream_readable.js:408:10)
    
  • Yeah going back versions is not supported unless you have a db backup from the prior version.

    What is broken on your theme when you use 0.6.1

  • @baris The js but I just need to change 2 or 3 things and it will work again. I have a typo in package.json that is not detected in 0.6.0 I think it's because of the empty keywords.
    Do the 0.6.0 plugins are compatible with 0.6.1dev ?

  • Did they same thing and have the same issue...

  • Also have an issue where iphone users on any browser are having issues.


Suggested Topics


  • 2 Votes
    4 Posts
    338 Views

    @jksh What a bug, thanks for reporting!

  • 0 Votes
    15 Posts
    9k Views

    @julian said:

    @priapo Keep in mind putting a socket.io section in config.json doesn't do anything 😄

    We had just talked about this configuration option short time ago in the issue 😄 so obviously it does affect. But "transports": ["polling","websocket"] is now the Standard.

    @priapo if you can't use the websockets you can set also "transports": ["polling"], then you will only get the failures for the long polling request which throws errors.

    I just tested by connecting directly without any proxy before NodeBB. The timeout disappears.

    So one failure source is that the timeout is higher than what is allowed by the proxy e.g. cloudflare. So an option to adjust the timeout would be great!

    The failure throwing which are left now are:

    GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766084670-12&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766094756-13&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766096635-23&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766106720-24&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766108697-34&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766118775-35&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766120692-45&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766130783-46&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)
  • 0 Votes
    8 Posts
    6k Views

    I figured out my issue...

    MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

  • 2 Votes
    13 Posts
    5k Views

    @baris Thanks Baris, that showed the issue, was using // as the URI instead of https which was incorrect apparently. 😆

    Plugin updated to 1.1.5 for 0.6.0 of NodeBB.

  • 0.5.1 installation problem...

    Bug Reports
    0 Votes
    3 Posts
    1k Views

    @julian thanks. I can login as admin now after git pull today.

    I understand the sub-category is still working in progress. I am just wondering
    how it will looks like: for example: I have category hierarchy like: US --> California --> SF Bay area; and US --> California --> San Diego area.

    when user navigate to California category page, will the user see all the subcategories link list (like "SF Bay area", and "San Diego area") , and also see the posts to "Californa" category ?

    when user do a new post, when user select categories, will the drop-down menu show some tree-like hierarchy to allow user select a specific sub-category?

    seems it introduces a lot of complexity to the code base. we really appreciate you guys' great work to make this feature working.