With the current codebase, making a group hidden also removes it from the badge selection.

Yes, it's working now, not sure why it wasn't earlier but thanks everyone!

You can change it to 5 minutes in the ACP using the online cutoff setting.

Is there a way to enable registration queue but make it so that user's registering with admin invites are able to register bypassing registration queue and admin approval? Since it would only make sense since the admins are the ones who invited the user.

Many thanks!

Quill 2.0 has been released.
https://slab.com/blog/announcing-quill-2-0/

Word that from would bee messed up. Can you try undoing your change and console.loging those values to see what they end up being?

@baris Yes, I test develop branch and it's really worked now. But community still loaded slow and shows from time to time 503 error

@crazycells yes, just like normal topics.

@Renan-Birlem-Deves make sure you're not using some other way to send a config in, otherwise config.json may not be read (or its values overridden).

@baris thanks!

@schwach I have two installations dependent on this image and I am stuck as there are no updates for a while, i wouldn't advise using it.

I'm still looking for an efficient way to setup a docker-compose file that can be used to update with new release (both nodebb and mongodb). I wish updating nodebb was much simpler, i have an old forum started from 1.7, it has been such a pain keeping it up to date because of the need of dependencies.

Found the issue!!

You must use the main account API key and secret and not a subaccount key for everything to work.

Getting emails now through both the Cloudron side and NodeBB

@tchesley85 when creating a category you can always clone the settings (that includes privileges) of an existing category.

Yes, the errors are still there with v3.x.

I even deleted the build/ and node_modules/ directories because I thought there might be outdated files in there. But that didn't help.

However, since the MongoDB schema upgrades were successful during the ./nodebb upgrade runs, I was able to complete the upgrade by doing a fresh git install and copying back the old config.json before running the setup routine. I then manually restored all the static files in public/uploads via rsync.

Not sure how that will be implemented since Tag1 and tag1 would end up being two different tags. Lowercasing solves that problem.

@crazycells Agree - you can have as many or as few as you'd like though.

@julian - Done! Thank you for the quick responses.

Yeah I think having a folder under public/uploads/profile for each user would make deleting easier. We can get rid of the glob and delete that folder on user deletion. But we would have to write an upgrade script to move all files and update the path in the user object since they are stored as "/assets/uploads/profile/1-profileavatar-1709738685611.jpeg"

@julian said in PWA push notifications:

@crazycells I will believe it when it happens 😏

Hi @julian , since apple has been supporting web push notifications for a while now... I am curious if there is an android counterpart plugin for ios in the pipeline?

https://developer.apple.com/documentation/usernotifications/sending-web-push-notifications-in-web-apps-and-browsers

@PitaJ v16.13.0 obviosuly very old 😞 Ooops..installed latest version and now it is all ok..

Thanks for the gentle reminder.

@hnipps said in Invalid CSRF token when authenticating via third-party app:

I'm trying to use NodeBB as a headless forum (i.e. just a REST API with a separate front end) but keep getting an "invalid csrf token" error when I try to authenticate.

I've confirmed I can authenticate via the NodeBB UI on the same instance.

I've also tried getting the NodeBB config and using the csrf token from there in my requests but it still does not work.

My frontend is a NextJS app that rewrites all /api/:path* requests to http://<MY-NODE-BB-INSTANCE>/api/:path*. It also rewrites the auth paths.

I can see the requests reach NodeBB but always get "invalid csrf token".

I've verified that I can successfully call GET endpoints from my app, e.g. I can get the user list from /api/users.

This is a 2 yr old thread, but @hnipps have you gone any further with the React/NextJS frontend with a headless nodebb?
If you have made any progress I would love to contribute on the frontend build. It is daunting to start as a new project but if any foundations were laid I would love to jump in and build upon it.