Skip to content
Sudonix

NodeBB 3.0 alpha1 : Error on install

Solved Configure
  • DownPWundefined

    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 ?

    PW and WS Spirit alive

    0
  • phenomlabundefined

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

    nodebb-plugin-emoji@4.0.6

    Then try the upgrade process again.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab

    npm remove nodebb-plugin

    ?

    PW and WS Spirit alive

    DownPWundefined phenomlabundefined 2 Replies
    0
  • DownPWundefined

    @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

    PW and WS Spirit alive

    phenomlabundefined 2 Replies
    0
  • phenomlabundefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • phenomlabundefined

    @DownPW looks like a permissions issue?

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab I’m on root maybe that

    EDit: nope idem on non root user

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW can you try with just

    npm remove nodebb-plugin-emoj

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

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

    npm remove nodebb-plugin-emoj

    nope

    PW and WS Spirit alive

    0
  • phenomlabundefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @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

    PW and WS Spirit alive

    0
  • phenomlabundefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @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 ?

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @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.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    1
  • DownPWundefined

    @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

    PW and WS Spirit alive

    0
  • DownPWundefined DownPW has marked this topic as solved on
  • phenomlabundefined

    @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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab

    37565bc6-3136-4ff4-b476-280934c48663-image.png

    PW and WS Spirit alive

    0
  • phenomlabundefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab Work now 😉

    PW and WS Spirit alive

    1

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 💗

  • Pandaundefined

    SEO and Nodebb

    Performance
    2
    2 Votes
    2 Posts
    143 Views
    phenomlabundefined

    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example

    https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1

    However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts

    https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365

    And also

    https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164

    It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”.

    Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.

  • Pandaundefined

    Composer options on nodebb

    Solved Configure
    8
    3 Votes
    8 Posts
    289 Views
    phenomlabundefined

    @Panda You should be able to expose the CSS for these using F12 to get into console

    3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png

    a2b8ed46-4157-4ff2-85f0-576543380107-image.png

    That should then expose the element once selected

    89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png

    Here’s the below CSS you need based on the screenshot provided.

    .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • Pandaundefined

    Email validation NodeBB

    Bugs
    21
    3 Votes
    21 Posts
    878 Views
    phenomlabundefined

    @Panda said in Email validation NodeBB:

    Did you configure that as a custom change to the usual quote icon. How do you do that?
    I notice on NodeBB site its a solid blue quotes

    Yes, I changed it. NodeBB by default users the free font awesome library whereas I use the pro (paid) version SDK have access to a wider set of icons, and at different thicknesses etc. The change of colour is just simple CSS.

  • Pandaundefined

    adding some console.log to Nodebb

    Solved Customisation
    4
    1 Votes
    4 Posts
    475 Views
    phenomlabundefined

    @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.

  • mventuresundefined

    NodeBB: Favicon upload issue

    Solved Configure
    12
    3 Votes
    12 Posts
    356 Views
    mventuresundefined

    @phenomlab I am on a Mac, so I used the “Option + Command + I”, and then performed the steps. It loaded my favicon! I checked on Firefox which I haven’t used before, and it showed my favicon also! That’s fantastic and thank you for the help!

  • mventuresundefined

    NodeBB: Privileges for the Announcement channel

    Solved Configure
    6
    1 Votes
    6 Posts
    188 Views
    phenomlabundefined

    Up to you really 🙂

  • phenomlabundefined

    NodeBB slow after DB recovery

    Solved Performance
    1
    5 Votes
    1 Posts
    249 Views
    No one has replied
  • DownPWundefined

    [NODEBB] Wallpapers BUG on Firefox Mobile ?

    Solved Customisation
    9
    0 Votes
    9 Posts
    804 Views
    phenomlabundefined

    @downpw I’m inclined to agree with this. There isn’t much else you can do, and provided it works with no odd looking artefacts in other browsers, then ok. The :before and :after are pseudo classes and very well supported across all browsers (except perhaps Internet Exploder, but who uses that these days ?)