administrators

Click here to see the full blog post

@mj Can you post it on our github? Thanks.

Can you paste the entire stack trace?

@dravere can you make a change for me and run the upgrade script again?

Add console.log('uploads', pid, uploads); here

The error is caused by a timeout and the only place I can think of halting execution is that while loop. The timeout seems to be 10minutes and if cursor.next() is not called for 10minutes you get that cursor not found error.

@abhinov-singh As stated in other thread, please consider upgrading your NodeBB as that may resolve the issue. Locking this thread now to reduce duplicate responses.

It is safe to assume that if a user explicitly set their user digest setting, then they can consider having opted into the email.

For those users that have not set any setting explicitly, you can change the default in the ACP, and that value will propagate to those users as well. So you'll probably want to disable the email digest for default users.

@alanbrown Depends which hook you are using, perhaps we can add that data in as well.

@yapne the scheduling is done inside NodeBB via a cron-like dependency. We don't hook into system cron.

@dravere said in Is there a way to display moderator rights only in category the user is a moderator?:

Otherwise I think it could be done via the hook filter:topics.addPostData? Just iterate over the posts array, get the category, and for every user of a post add an object to custom_profile_info with the property content set to some HTML indicating moderator rights?

Probably this... alternatively, use the groups method, but hook into filter:topics.addPostData to remove the group badge if they're not in the category that user moderates?

The recommended method of sharing sessions between two separate and distinct applications is through OAuth2. We recommend this approach because NodeBB maintains its own user records, so that we can keep track of user-related metrics and other data. Relying on another database would be tricky, prone to breaking, and quite possibly dangerous.

Luckily, it's quite straightforward to get things working with OAuth2!

The first step is getting your application to expose an OAuth2 endpoint. If you're running a Node.js based app, you can use a module called OAuth2orize.

Once that is set up, you'll want to take a look at the SSO plugin skeleton for customised OAuth deployments -- nodebb-plugin-sso-oauth. You'll take this plugin, fork it, and modify it to communicate with your OAuth endpoint.

Once everything is working properly, you should be able to register and log in/out via your web app.