I have a related question please if someone can help with a short example.

I am mainly trying to send some data to my plugin, from the client side to perform an action not available via API.
I thought I could fire a hook on client side and that would get the data to the plugin, but I don't see any data. I am wondering is it possible to fire a hook from the client-side?

I can see some hook examples in composer plugin, but I am not sure if I can send data to the server, and have my plugin receive the data and perform an action, is it possible? and any guidance on how I may accomplish it?

I don't need to return a value, I just need some data to do a change server-side but which is not available by API.

Thank you

@baris said in Last group owner able to rescind ownership leaving group ownerless, but code was intended to disallow such action:

@solmak nice catch, I've fixed it here will be available in 3.7.2.

Thank you for spending time on this, that was fast!

I am working on an instance of nodebb where Groups are as major part as Categories, i.e. users are allowed to create groups, and have categories dedicated to groups, to moderate their own group/category as owners, etc.

I am finding that Groups part of nodebb hasn't gotten much attention since it is not the major aspect of a the usual use case.

However, here is a bug I found: It appears the program does not intend for any group to be ownerless (as per the code throwing error).

In src/groups/ownership
Method Groups.ownership.rescind
It appears the intention was for the function to make sure this wasn't the last owner who is being rescinded ownership, and throw an error.

const numOwners = await db.setCount(`group:${groupName}:owners`);
const isOwner = await db.isSortedSetMember(`group:${groupName}:owners`);
if (numOwners <= 1 && isOwner) {
			throw new Error('[[error:group-needs-owner]]');
		}

However, isOwner is returning false even when the uid is the owner, and hence they're being removed as owner, and group is able to become ownerless. Nothing wrong with ownerless groups, but since the intention in the code appears to be contrary to the output I felt it appropriate to be in the bug reports category here.

I've replaced the above check, with this function instead, and now I see the error thrown.

const isOwner = await db.isSetMember(`group:${groupName}:owners`, toUid);

Not a major issue, but since I am working on something where groups play a major role (group based site) I found this and wanted to bring this out here.

nodebb v3.7.1

@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.

@data-dataninja said in react-redux-nodebb, we are building it!:

We are building react-redux-nodebb

this will enable react-dom & react-native with nodebb, which means we can build nodeBB into native apps & also use react ecosystem UI components

steps we are taking:

1. react-redux structure (state, api, hooks)
2. converting controllers
3. module bridge (to enable current ecosystem of plugins)

then next up we will build:
react-native-nodebb theme & skins

Any help & suggestions are super welcome!

This is quite an old post, but @data-dataninja have you given up on building the decoupled frontend?
I am more interested in a NextJS or any Server Side rendered solution to get the SEO and other benefits of SSR.
But a frontend in React-Redux would be a good start if you're working on it.

Thanks a ton @julian I was able to set a boolean field called 'locked' to the groupd data upon group creation, and was able to retrieve it in the group update hooks to work with it!

Will a similar approach also apply for custom data added to category, group, post, topic? If so that would make life so much easier for me, literally! I can't let go nodebb especially seeing you work so hard on getting it to work with fediverse, it opens up so many possibilities and is better for the internet community as a whole in this era of corporate and govt censorship and restrictions on free-speech!

Thank you @julian you always respond and seem motivated in helping the community. By proprietary I meant no effort has been made to provide clean working examples for the latest nodebb, as in maintenance of such documentation for people jumping into nodebb to replace their old system.

You have a great product here, with so much more potential and I understand you may not have resources and funding to provide so much documentation and maintain working example of a plugin that does CRUD with custom fields/custom data, but it becomes harder for new adopters if they're unable to figure out cost effective way to replace their old platforms which have plethora of 3rd party add-ons and plugins especially dealing with custom fields and custom data.

I take the blame as well, as part of the community it is partly our job to help keep a set of quickstart plugins, documentation, help available to enhance and optimize the process for new adopters. I hope the community gets together and makes something like a curated directory of available plugins, and tags and tracks what versions each supports, and tries to keep a version that supports the latest major version updates.

Thank you for the wonderful product, I keep trying and finding an excuse to adopt it and hopefully I will get there sooner or later.

I thought NodeBB was trying to emulate how wordpress works, in terms of ease of extending functionality. Yet, so much confusion about adding custom fields and old plugins which don't work anymore make it harder to adopt NodeBB. Adding, retrieving, and displaying custom data for users, categories, topics, posts, groups should be easier and documented for developers who want to adopt and extend NodeBB, keeping this information so proprietary maybe a good business decision but it certainly isn't going to help expand adoption of NodeBB.

I don't see any examples of this basic extension implementation in plugin documentation, and trying to decipher how old plugins are doing it is a mess as demonstrated by so many users who gave up, by their own admission which I found upon searching this forum to learn custom fields/custom data implementation via plugins.

@baris Thanks a lot for replying, and I apologize for wasting your time
I somehow got the markdown plugin disabled while upgrading, hence the issue.
Enabling it back up solved it.

Hey folks anyone experienced this issue?

After upgrading from v3.6.3 to v3.6.4 i don't see line breaks when writing posts, all the text shows up as one chunk of content when posted, including replies.