NodeBB version: 4.10.0 Description When the chat modal (#chat-modal-{roomId}) is open and the user focuses the textarea inside it, the browser logs the following warning: Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. The modal div keeps aria-hidden="true" while one of its descendants — the .chat-input textarea — holds focus. This is a direct violation of the WAI-ARIA specification, which states that aria-hidden must not be applied to a focused element or any of its ancestors. Steps to reproduce Open a chat window (any room). Click inside the message textarea. Open the browser DevTools console. Observe the warning: Blocked aria-hidden on an element because its descendant retained focus. Element with focus: <textarea.chat-input …> Ancestor with aria-hidden: <div.chat-modal … aria-hidden="true" …> Expected behaviour aria-hidden="true" should be removed from the chat modal (or never set) when any focusable element inside it receives focus. Screen reader users should be able to interact with the chat textarea without it being hidden from assistive technologies. Actual behaviour The modal retains aria-hidden="true" even when its child textarea is focused, causing the focus to silently disappear for screen reader users and breaking keyboard accessibility. Suggested fix Two approaches: 1. Remove aria-hidden on focus — listen for focusin events on .chat-input and strip aria-hidden from the closest ancestor that carries it: document.addEventListener('focusin', (e) => { if (e.target.classList.contains('chat-input')) { const modal = e.target.closest('[aria-hidden="true"]'); if (modal) modal.removeAttribute('aria-hidden'); } }); 2. Replace aria-hidden with inert — the inert attribute (now baseline across all major browsers) prevents both focus and AT exposure simultaneously, making this conflict impossible by design: // Instead of: modal.setAttribute('aria-hidden', 'true'); // Use: modal.setAttribute('inert', ''); Environment NodeBB: 4.10.0 Browser: reproducible in Chrome, Firefox, Edge Impact: accessibility regression for keyboard and screen reader users

Hi everyone, I’ve developed a code snippet to improve visual differentiation in NodeBB chats. The code was initially drafted by AI and is currently a proof-of-concept. It’s functional but needs further optimization and design refinement to meet community standards. I’m sharing this because I believe it could be a valuable addition to the platform. I would love for the community to help refine the logic and explore integrating it as a feature or a plugin. Looking forward to your feedback! @julian @baris /* --- עיצוב בסיסי לצ'אט --- */ /* רקע כללי של הצ'אט */ [class="modal-content ui-resizable"], [component="chat/main-wrapper"] { background-image: url(https://good-link.org/assets/uploads/system/whatsapp-wallpaper-39.jpg); position: relative; } /* כותרת עליונה של הצ'אט הראשי */ [component="chat/header"] { background-color: #075E54 !important; color: #ffffff !important; font-weight: bold; font-size: 16px; text-align: center; padding: 10px; } [component="chat/header"] *, [component="chat/header"] i, [component="chat/header"] svg, [component="chat/header"] button { color: #ffffff !important; fill: #ffffff !important; stroke: #ffffff !important; } /* כותרת צ'אט מוקטן בצד */ .modal-header.d-flex.gap-4.justify-content-between.ui-draggable-handle { background-color: #075E54 !important; color: #ffffff !important; padding: 10px; font-weight: bold; font-size: 14px; } .modal-header.d-flex.gap-4.justify-content-between.ui-draggable-handle * { color: #ffffff !important; fill: #ffffff !important; stroke: #ffffff !important; } /* --- עיצוב הודעות (בועות צ'אט) --- */ /* הגדרות כלליות להודעה: מיקום, רוחב מקסימלי, מרווח תחתון */ [component="chat/message"] { position: relative; margin-top: 9px; margin-bottom: 30px !important; padding: 5px 17px; /* ריווח פנימי אנכי ואופקי בסיסי */ max-width: calc(100% - 70px); /* השארת מרווח כולל של 70px (10 בצד אחד, 60 בצד שני) */ width: fit-content; /* התאמת רוחב לתוכן */ clear: both; /* למנוע בעיות גלישה */ } /* הודעות של אחרים (בועה לבנה, יישור לימין ב-RTL) */ [data-self="0"][component="chat/message"] { background-color: #fff; border-radius: 20px 20px 0px 20px; /* פינה תחתונה-ימנית חדה */ margin-left: 10px !important; /* מרווח קבוע מהצד השמאלי */ margin-right: auto !important; /* דחיפה לימין */ /* padding-bottom: 5px; ריווח תחתון פנימי קטן - הועבר לכלל הראשי */ } /* ההודעות שלי (בועה ירוקה, יישור לשמאל ב-RTL) */ [data-self="1"][component="chat/message"] { background-color: #e7ffdb; border-radius: 20px 20px 20px 0px; /* פינה תחתונה-שמאלית חדה */ margin-left: auto !important; /* דחיפה לשמאל */ margin-right: 10px !important; /* מרווח קבוע מהצד הימני */ padding-left: 21px !important; /* ריווח פנימי שמאלי קצת יותר גדול אם צריך */ /* padding-bottom: 5px; ריווח תחתון פנימי קטן - הועבר לכלל הראשי */ } /* הודעות ללא הפרדה (רצופות) */ [component="chat/message"][data-break="false"] { margin-top: 2px; /* הקטנת מרווח עליון */ margin-bottom: 2px !important; /* הקטנת מרווח תחתון */ } /* עיצוב טקסט מצוטט בתיבת הקלט */ .w-100.flex-grow-1.flex-nowrap.position-relative.d-flex.rounded-2.border.border-secondary.p-1.align-items-end textarea::before { content: "> "; color: #007bff; /* צבע ציטוט */ font-weight: bold; } /* --- מיקום אימוג'ים (Reactions) מתחת להודעה --- */ [component="chat/message"] [component="message/reactions"] { position: absolute; bottom: -22px; /* מיקום מתחת לבועה (שחק עם הערך לפי הצורך) */ z-index: 5; display: flex; flex-wrap: wrap; gap: 4px; max-width: 80%; background-color: rgba(240, 240, 240, 0.85); padding: 2px 5px; border-radius: 10px; box-shadow: 0 1px 2px rgba(0,0,0,0.1); } [data-self="0"][component="chat/message"] [component="message/reactions"] { left: 5px; right: auto; } [data-self="1"][component="chat/message"] [component="message/reactions"] { right: 5px; left: auto; justify-content: flex-end; } /* --- מיקום כלי ההודעה (Reply, React, More) בצד --- */ [component="chat/message"] .controls { position: absolute !important; top: -10px !important; bottom: auto !important; opacity: 0; pointer-events: none; transition: opacity 0.2s ease-in-out, transform 0.1s ease-in-out; transform: translateY(3px); background-color: rgba(250, 250, 250, 0.97) !important; border-radius: 15px !important; padding: 5px 8px !important; box-shadow: 0 2px 5px rgba(0,0,0,0.2) !important; border: none !important; z-index: 10; display: flex !important; gap: 5px; } [component="chat/message"]:hover .controls { opacity: 1; pointer-events: auto; transform: translateY(0); } [data-self="0"][component="chat/message"] .controls { right: -15px !important; /* מיקום מימין להודעה (שחק עם הערך) */ left: auto !important; } [data-self="1"][component="chat/message"] .controls { left: -15px !important; /* מיקום משמאל להודעה (שחק עם הערך) */ right: auto !important; } [component="chat/message"] .controls .btn { padding: 2px 4px !important; background: none !important; border: none !important; line-height: 1; box-shadow: none !important; border-radius: 5px; transition: background-color 0.15s ease; } [component="chat/message"] .controls .btn:hover { background-color: rgba(0, 0, 0, 0.1) !important; } [component="chat/message"] .controls i, [component="chat/message"] .controls svg { color: #444 !important; fill: #444 !important; stroke: none !important; width: 18px; height: 18px; vertical-align: middle; }

[image: 1774356228471-1234633f-78a8-464c-82fe-57d352ccad19-image.jpeg] I am getting same digest email 3 times simulteneouly daily? what is the reason ? i am not able to find it. It should receive only one time if Digest is enabled.

Hi everyone, I'm having some trouble managing my NodeBB instance. I’ve noticed that I cannot successfully run updates or perform backups directly through the terminal. It seems I am forced to log in to the server/SSH directly to get these tasks done. Could someone explain why these actions aren't working via the terminal interface and why server-level access is required for these specific processes? Thanks for the help!

I am implementing tribe/clan pages for a video game. It should be something like categories but It would have another tab on the sidebar, own route and own read only display fields (much alike my previous question but for the tribe page). And of course I should be able to fetch all the tribe data through some hook. How do you do that?

Hello. I'm implementing a plugin that integrates forum to a system. I need the plugin to show some extra user fields that are pulled from the database, much like the Preferred code editor in this forum, but read only. Is there a plugin for that out there?

Hello everyone, I'm the administrator of a NodeBB instance (4.9.1) and I also display other remote categories within that instance (the communities of a Lemmy instance I manage). I would like to point out that I have not opened an issue on Github because I am not sure whether the problem in question is a bug or just the consequence of a deliberate choice by the developers. I've noticed that sometimes, when a Fediverse user posts a mention of a Lemmy community, while the Lemmy server correctly categorizes that conversation, the NodeBB server displaying the remote category may not "understand" that the post belongs to the community in question. In the past, when I noticed these anomalies, I could resolve the issue by "moving the thread" using my administrator privileges. When I moved the thread, I was only shown the local category tree, but I could search for remote categories using the search function. Not anymore. Has something changed, or am I misremembering? I hope I explained myself correctly, but since I use an automatic translator, I may have explained the problem incorrectly.

Hi everybody i'm a new member here I have a few questions- First, is there a age limit for this site? I just wanna make sure I'm not breaking rules by being here Also does this site support dms? I saw a few posts saying they disappeared I mostly came here because I wanted a few contacts to just yap iykwim :') Also uhm. Hi i'm Jaye!! My pronouns are He/It and i'm transmasc nice to meet all of you guys!!

Hello friends A user on our forum reported that when a banned user tries to log in to the forum, the reason for the ban is returned even if the correct password is not entered, allowing anyone to check why another user was banned without having permission to do so. This bug is a serious privacy security breach, and I would appreciate it if you could fix it. I used machine translation because I don't speak English, so please forgive me if there are any linguistic errors Thank you very much

Hi all, So I'm on Nodebb v3.10.3 and previously I have successfully restored the database to local instances for testing. However, I've been trying to migrate the forum to a different server (My MongoDB is setup and a db dump has been restored). However, whenever I try to run ./nodebb build, it stops after installing dependencies. There are no other logs. When I was trying again by performing ./nodebb setup (instead of build), I did see the following after providing my newly restored DBs URI: 2026-03-20T09:03:03.067Z [9971] - error: admin:username 2026-03-20T09:03:03.067Z [9971] - error: admin:password 2026-03-20T09:03:03.067Z [9971] - error: admin:password:confirm 2026-03-20T09:03:03.068Z [9971] - error: admin:email I was wondering how to provide these info/overwrite in the DB/config file? Thank you

Hi everybody, With spring around the corner (it is currently a balmy 5°C here right now), it's time to get crackin' on a new release of NodeBB! We focused on a lot of user experience updates this time around, along with tweaking the new /world page that was introduced in v4.9.0. In the backend, lots of optimizations were implemented, which make federation processing (and day-to-day maintenance) faster. Here's what you can expect from v4.10.0... Updates to the /world page The /world page got a makeover in v4.9.0, showcasing a more timeline-based feel. It more accurately represents the breadth of content available on the open social web, such as microblogging, in addition to long-form text (blogs), media-focused items, and everything in between. We focused on UX updates to this page: New sorts are available: You can now view just local content, as well as all known content. The default sort continues to be "your followers", but also includes local content now as well, because you are also tracking those categories! Guests were barred from /world in v4.9.0, but this is now opened up again. Their view of the /world page shows only local posts. The /world page can now be set as a default home page. Duplicate items were showing up when scrolling down /world (especially on very active timelines) Uploaded images were showing up in the thumbnail/card headers, even if they were embedded in the post itself. The header is now restricted to topic thumbnails (and post attachments, which only occur with remote posts) Posts are now height-restricted, so long posts don't take up an inordinate amount of space. A "show more" button is available to expand posts in-timeline. The "quick create" editor at the top of this page now also lets you choose a category to post to. Administrators can update the default value as desired. It defaults to World/Uncategorized. Alt Text now federating outward Alt text was always supported in NodeBB, but this was not federated outward to remote instances. This is now supported for uploaded images and externally-linked images. Topic thumbnails do not support alt text at this time. Soft redirects of remote content Users unfamiliar with NodeBB were often surprised to see their content cached by NodeBB, despite this being how federation works. In order to reduce surprise, any guest navigating directly to a remote post or remote user will be soft-redirected out to the original source. This goes hand-in-hand with the topic-restriction feature in v4.9.0. ActivityPub Outboxes published For ActivityPub developers, we now publish outboxes as of this version. More profile pics! @baris improved the avatar handling code so that NodeBB now remembers your last three used avatars, allowing you to toggle between them. You will no longer need to upload new pictures if you want to switch between previously-used avatars! Follow counts better synchronized @[email protected] reported awhile back that follow counts in user pages were off. The logic was updated and should be back in sync with the real values once you follow/unfollow a user.

Nostr NIP-07 Login Support https://github.com/nostr-protocol/nips/blob/master/07.md

We were fiddling with the markdown options to see if everything worked - and while a few minor issues I could fix with css (such as checkbox lists keeping the bullet) [image: 1773919256983-af74d19f-7dc1-4733-994f-d3b277196a5a-image.jpeg] For reference in case others want to know how I attempted to fix it: // Change all ul li within post content to "∙" .content ul li::marker { content: "∙"; } // Do not change ordered lists to "∙",but keep them as they were. ol li::marker { content: initial; } // Remove bullets from bullted checkbox lists. li:has(.plugin-markdown input[type="checkbox"])::marker { content: none !important; } Result: [image: 1773919512795-f0c1ecf4-73e0-41da-9eb4-96a5fd1e5de5-image.jpeg] But the major reason I am posting is the grouped codeblocks: https://github.com/MinecraftForgeFrance/nodebb-plugin-extended-markdown/issues/18 [image: 1773919418176-94b2768f-5e99-4d6c-be23-dab2354c4781-image.jpeg] I posted in the github issues, but no reply. I am not sure if the project is simply inactive, or the devs just simply haven't gotten around to it - but I thought it was worth a shot posting here as well.

Hello, I changed my base URL by re-running the setup and it seems to have updated, however in odd locations like RSS and following from other social platforms it’s still inputting local host instead of the new URL. How can I ensure this gets updated everywhere?

Is it possible to share prefilled topic and text in nodebb something along like this: domain.com/compose?cid=123&topic=Some topic&body=Some short text read more [link](https://domain.com)

As a new user of NodeBB I didn't find much info on getting the email side of the application working. Now that it is working well, here is how I did it using GMAIL Create a new Gmail account or use an existing one. (if you use an existing account, your email address will be seen by your Nodebb users) Turn on "two step verification" for this account by visiting your Gmail security page and clicking on the "Signing in to Google". You will receive a text message or two to verify the settings change. Once "Two Step Verification" is enabled, goto this link Sign in using App Passwords and have a read. then click on this link to create an "app password", copy and save it for later. Now we can go back to the NodeBB settings and choose "Email". Enter your email address as the "Email address" in NodeBB "From Name" can be anything you like Enable the slider "Route emails through a GMAIL account" Username is your GMAIL email address Password is the "app password" you generated above. Save the config and then restart NodeBB Come back to the Nodebb email settings and press the test button, you should receive an email All done! - ask any questions if you have them.

[Plugin] Super Admin Chat Control - Monitor and Manage All Conversations Hi everyone, I've developed a new plugin called Super Admin Chat Control. This plugin is designed for forum administrators who need deeper oversight into the messaging system for moderation purposes. It allows administrators to view, manage, and interact with any chat room on the forum, even if they aren't a participant. Key Features: Global Access: View any private or group conversation directly. Moderation Power: Administrators can edit or delete any message within the chat system. Quick Audit: Adds a "View Chats" link to the user profile menu for admins. Smart Presence: Admins can view room history without being permanently added as members, keeping room statistics accurate. Bilingual UI: Full support for English and Hebrew interfaces. How it works: The plugin hooks into NodeBB's messaging system to elevate admin permissions. It overrides core functions like Messaging.canEdit, Messaging.canDelete, and Messaging.canViewMessage to ensure administrators have the necessary access for effective moderation. Technical Details: Compatibility: NodeBB ^3.0.0 or ^4.0.0. Hooks used: filter:messaging.isRoomOwner, filter:messaging.canReply, filter:messaging.loadRoom, and more. Installation: Install the plugin via your terminal: npm install nodebb-plugin-admin-chats Activate the plugin in the NodeBB Admin Control Panel (ACP). Restart NodeBB. Repo & Issues: You can find the source code here: https://github.com/palmoni5/nodebb-plugin-admin-chats Feel free to leave feedback or report issues on GitHub!

This table is generated dynamically. If you wish to submit your NodeBB, please visit this page. Click here to see a full list with more details.

Hi! I'm interested in knowing, is there a nodebb plugin for WordPress? I like your design, and I'm really interested in integrating it into my website in a way that integrates with WordPress. Is there such a plugin? Is there something in development? Thanks.

Hello. My login strategy implements creating account if it doesn't exist: uid = await User.create({username: player.playerName, email: player.emailAddress}); but "email taken" error occurs. Is this possible to allow multiple accounts with the same email? If I somehow set this in the database, for example, through User.setUserField, will anything break or is this just a way to prevent multiaccounts?