Technical Support

@[email protected] can you share a link to it?

@Kosiak Sure thing, v4 shipped with allow/deny lists so you can specify which domains to add to that list. In your case, you'd be using an allow-list. The same limitations to the content sharing model still apply. Topics and posts won't magically flow between the sites unless follow relationships exist or you set up category syncing.

Completely understood, that's why it's always been such a sticking point. We have some migrators available, but it's not always as easy as running a script and coming back to a NodeBB-compatible DB. There are always some thorny edge cases that crop up over and over again. Unfortunately we're not quite there yet, but perhaps we can get part of the way by consuming an ActivityPub actor's outbox? hmm... food for thought

@julian how will this issue with the urls with accents and Ñ ñ affect the federated content and urls?

why didn’t I think of that myself? Thank you @[email protected] and thank you for this release

@baris new info. when registering an user from /login it gets redirected to the profile instead of going to the root. I mean, share the link to register as "Forum.example/login" instead of sharing the root.. Is it possible this is related? Is this something that can be changed? Thanks Edit: I have not tried yet, but maybe if I share the url with login and then login from there, I go to the profile instead of getting back into the root? Did you try that @baris?

[image: 1737103598023-screenshot-1737103576996.png] This navigation, how to increase. I'm a newbie

@abc123 if you are unable to install NodeBB on your own I'd recommend using a hosted service (like manage.nodebb.org)

Thanks, now the testing can start with my testers. a not working search would have been a show stopper. Thanks for your input.

@xiaoye looks like an issue with the template engine and strings that start with @key and @value. I've created an issue here, in the meantime I will make some changes in core so an error like that widget doesn't prevent the page from rendering.

@Developer.this said in Some general help with NodeBB: So the plugins are OK yet there is one specific plugin that prevents the save function? That was what I ran into. It may have involved the plug-in load order, but the ones I had installed were not need to haves, but want to play withs. @Developer.this said in Some general help with NodeBB: the google SSO does work after i added the .env vars manually Sounds like something is interfering then as I did not need to do the environmental variables.

ohhhh many thanks

Just to mention, I think Amazon SES blocks sending on port 25 by default. They advise you to use 587 and StartTLS instead. If you have to use port 25 you are required to submit a request for them to allow it for you. I ran into that on helping a Xenforo admin that was wanting to use SES and was insistent that port 25 was what they wanted to use for some unknown reason.

Replying to myself, this is required when using additional locations for static files.

Hello friends, I am facing a big issue that is blocking me with Nodebb I tried building NodeBB using the postgress configuration with docker but I am getting this issue. I really don't know what is happening. The .docker/build folder is empty and is not generating nothing. I tried in Windows and in MacOS. The error is the same. Could somebody help me please? This issue is blocking me a lot. PD: I am using the code from github, not a modify version by me. Thanks for your help! nodebb-1 | 2025-01-08T23:33:41.761Z [4567/86] - info: 🎉 NodeBB Ready nodebb-1 | 2025-01-08T23:33:41.762Z [4567/86] - info: 🤝 Enabling 'trust proxy' nodebb-1 | 2025-01-08T23:33:41.763Z [4567/86] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 nodebb-1 | 2025-01-08T23:33:41.763Z [4567/86] - info: 🔗 Canonical URL: http://localhost nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - error: uncaughtException: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | at async open (node:internal/fs/promises:638:25) nodebb-1 | at async readFile (node:internal/fs/promises:1242:14) nodebb-1 | at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19) {"date":"Wed Jan 08 2025 23:33:42 GMT+0000 (Coordinated Universal Time)","error":{"code":"ENOENT","errno":-2,"path":"/usr/src/app/build/public/src/service-worker.js","syscall":"open"},"exception":true,"os":{"loadavg":[0.49,0.49,0.29],"uptime":8437.17},"process":{"argv":["/usr/local/bin/node","/usr/src/app/app.js"],"cwd":"/usr/src/app","execPath":"/usr/local/bin/node","gid":1001,"memoryUsage":{"arrayBuffers":714282,"external":4294458,"heapTotal":94744576,"heapUsed":64312264,"rss":192311296},"pid":86,"uid":1001,"version":"v22.13.0"},"stack":"Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js'\n at async open (node:internal/fs/promises:638:25)\n at async readFile (node:internal/fs/promises:1242:14)\n at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19)","trace":[{"column":25,"file":"node:internal/fs/promises","function":"async open","line":638,"method":null,"native":false},{"column":14,"file":"node:internal/fs/promises","function":"async readFile","line":1242,"method":null,"native":false},{"column":19,"file":"/usr/src/app/src/controllers/service-worker.js","function":"async Controller.generate","line":13,"method":"generate","native":false}]} nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - error: Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | at async open (node:internal/fs/promises:638:25) nodebb-1 | at async readFile (node:internal/fs/promises:1242:14) nodebb-1 | at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19) nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - info: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. nodebb-1 | 2025-01-08T23:33:42.064Z [4567/86] - info: [app] Web server closed to connections. nodebb-1 | 2025-01-08T23:33:42.071Z [4567/86] - info: [app] Live analytics saved. nodebb-1 | 2025-01-08T23:33:42.072Z [4567/86] - info: [app] Database connection closed. nodebb-1 | 2025-01-08T23:33:42.072Z [4567/86] - info: [app] Shutdown complete. nodebb-1 | [cluster] Child Process (86) has exited (code: 1, signal: null) nodebb-1 | [cluster] Spinning up another process... nodebb-1 | 2025-01-08T23:33:42.201Z [4567/118] - info: Initializing NodeBB v4.0.0-rc.4 http://localhost nodebb-1 | 2025-01-08T23:33:42.684Z [4567/118] - warn: [cache-buster] could not read cache buster ENOENT: no such file or directory, open '/usr/src/app/build/cache-buster' {"code":"ENOENT","errno":-2,"path":"/usr/src/app/build/cache-buster","stack":"Error: ENOENT: no such file or directory, open '/usr/src/app/build/cache-buster'\n at async open (node:internal/fs/promises:638:25)\n at async Object.readFile (node:internal/fs/promises:1242:14)\n at async read (/usr/src/app/src/meta/cacheBuster.js:31:18)\n at async Configs.init (/usr/src/app/src/meta/configs.js:90:17)\n at async start.start (/usr/src/app/src/start.js:19:3)","syscall":"open"} nodebb-1 | 2025-01-08T23:33:42.953Z [4567/118] - info: [socket.io] Restricting access to origin: http://localhost:* nodebb-1 | 2025-01-08T23:33:43.011Z [4567/118] - info: [api] Adding 0 route(s) to `api/v3/plugins` nodebb-1 | 2025-01-08T23:33:43.019Z [4567/118] - info: [router] Routes added nodebb-1 | 2025-01-08T23:33:43.025Z [4567/118] - info: 🎉 NodeBB Ready nodebb-1 | 2025-01-08T23:33:43.026Z [4567/118] - info: 🤝 Enabling 'trust proxy' nodebb-1 | 2025-01-08T23:33:43.027Z [4567/118] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 nodebb-1 | 2025-01-08T23:33:43.027Z [4567/118] - info: 🔗 Canonical URL: http://localhost

@baris Thanks!!

You will have to modify the template for that page which is at https://github.com/NodeBB/nodebb-theme-harmony/blob/main/templates/account/posts.tpl, keep in mind you that page is showing posts and you want to change them to show as topics so you will have to add make changes to the data as well, possibly using the hook filter:account/posts.build