Skip to content

NodeBB 3.0 alpha1 : Error on install

Solved Configure
19 2 3.0k 1
  • Hello @phenomlab

    I want to test alpha1 for V3 for test JS, theme switcher, css themes, etc.

    I have upgraded my dev environnement to 2.8.1
    I follow this link : https://community.nodebb.org/post/89581

    So, hop !

    cd /path/to/your/nodebb
    git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    git fetch && git checkout bootstrap5
    git reset --hard v3.0.0-alpha.1
    ./nodebb upgrade -mi
    

    But 😞

    nodebb@node:~$ cd /home/nodebb/nodebb/
    nodebb@node:~/nodebb$ git rev-parse HEAD
    727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    nodebb@node:~/nodebb$ git fetch && git checkout bootstrap5
    error: impossible d'ouvrir .git/FETCH_HEAD: Permission non accordée
    nodebb@node:~/nodebb$ su -
    Mot de passe : 
    root@node:~# cd /home/nodebb/nodebb/
    root@node:/home/nodebb/nodebb# git fetch && git checkout bootstrap5
    remote: Enumerating objects: 5, done.
    remote: Counting objects: 100% (5/5), done.
    remote: Total 5 (delta 4), reused 5 (delta 4), pack-reused 0
    Dépaquetage des objets: 100% (5/5), 441 octets | 73.00 Kio/s, fait.
    Depuis https://github.com/NodeBB/NodeBB
       cf7aa1941..71743affc  bootstrap5 -> origin/bootstrap5
    La branche 'bootstrap5' est paramétrée pour suivre la branche distante 'bootstrap5' depuis 'origin'.
    Basculement sur la nouvelle branche 'bootstrap5'
    root@node:/home/nodebb/nodebb# git reset --hard v3.0.0-alpha.1
    HEAD est maintenant à 4f70d19e1 chore: v3.0.0-alpha.1 :tada:
    root@node:/home/nodebb/nodebb# ./nodebb upgrade -mi
    Dependencies outdated or not yet installed.
    Installing them now...
    
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-emoji@4.0.6
    npm WARN node_modules/nodebb-plugin-emoji
    npm WARN   nodebb-plugin-emoji@"5.0.2" from the root project
    npm WARN   2 more (@nodebb/nodebb-plugin-reactions, nodebb-plugin-emoji-android)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-markdown@10.1.1
    npm WARN node_modules/nodebb-plugin-markdown
    npm WARN   nodebb-plugin-markdown@"11.0.2" from the root project
    npm WARN   1 more (nodebb-plugin-extended-markdown)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN node_modules/nodebb-plugin-extended-markdown
    npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm ERR! code 128
    npm ERR! An unknown git error occurred
    npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
    npm ERR! Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of known hosts.
    npm ERR! git@github.com: Permission denied (publickey).
    npm ERR! fatal: Impossible de lire le dépôt distant.
    npm ERR! 
    npm ERR! Veuillez vérifier que vous avez les droits d'accès
    npm ERR! et que le dépôt existe.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2023-01-05T21_47_28_777Z-debug-0.log
    Error installing dependencies!
    message: Command failed: npm install --omit=dev
    stdout: null
    stderr: null
    /home/nodebb/nodebb/src/cli/package-install.js:138
                    throw e;
                    ^
    
    Error: Command failed: npm install --omit=dev
        at checkExecSyncError (node:child_process:841:11)
        at Object.execSync (node:child_process:912:15)
        at Object.pkgInstall.installAll (/home/nodebb/nodebb/src/cli/package-install.js:129:9)
        at Object.<anonymous> (/home/nodebb/nodebb/src/cli/index.js:51:18)
        at Module._compile (node:internal/modules/cjs/loader:1126:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
        at Module.load (node:internal/modules/cjs/loader:1004:32)
        at Function.Module._load (node:internal/modules/cjs/loader:839:12)
        at Module.require (node:internal/modules/cjs/loader:1028:19) {
      status: 128,
      signal: null,
      output: [ null, null, null ],
      pid: 1251,
      stdout: null,
      stderr: null
    }
    

    An idea ?

  • Hello @phenomlab

    I want to test alpha1 for V3 for test JS, theme switcher, css themes, etc.

    I have upgraded my dev environnement to 2.8.1
    I follow this link : https://community.nodebb.org/post/89581

    So, hop !

    cd /path/to/your/nodebb
    git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    git fetch && git checkout bootstrap5
    git reset --hard v3.0.0-alpha.1
    ./nodebb upgrade -mi
    

    But 😞

    nodebb@node:~$ cd /home/nodebb/nodebb/
    nodebb@node:~/nodebb$ git rev-parse HEAD
    727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    nodebb@node:~/nodebb$ git fetch && git checkout bootstrap5
    error: impossible d'ouvrir .git/FETCH_HEAD: Permission non accordée
    nodebb@node:~/nodebb$ su -
    Mot de passe : 
    root@node:~# cd /home/nodebb/nodebb/
    root@node:/home/nodebb/nodebb# git fetch && git checkout bootstrap5
    remote: Enumerating objects: 5, done.
    remote: Counting objects: 100% (5/5), done.
    remote: Total 5 (delta 4), reused 5 (delta 4), pack-reused 0
    Dépaquetage des objets: 100% (5/5), 441 octets | 73.00 Kio/s, fait.
    Depuis https://github.com/NodeBB/NodeBB
       cf7aa1941..71743affc  bootstrap5 -> origin/bootstrap5
    La branche 'bootstrap5' est paramétrée pour suivre la branche distante 'bootstrap5' depuis 'origin'.
    Basculement sur la nouvelle branche 'bootstrap5'
    root@node:/home/nodebb/nodebb# git reset --hard v3.0.0-alpha.1
    HEAD est maintenant à 4f70d19e1 chore: v3.0.0-alpha.1 :tada:
    root@node:/home/nodebb/nodebb# ./nodebb upgrade -mi
    Dependencies outdated or not yet installed.
    Installing them now...
    
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-emoji@4.0.6
    npm WARN node_modules/nodebb-plugin-emoji
    npm WARN   nodebb-plugin-emoji@"5.0.2" from the root project
    npm WARN   2 more (@nodebb/nodebb-plugin-reactions, nodebb-plugin-emoji-android)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-markdown@10.1.1
    npm WARN node_modules/nodebb-plugin-markdown
    npm WARN   nodebb-plugin-markdown@"11.0.2" from the root project
    npm WARN   1 more (nodebb-plugin-extended-markdown)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN node_modules/nodebb-plugin-extended-markdown
    npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm ERR! code 128
    npm ERR! An unknown git error occurred
    npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
    npm ERR! Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of known hosts.
    npm ERR! git@github.com: Permission denied (publickey).
    npm ERR! fatal: Impossible de lire le dépôt distant.
    npm ERR! 
    npm ERR! Veuillez vérifier que vous avez les droits d'accès
    npm ERR! et que le dépôt existe.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2023-01-05T21_47_28_777Z-debug-0.log
    Error installing dependencies!
    message: Command failed: npm install --omit=dev
    stdout: null
    stderr: null
    /home/nodebb/nodebb/src/cli/package-install.js:138
                    throw e;
                    ^
    
    Error: Command failed: npm install --omit=dev
        at checkExecSyncError (node:child_process:841:11)
        at Object.execSync (node:child_process:912:15)
        at Object.pkgInstall.installAll (/home/nodebb/nodebb/src/cli/package-install.js:129:9)
        at Object.<anonymous> (/home/nodebb/nodebb/src/cli/index.js:51:18)
        at Module._compile (node:internal/modules/cjs/loader:1126:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
        at Module.load (node:internal/modules/cjs/loader:1004:32)
        at Function.Module._load (node:internal/modules/cjs/loader:839:12)
        at Module.require (node:internal/modules/cjs/loader:1028:19) {
      status: 128,
      signal: null,
      output: [ null, null, null ],
      pid: 1251,
      stdout: null,
      stderr: null
    }
    

    An idea ?

    @DownPW you should remove the plugins quoted in that list - for example

    nodebb-plugin-emoji@4.0.6
    

    Then try the upgrade process again.

  • @DownPW you should remove the plugins quoted in that list - for example

    nodebb-plugin-emoji@4.0.6
    

    Then try the upgrade process again.

    @phenomlab

    npm remove nodebb-plugin
    

    ?

  • @phenomlab

    npm remove nodebb-plugin
    

    ?

    @phenomlab

    test with npm remove nodebb-plugin-emoji@4.0.6

    npm remove nodebb-plugin-emoji@4.0.6
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-emoji@4.0.6
    npm WARN node_modules/nodebb-plugin-emoji
    npm WARN   peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN   node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN     @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN   2 more (nodebb-plugin-emoji-android, the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-markdown@10.1.1
    npm WARN node_modules/nodebb-plugin-markdown
    npm WARN   peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN   node_modules/nodebb-plugin-extended-markdown
    npm WARN     nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm WARN   1 more (the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN node_modules/nodebb-plugin-extended-markdown
    npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm ERR! code 128
    npm ERR! An unknown git error occurred
    npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
    npm ERR! git@github.com: Permission denied (publickey).
    npm ERR! fatal: Impossible de lire le dépôt distant.
    npm ERR! 
    npm ERR! Veuillez vérifier que vous avez les droits d'accès
    npm ERR! et que le dépôt existe.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2023-01-05T22_23_12_150Z-debug-0.log
    
  • @phenomlab

    npm remove nodebb-plugin
    

    ?

    @DownPW yes, exactly. You can then install the updated (and compliant) v3 versions after the upgrade process completed successfully.

  • @phenomlab

    test with npm remove nodebb-plugin-emoji@4.0.6

    npm remove nodebb-plugin-emoji@4.0.6
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-emoji@4.0.6
    npm WARN node_modules/nodebb-plugin-emoji
    npm WARN   peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN   node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN     @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN   2 more (nodebb-plugin-emoji-android, the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-markdown@10.1.1
    npm WARN node_modules/nodebb-plugin-markdown
    npm WARN   peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN   node_modules/nodebb-plugin-extended-markdown
    npm WARN     nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm WARN   1 more (the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN node_modules/nodebb-plugin-extended-markdown
    npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm ERR! code 128
    npm ERR! An unknown git error occurred
    npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
    npm ERR! git@github.com: Permission denied (publickey).
    npm ERR! fatal: Impossible de lire le dépôt distant.
    npm ERR! 
    npm ERR! Veuillez vérifier que vous avez les droits d'accès
    npm ERR! et que le dépôt existe.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2023-01-05T22_23_12_150Z-debug-0.log
    

    @DownPW looks like a permissions issue?

  • @DownPW looks like a permissions issue?

    @phenomlab I’m on root maybe that

    EDit: nope idem on non root user

  • @phenomlab

    test with npm remove nodebb-plugin-emoji@4.0.6

    npm remove nodebb-plugin-emoji@4.0.6
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-emoji@4.0.6
    npm WARN node_modules/nodebb-plugin-emoji
    npm WARN   peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN   node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN     @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN   2 more (nodebb-plugin-emoji-android, the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
    npm WARN node_modules/@nodebb/nodebb-plugin-reactions
    npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
    npm WARN ERESOLVE overriding peer dependency
    npm WARN While resolving: nodebb@3.0.0-alpha.1
    npm WARN Found: nodebb-plugin-markdown@10.1.1
    npm WARN node_modules/nodebb-plugin-markdown
    npm WARN   peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN   node_modules/nodebb-plugin-extended-markdown
    npm WARN     nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm WARN   1 more (the root project)
    npm WARN 
    npm WARN Could not resolve dependency:
    npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
    npm WARN node_modules/nodebb-plugin-extended-markdown
    npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
    npm ERR! code 128
    npm ERR! An unknown git error occurred
    npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
    npm ERR! git@github.com: Permission denied (publickey).
    npm ERR! fatal: Impossible de lire le dépôt distant.
    npm ERR! 
    npm ERR! Veuillez vérifier que vous avez les droits d'accès
    npm ERR! et que le dépôt existe.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2023-01-05T22_23_12_150Z-debug-0.log
    

    @DownPW can you try with just

    npm remove nodebb-plugin-emoj
    
  • @DownPW can you try with just

    npm remove nodebb-plugin-emoj
    

    @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    npm remove nodebb-plugin-emoj

    nope

  • @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    npm remove nodebb-plugin-emoj

    nope

    @DownPW can you provide an output of the currently installed plugins before upgrade?

  • @DownPW can you provide an output of the currently installed plugins before upgrade?

    @phenomlab https://community.nodebb.org/topic/16721/nodebb-v3-0-0-alpha-1-an-alpha-release/29

    maybe a problem with depot permissions.
    I wait a answer by Pitag or other nodebb staff

  • @phenomlab https://community.nodebb.org/topic/16721/nodebb-v3-0-0-alpha-1-an-alpha-release/29

    maybe a problem with depot permissions.
    I wait a answer by Pitag or other nodebb staff

    @DownPW yes, I saw that this morning. You could still try and remove those plugins which aren’t compliant though.

  • @phenomlab

    Hourra I’m on V3 🙂

    here the solution for installation :

    cd /path/to/your/nodebb
    git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    git fetch && git checkout bootstrap5
    git reset --hard v3.0.0-alpha.3
    npm config set legacy-peer-deps true
    ./nodebb upgrade -mi
    ./nodebb build
    ./nodebb start
    

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    –> Could I count on you to help me evolve the things we created together for Persona5 or Harmony? Like footerbar, theme Switcher selector, welcome message with image change ?

    –> Other things, Harmony theme not include on alpha ?

  • @phenomlab

    Hourra I’m on V3 🙂

    here the solution for installation :

    cd /path/to/your/nodebb
    git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
    git fetch && git checkout bootstrap5
    git reset --hard v3.0.0-alpha.3
    npm config set legacy-peer-deps true
    ./nodebb upgrade -mi
    ./nodebb build
    ./nodebb start
    

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    –> Could I count on you to help me evolve the things we created together for Persona5 or Harmony? Like footerbar, theme Switcher selector, welcome message with image change ?

    –> Other things, Harmony theme not include on alpha ?

    @DownPW said in NodeBB 3.0 alpha1 : Error on install:

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    It does work, but needs minor tweaks as the existing listener doesn’t work under bootstrap 5 as it did under bootstrap 3. Nothing major to fix.

    Of course you can count on me. I’ll be in the same journey 🙂

    Harmony isn’t available yet from what I’ve read - not until beta releases I think.

  • @DownPW said in NodeBB 3.0 alpha1 : Error on install:

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    It does work, but needs minor tweaks as the existing listener doesn’t work under bootstrap 5 as it did under bootstrap 3. Nothing major to fix.

    Of course you can count on me. I’ll be in the same journey 🙂

    Harmony isn’t available yet from what I’ve read - not until beta releases I think.

    @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    Of course you can count on me. I’ll be in the same journey

    ✈

    haha that doesn’t surprise me. Thank you again for that my friend 👍 ♥

    I still hesitate between staying under Persona 5 or Harmony.

    I will decide when I can test it

  • DownPWundefined DownPW has marked this topic as solved on
  • @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    Of course you can count on me. I’ll be in the same journey

    ✈

    haha that doesn’t surprise me. Thank you again for that my friend 👍 ♥

    I still hesitate between staying under Persona 5 or Harmony.

    I will decide when I can test it

    @DownPW I’m going to test harmony. I quite like the look. However, I did start a topic to discuss this. Would appreciate input

    https://sudonix.com/topic/397/nodebb-v3-and-harmony-theme

  • @DownPW I’m going to test harmony. I quite like the look. However, I did start a topic to discuss this. Would appreciate input

    https://sudonix.com/topic/397/nodebb-v3-and-harmony-theme

  • @DownPW very odd. I don’t recall setting permissions there but try now.

  • @DownPW very odd. I don’t recall setting permissions there but try now.

    @phenomlab Work now 😉


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
  • Bug Report

    Solved Bugs nodebb bugs
    47
    1
    26 Votes
    47 Posts
    9k Views
    @crazycells Good points, thanks. I completely forgot that classes are added - makes life much simpler! EDIT - seems this is pretty straightforward, and only needs the below CSS .upvoted i { color: var(--bs-user-level) !important; } This then yields [image: 1718028529465-3f072f8a-ebfa-4910-8723-73c493b8e4eb-image.png] However, the caveat here is that the .upvoted class will only show for your upvotes, and nobody else’s. However, this does satisfy the original request however I would love to see my upvoted posts more clearly, because currently, when I upvote, nothing on the post tool is changing, it would be nicer if there is an indication that I have upvoted (like a filled or colored triangle?)
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    800 Views
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • adding some console.log to Nodebb

    Solved Customisation nodebb
    4
    1 Votes
    4 Posts
    1k Views
    @eeeee if you’re using the console, you could try node app.js > app.log 2>&1 This would redirect stdout to a file named app.log and redirect stderr to stdout. I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log. Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.
  • NodeBB: hCaptcha

    Solved Configure hcaptcha
    15
    2 Votes
    15 Posts
    2k Views
    @mventures none that I know of. I don’t recall selecting these either for mine.
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    1k Views
    @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 [image: 1680448167972-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.
  • Upgrade Problem from 2.8.3 to 2.8.4

    Solved Configure nodebb
    35
    1
    8 Votes
    35 Posts
    6k Views
    @cagatay No, you can ignore that.
  • Gettin Erors NodeBB

    Solved Configure nodebb eror
    7
    0 Votes
    7 Posts
    1k Views
    @phenomlab no forum is working goods. there is no eror message since yestarday.
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    7k Views
    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.