Thank you both and apologies for the delay! I will try them both out.

@baris Ah ok thanks, I will give it a try next time this comes up (I used the API this time).

This is one of the socket.io methods that is not available in the v3 read API yet. If you want to load all the subcategories you can do it with a socket.io emit. See below function async function getSubCategories(cid) { // store current loaded children let subCats = ajaxify.data.children.slice(); let newCats = []; // start from the nextSubCategory index let start = ajaxify.data.nextSubCategoryStart; do { // load the next page newCats = await socket.emit('categories.loadMoreSubCategories', { cid: cid, start: start, }); // move start to next page start += ajaxify.data.subCategoriesPerPage; // add the newly loaded children to our sub categories subCats = subCats.concat(newCats); // we are done if no new categories were loaded } while (!newCats.length); return subCats; } You can call this function on a category page and it would return all the subcategories of that category.

This morning I checked and the emoji image had gone, but the emoji code was still being applied whenever certain characters were used, including "£". [image: 1688790527276-92cf3b3a-e854-438b-baf5-8874b76f9933-image.png] [image: 1688790540653-bd43f17c-22b2-4b05-aa0b-9fd85be1c225-image-resized.png] I figured if it's doing a "live" replacement of those things then it must be something to do with the "Replace..." options in the plugin settings: [image: 1688790636729-9d12d3c4-3c7d-42e3-be76-f765ae91c0f1-image.png] So I disabled them both and did a restart / rebuild. The issue went away. I re-enabled them 1 by 1 to try and figure out which was causing the problem (rebuilding and restarting each time) and now, they're both re-enabled and the problem has not come back. So I'm a bit mystified. Evidently it was a problem with one of those options, but setting them again seems to have somehow fixed it.

@baris It works! Brilliant. I wasn't expecting it to be that easy

@julian said in Re-link deleted user's content when they re-join?: Right now we just save the @mention text, not the actual user association. And provided this does not provide direct attribution, then this is in fact acceptable and within GDPR. For example, having John Smith as the @ name is obviously providing attribution (but you could argue that the name means nothing given it's popularity and it would be a valid point), but a handle like "theWasp" doesn't - unless there is a post that directly correlates that handle to a physical person. For example, if someone posted "@thewasp is John Smith who lives at ....." (you get the picture), then this clearly provides direct attribution, and you'd have no foundation to keep data in this manner. Unfortunately, the only way around something like this is to develop a plugin that performs regex matches and purposely looks for data to redact or expunge. This specific method can be expensive (in the performance sense) on large forums and associated databases, and complex in nature owing to the type of regex you'd need to build. Even then, you cannot possibly catch everything because you'd run into issues such as the regex being too "greedy" (affecting large portions of text in a gratuitous nature) or too lenient (not going far enough). There is seldom any sensible balance - it's either too much, or not enough. You'd need to search the entire database looking for possible matches, and that would take significant effort to ensure you removed or redacted information that could provide attribution. This is where the waters of GDPR and privacy become muddied in the sense that you need to impose sane limits on what is necessary to either remove or redact. For example, if a user claimed that "the" personally identified them, you couldn't remove it for obvious reasons otherwise literally everything your other users have posted would need redaction, and that makes zero sense. This is why "legitimate interest" exists in the first place. You are entitled to keep data intact if it is considered impactful to the consistency if you were to remove it, but you cannot claim implied consent (assuming it's ok to keep without foundation). GDPR is a complex animal and most people either go way overboard, or do nothing at all, which is arguably worse. NodeBB has this balance just right.

@btc I plan on improving the manage/users section. Right now it shows (No email) for everyone even if they have entered an email during registration. [image: 1685911072371-current.png] So there is no way to tell which of these users left the email field empty or have a pending/expired verification email. Gonna try to change it so it looks like below. [image: 1685911189527-new.png] After that you should be able to manually verify them from the ACP or resend the confirmation email. Right now as you already figured out the confirmation email expires and there is no record of the email it was sent to so the resend in the ACP and manual verification doesn't work.

In the v3 write API, it seems that when granting privileges to groups, within each call we can only apply 1 privilege at a time. It used to be possible to apply multiple privileges in one API call. Please tell me I'm missing something! As it stands, to apply a standard set of privileges to 2 group members, I have to make 22 separate API calls where I used to make 2!

@btc hset topic:<tid> postcount <postcount> But of course, replace <tid> and <postcount> as necessary.

Is there a way to make users automatically follow all admin users when they join a nodebb forum? Or anything similar that will result in everyone getting a notification when an admin makes a post? For reference I'm on v1.9.2.

There is existing discussion about this here: https://github.com/NodeBB/NodeBB/issues/5172 You can voice your support for whatever option you see as best there.

Do you have a repo or code to show?

Excellent thanks!

Thanks so much, that has worked and I can now post new topics and replies. However I now have another issue but I think it's unrelated so will start a new thread.