Adding javascript in the footer

Technical Support

Suggested Topics


  • 0 Votes
    5 Posts
    262 Views

    @baris Thank you. Very valuable feedback. Ought the theme quickstart to be kept in sync with the plugin quickstart?

  • 0 Votes
    3 Posts
    327 Views

    Sorry for the very late reply @julian !
    yes I was rebuilding the templates, it was a misconception by my side, i thought that I could change on the ACP the header and footer and it will affect to the other templates, but i was importing the src template.

    Now i'll try to override the e-mail templates using my child theme, is it just create a e-mail folder inside my templates folder?
    i've seen that this has been asked before, but why can't you change the e-mail subject from the ACP? i had to modify it on the src template.

    Thank you very much!!

  • 0 Votes
    7 Posts
    2k Views

    @julian I found this after re-reading the NodeBB NGINX configuration docs

    nginx must be on version 1.4.x to properly support websockets. Debian/Ubuntu uses 1.2, although it will work there will be a reduction in functionality.

    Previously, in the same doc:

    NGINX version v1.3.13 or greater

    I'm not sure if that is just a sign of an outdated doc, or if there is actually some type of incompatibility (which apparently doesn't surface everywhere). All I know is that by reverting to 1.4.x, all functionality was restored.

  • 0 Votes
    1 Posts
    658 Views

    I had this problem going from v0.9.4 -> v1.0.0 and now still have it going from v0.9.4 -> v1.0.1 but now I have additional information about it. See here for my original post.

    The tl;dr is

    $ ./nodebb upgrade 1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK 3. Updating NodeBB data store schema... 18/3 15:15 [1511] - info: Beginning database schema update 18/3 15:15 [1511] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped 18/3 15:15 [1511] - info: [2015/11/06] Gravatar removal skipped 18/3 15:15 [1511] - info: [2015/12/15] Upgrading chats 18/3 15:15 [1511] - info: adding message 1 to new roomID 1 18/3 15:15 [1511] - info: adding message 2 to existing roomID 2 18/3 15:15 [1511] - info: adding message 3 to existing roomID 2 18/3 15:15 [1511] - info: adding message 4 to new roomID 2 18/3 15:15 [1511] - info: adding message 5 to new roomID 3 18/3 15:15 [1511] - error: [upgrade] Errors were encountered while updating the NodeBB schema: ERR value is not a valid float OK NodeBB Upgrade Complete!

    Before deleting the "message:x" keys from my redis database (to attempt the upgrade again) I noticed that message:5 was different than the other message keys. Specifically it seems the upgrader is choking on message:5

    "Bad" Message 5 key:
    0_1458338042461_redis-message5.png

    "Good" message key:
    0_1458338006166_redis-message6.png

    So it appears that the NodeBB upgrader does not like messages that do not have a touid or fromuid or possibly timestamp information. Should this be reported as a bug?

  • 0 Votes
    6 Posts
    4k Views

    @psychobunny nice, It's very helpful.