3.0.0 Bug Report Thread

Bug Reports

Suggested Topics


  • 0 Votes
    6 Posts
    664 Views

    Excellent thanks chaps.

    I've just pulled down the latest code base and all seems to be working again.

    Calum

  • 0 Votes
    4 Posts
    3k Views

    The common causes for a session mismatch error are usually one of the following:

    1. Mis-configured URL parameter in your config.json file

    If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.

    2. Improper/malformed cookieDomain set in ACP

    Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:

    Cookie Domain setting

    If this is set, you'll want to revert the setting by editing your database directly:

    Redis: hdel config cookieDomain
    MongoDB: db.objects.update({ _key: "config" }, { $set: "cookieDomain": "" });

    3. Missing X-Forwarded-Proto header from nginx/apache

    If you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure property.

    In nginx, you will need to add the directive like so:

    location / { ... proxy_set_header X-Forwarded-Proto $scheme; ... }
  • 5 Votes
    13 Posts
    2k Views

    But lemmie tell you writing Javascript inside an HTML widget is a Pain In The Neck.

  • 1 Votes
    1 Posts
    909 Views

    If you are using filter:user.settings it will be renamed to filter:user.customSettings in 0.8.3.

    filter:user.settings and filter:user.getSettings are duplicates · Issue #3606 · NodeBB/NodeBB

    .... sort of. .settings is fired only in the /user/settings controller, while .getSettings is fired whenever user settings are called site-wide. However, both hooks alter user settings, and .settings additionally adds a new property call...

    favicon

    GitHub (github.com)

    closes #3606 · NodeBB/NodeBB@d96073d

    Node.js based forum software built for the modern web - closes #3606 · NodeBB/NodeBB@d96073d

    favicon

    GitHub (github.com)

  • 0 Votes
    19 Posts
    3k Views

    @julian

    ok, retried and it installed.
    but it's not launching.
    opening the log shows:

    info: * using themes stored in: /home/super/nodeBB/nodebb/node_modules info: NodeBB v0.4.3 Copyright (C) 2013-2014 DesignCreatePlay Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Fri May 16 2014 15:23:40 GMT+0200 (CEST) info: Initializing NodeBB v0.4.3 info: * using configuration stored in: /home/super/nodeBB/nodebb/config.json info: * using redis store at 127.0.0.1:6379 info: * using themes stored in: /home/super/nodeBB/nodebb/node_modules info: NodeBB v0.4.3 Copyright (C) 2013-2014 DesignCreatePlay Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Fri May 16 2014 15:23:40 GMT+0200 (CEST) info: Initializing NodeBB v0.4.3 info: * using configuration stored in: /home/super/nodeBB/nodebb/config.json info: * using redis store at 127.0.0.1:6379 info: * using themes stored in: /home/super/nodeBB/nodebb/node_modules info: NodeBB v0.4.3 Copyright (C) 2013-2014 DesignCreatePlay Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Fri May 16 2014 15:23:41 GMT+0200 (CEST) info: Initializing NodeBB v0.4.3 info: * using configuration stored in: /home/super/nodeBB/nodebb/config.json info: * using redis store at 127.0.0.1:6379 info: * using themes stored in: /home/super/nodeBB/nodebb/node_modules [loader] Experienced three start attempts in 10 seconds, most likely an error on startup. Halting.