Skip to content
Sudonix

NodeBB: Creating the Swatch modes

Solved Configure

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • Pandaundefined

    Fixed background to nodebb forum

    Solved Configure
    25
    4 Votes
    25 Posts
    2k Views
    phenomlabundefined

    @Panda said in Fixed background to nodebb forum:

    Chatgpt told me the ::before method.

    Go figure 😛

  • phenomlabundefined

    Swatch / Theme Changer

    Code Respository
    8
    3 Votes
    8 Posts
    2k Views
    phenomlabundefined

    @veronikya it might flicker on load, yes, and that’s normal. It’s because the CSS and JS are loaded before the custom elements, but it shouldn’t be too bad on reasonable links.

    It shouldn’t flicker at all navigating through the site though as the CSS and JS are already loaded.

  • mventuresundefined

    NodeBB: Opening the Composer for replies

    Solved Configure
    2
    0 Votes
    2 Posts
    296 Views
    phenomlabundefined

    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below

    82ca1209-31be-4a51-a641-9887b5a238b8-image.png

    Failing that, you’ll need to use the reply button in the sticky toolbar

    1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png

  • mventuresundefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    6
    0 Votes
    6 Posts
    326 Views
    phenomlabundefined

    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server

    https://docs.ovh.com/gb/en/dedicated/ssh-introduction/

    Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed

    You’ll then need to change to the directory as shown below

    /home/unbuntu/nodebb

    fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png

    In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command

    cd /home/ubuntu/nodebb

    Once in the NodeBB directory, you’d use the below commands

    ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start

    Line 1 stops the NodeBB instance
    Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3
    Line 3 Runs the upgrade once the new branch is set, and code pulled
    Line 4 Restarts the NodeBB instance after the upgrade has completed

    Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.

  • mventuresundefined

    NodeBB: Creating pages

    Solved Configure
    9
    0 Votes
    9 Posts
    481 Views
    mventuresundefined

    OK, I think I have figured out how to place a link in the footer which will click to a new page.

  • mventuresundefined

    NodeBB: Privileges for the Announcement channel

    Solved Configure
    6
    1 Votes
    6 Posts
    299 Views
    phenomlabundefined

    Up to you really 🙂

  • Pandaundefined

    restarting nodebb on boot

    Unsolved Configure
    3
    1 Votes
    3 Posts
    320 Views
    phenomlabundefined

    @eeeee said in restarting nodebb on boot:

    can I just run nodebb under nodemon for auto restarts?

    It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

  • cagatayundefined

    Podcast Share NodeBB

    Solved Configure
    15
    4 Votes
    15 Posts
    707 Views
    phenomlabundefined

    @cagatay You could experiment with nodebb-plugin-ns-embed but I expect the x-origin tag on the remote site to prevent playback.