Community

Include "npm update " in upgrade

Feature Requests
  • E
    E
    #1

    Today I upgraded my forum from v0.4.1 to v0.4.3 . When upgrading ,I got some trouble such as widget error.I solved these problems by upgrading my dependency npm upgrade ,eventually.
    I think maybe It's better to include npm update in nodebb upgrade command ☺

    0
  • julianJ
    julianJ
    GNU/Linux
    #2

    We'd probably have to roll our own upgrade script that calls npm install with a version number. npm upgrade is too risky, since it downloads the latest version of a module, irrespective of any configured versioning in your package.json.

    Our themes and plugins aren't comparible with older versions, so they might end up installing a version that is too new and break their forum...

    1

Suggested Topics

  • W

    Another way to format quotes in replies?

    Feature Requests
    0 Votes
    2 Posts
    1105 Views

    PitaJP

    @wptheme88 almost anything is possible with CSS. What do you want?

  • NicolasN

    Upgrade: show progress

    Feature Requests
    0 Votes
    1 Posts
    1066 Views

    NicolasN

    Would be nice to see upgrade progress for ./nodebb upgrade.
    Thanks 😉

  • A

    Using Auto 301 Redirect after Renaming/ Updating the Existing Topic to New

    Feature Requests
    0 Votes
    4 Posts
    1950 Views

    julianJ

    This is related to an issue resolved earlier.

    We found that if a topic's posts contained images pointing to a relative path (e.g. ![test](1.jpg), NodeBB would attempt to load them, causing them to load the entire topic again (since the url is site.com/topic/123/1.jpg).

    To combat this, @baris restricted the URL so that the slug must be correct, otherwise the user is sent to 404.

    For lack of a better solution, this was the approach we took, so this seems to be the reason why you're running into this issue now.

  • PitaJP

    Support PM2 for the "Restart NodeBB" button

    Feature Requests
    0 Votes
    7 Posts
    2736 Views

    PitaJP

    @julian said:

    If you're using pm2 loader.js, you should use the restart button in the ACP to restart NodeBB... 😄

    I was dag nabbit.

    (... or ideally, don't use PM2 at all, since the loader supercedes it. Just: ./nodebb start)

    But I like to use pm2 because I use it for all of my other task management needs. Where in the code would it be?

  • R

    Generate "502 Bad Gateway" page after every theme change

    Feature Requests
    0 Votes
    1 Posts
    1066 Views

    R

    When "community.nodebb.org" was updating, nginx servered a "502 Bad Gateway" text error page instead of a custom page displaying something like: "We will be back soon". I recommend that NodeBB creates a static page that is directly servered by nginx when NodeBB is down. This page should use the exact same theme as you currently have selected for your site. I think the link to nginx should be automated as much as possible (maybe ask [yes]/no permission in setup). But if it can't be there needs to be an easy tutorial on how to link nginx to this static page. The static page should be able to be overridden. It should be updated every time the theme changes. Thoughts?

| | | |
Copyright © 2023 NodeBB | Contributors