v4.0.0 Upgrade Support

karsten13

Hi,

I plan upgrading to v4 and tested the new version locally getting these warnings:

2025-01-22T21:37:20.474Z [4567/233] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-2factor
  * nodebb-plugin-composer-default
  * nodebb-plugin-dbsearch
  * nodebb-widget-essentials
  * nodebb-plugin-custom-pages
  * nodebb-plugin-recent-cards
  * nodebb-plugin-question-and-answer
  * nodebb-rewards-essentials
  * nodebb-plugin-spam-be-gone

After digging in the code I found that the plugins define compatibility in their package.json

  "nbbpm": {
    "compatibility": "^3.0.0"
  },

So I did some debug logging:

'nodebb-theme-persona ^4.0.0'
'nodebb-plugin-2factor ^3.8.0'
'nodebb-plugin-composer-default ^3.0.0'
'nodebb-plugin-dbsearch ^3.3.0'
'nodebb-widget-essentials ^3.0.0'
'nodebb-plugin-custom-pages ^3.2.0'
'nodebb-plugin-recent-cards ^3.7.0'
'nodebb-plugin-mentions ^4.0.0'
'nodebb-plugin-markdown ^4.0.0'
'nodebb-plugin-emoji ^4.0.0'
'nodebb-plugin-question-and-answer ^3.6.3'
'nodebb-rewards-essentials ^3.5.0'
'nodebb-plugin-spam-be-gone ^3.0.0'

Most incompatible plugins are delivered with core nodebb.

My question: Is it safe to upgrade to v4? Waiting for compatibility updates of the plugins could take long ...

Thanks!

<baris>

All those plugins are likely working with 4.x we just need to release new versions after updating the compatibility string. 4.x didn't have plugin breaking changes like 3.x did.

julian

@baris @karsten13 agreed, all of those plugins should be working fine with latest NodeBB

cagatay

I enabled ActivityPub, but I didn’t fully understand how it works.

cagatay

I created a topic, but when I search for the link, it doesn’t appear NodeBB web site.

julian

@cagatay can you share the link with me?

cagatay

here https://efelsefe.com/topic/2371/activitypub-a-hosgeldiniz

julian

@cagatay loads fine: https://community.nodebb.org/post/https%3A%2F%2Fefelsefe.com%2Fpost%2F24380

I had to use the post URL though, to bring it in to this forum. I'll see if I can get the topic URL working instead.

The topic doesn't show up here automatically because there is no existing connection between this forum and yours.

cagatay

@julian The manual addition feels odd because when I searched for your link, it appeared directly on my site and stayed there. However, my content did not appear on your site, neither as a link nor as normal content. If this connection is going to be made through manual addition, it doesn’t seem to make much sense to me.

julian

@cagatay content discovery via ActivityPub is powered through follow relationships – I wrote more about that in our documentation

Content Discovery - NodeBB Documentation

Documentation portal for NodeBB Forum Software

(docs.nodebb.org)

When you "searched for my link", that is the same thing that I did for you. You instructed your NodeBB to load my topic/post, and conversely, I did the same to load your topic into this community.

The reason that right now it requires someone to search for it is because you don't follow me at NodeBB, and I don't follow you at efelsefe.com once I follow your account, your topics will automatically show up here in my world category.

nono-lqdn

Hello,

I have this error while upgrading to 4.0.0 :

2. Bringing base dependencies up to date...  started
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/nodebb-plugin-emoji
npm error   nodebb-plugin-emoji@"6.0.1" from the root project
npm error   peer nodebb-plugin-emoji@"^5.0.0 || ^6.0.1" from [email protected]
npm error   node_modules/nodebb-plugin-emoji-android
npm error     nodebb-plugin-emoji-android@"4.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer nodebb-plugin-emoji@"^5.0.0" from [email protected]
npm error node_modules/nodebb-plugin-emoji-one
npm error   nodebb-plugin-emoji-one@"4.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/nodebb-plugin-emoji
npm error   peer nodebb-plugin-emoji@"^5.0.0" from [email protected]
npm error   node_modules/nodebb-plugin-emoji-one
npm error     nodebb-plugin-emoji-one@"4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /srv/nodebb/.npm/_logs/2025-01-23T16_21_06_646Z-eresolve-report.txt

nono-lqdn

@nono-lqdn Fixed by doing :

npm unl nodebb-plugin-emoji
npm i nodebb-plugin-emoji

cagatay

@julian If it is a one-sided follow instead of mutual, will it not be visible post?

eeeee

I had tried the alpha and now have to go back to normal upgrade route.
after

git fetch

it said Fatal: not a git repository (or any of the parent directories): .git

whats going on here?

On another point, upgrading can be a hassle. It in theory, could something be coded so an admin could upgrade from the ACP?

FrankM

try

git reset --hard origin/v4.x

julian

@cagatay I think so. If A follows B, then B sends stuff to A, but A doesn't send stuff to B.