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: nodebb-plugin-emoji-one@4.0.0
npm error Found: nodebb-plugin-emoji@6.0.1
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 nodebb-plugin-emoji-android@4.1.1
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 nodebb-plugin-emoji-one@4.0.0
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: nodebb-plugin-emoji@5.2.0
npm error node_modules/nodebb-plugin-emoji
npm error   peer nodebb-plugin-emoji@"^5.0.0" from nodebb-plugin-emoji-one@4.0.0
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 Fixed by doing :

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

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

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?

try

git reset --hard origin/v4.x

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

@jdp23@neuromatch.social can you please update the category handles on discussions.thenexus.today? There was a bug that caused some categories to not respond to webfinger request appropriately, so they could not be found on fedi.

You can just change them from one handle to another, and then back again.

That should fix the issue with the testing category not being able to be found.

@julian done, thanks for looking at this!

while I've got you on the line ... i'm still experimenting with Bridgy Fed and last night i had somewhat unexpected results (although maybe it's just that my expectation is wrong). CCing @snarfed.org and @quillmatiq as well ...

There were three accounts involved:

* jon@discussions.thenexus.today and jdp23.thenexus.today (on Bluesky) are following each other

* thenexusofprivacy.net on Bluesky and jon@discussions.thenexus.today *aren't* following each other (but thenexusofprivacy.net *is* following ap.brid.gy, and bridges correctly in other situations)

jon@discussions.thenexus.today posted https://discussions.thenexus.today/topic/28/testing-federation-from-nodebb-to-bluesky-again-... and it federated correctly. Yay! Here's the bridged equivalent: https://bsky.app/profile/jon.discussions.thenexus.today.ap.brid.gy/post/3lgwoj4vkgbd2

jon@discussions.thenexus.today replied and it federated back. also yay!

but when thenexusofprivacy.net replied, it *didn't* federate back. not so yay.

Any idea what's going on?

I did upgrade to v4.0.1 yesterday and now have an issue displaying some forum posts on apple devices (under safari or chrome).

As example you can take a look at https://forum.magicmirror.builders/topic/19306/new-module-installer

Problem is the preview of the 4 images from the topic at the top right. On an iphone they are overlapping so you can not really operate.

Is there an option to disable this preview?

Thanks!

You can hide it with custom css in the ACP, .topic-header [component="topic/thumb/list"] { display: none }

This is only happening on apple devices?

nothing changes v4.0.1
I think this ActivityPub implementation is only designed for NodeBB's own page. It’s not very useful for sites that use NodeBB.

@baris looks to be Persona, could be a bug with the theme.