MTO- NodeBB on Elestio
-
I have started to install some anti-spam stuff, so if you want to try banning someone, you should do it with one of the existing spambots as hopefully there won't be a lot more.
Otherwise you can ban Fred if you want to try, but please let me know if you do as I need him.
Multitool.org Anti‑Spam Setup Log — October 14, 20261. Installed & opened Spam‑Be‑Gone
You accessed the NodeBB admin panel:
Admin → Plugins → Spam Be Gone
You reviewed all available tabs:
- Akismet
- Project Honeypot
- Google reCAPTCHA
- StopForumSpam
- hCaptcha
2. Configured Project Honeypot (successfully)
Steps completed:
- Logged into Project Honeypot
- Navigated to Services → HTTP:BL Access
- Retrieved your 12‑character access key
- Entered it into Spam‑Be‑Gone under Project Honeypot → Honeypot API Key
- Enabled Honeypot
- Saved changes
Result:
Project Honeypot is active and working.
It silently checks IPs during registration with zero user friction.
3. Attempted to enable StopForumSpam (SFS)
You enabled SFS but left the API key blank.
Your version of Spam‑Be‑Gone requires an SFS API key if SFS is enabled.
This caused the error:
“Error — Empty fields not allowed!”
You confirmed:
- Honeypot tab had no empty fields
- SFS tab had no required fields except the optional API key
- All CAPTCHA tabs were disabled
Conclusion:
The error was caused by SFS being enabled without an API key.
4. Disabled StopForumSpam to clear the error
You disabled SFS.
Result:
The error disappeared immediately.This confirmed the plugin’s behavior:
- SFS must have an API key if enabled
- Leaving it blank triggers validation failure
5. Current active anti‑spam configuration
As of the end of the session:
Enabled- Project Honeypot (with valid API key)
Disabled- StopForumSpam (temporarily)
- Akismet
- Google reCAPTCHA
- hCaptcha
This configuration is:
- Fully functional
- Invisible to users
- Error‑free
6. Plan for later (after domain switch)
You decided to wait until the forum is running on its final, correct domain before enabling SFS.
When ready:
Steps to re‑enable SFS:
- Log into StopForumSpam
- Go to User Panel → API Keys
- Copy your API key
- Paste it into Spam‑Be‑Gone → StopForumSpam
- Enable SFS
- Save changes
This will give you:
- IP checks
- Email checks
- Username checks
- Zero friction for new members
7. Overall outcome
You now have:
- A clean, stable anti‑spam setup
- No signup friction for legitimate users
- Strong invisible protection via Honeypot
- A clear path to enabling SFS later
- No plugin errors
Def
-
For some reason i cannot reply to messages, i tried to wait but it doesnt send message even tho i tried multiple times. Site is now bit messy to use on mobile cannot open threads where messages has been sent without changing to desktop mode
-
You are right- the Submit button doesn't seem to work.
smurf.
I'll get on that ASAP.
Def
-
- User Intent — Diagnose and restore broken compose submit actions, implement a permanent mobile-friendly duplicate Submit button below the composer, retain custom profile card structures, restore the display of user post counts in post sidebars, and apply readable, high-contrast light and dark styling to post header Quote and Reply buttons.
- Key Information —
- Core compose routes fire
action:composer.enhanceviaforum/compose. - NodeBB core
client.jswas patched fromrequire(['composer'])toapp.require('composer')because globalrequirewas unavailable. composer/scheduler.jswas patched with a null-check guard oncancelBtn.addEventListenerto prevent unhandledTypeErrorcrashes when.dropdown-item.cancel-schedulingwas absent from the DOM.- Theme client scripts must be declared inside
plugin.json(such asstatic/lib/mto-topic-actions.js) for NodeBB to compile them into the active bundle. - Post header Quote and Reply buttons are rendered in
templates/partials/topic/post.tplusing.mto-btn-quoteand.mto-btn-replyclasses, requiring explicit styling across light and dark mode intheme.scss. - Author sidebar metadata is rendered in
templates/partials/topic/post.tplunder<aside class="mto-post-author">and supports{formattedNumber(posts.user.postcount)}.
- Progress & Completed Changes —
- Core Engine & Scheduler Patches: Verified patches to
client.jsandscheduler.jsinnode_modulespreventing silent client JS execution failures. - Duplicate Mobile Submit Button: Implemented the duplicate submit button container inside
static/lib/mto-topic-actions.jsonaction:composer.enhanced, verified working natively on compose views. - Quote & Reply Button Restyling: Added custom SCSS in
theme.scsstargeting.mto-header-tools .mto-btn-quoteand.mto-btn-reply, restoring sharp border definition, solid background contrast, and crisp icons across both light and dark themes. - Author Post Count Restoration: Added
<div class="mto-post-author-stats">displayingPosts: {formattedNumber(posts.user.postcount)}directly intotemplates/partials/topic/post.tplbeneath the author groups container, along with matching styles intheme.scss. - Asset Compilation & Container State: Completed
nodebb build clientand verified clean asset compiles followed by container restarts.
- Active Context / Next Session — All primary functional fixes, duplicate submit controls, post count metadata displays, and header button styling updates are successfully compiled, verified, and running in production. Optional polish items left for the next session include suppressing the automatic
@usernamepre-population when clicking per-post Reply buttons and any remaining profile sidebar layout enhancements.
-
I am working on the Treasury module now- if there are any more functional/operational changes you guys think should be made, let me know. Currently it appears as if the forum is functioning as a forum should.
Def
-
I cut it a bit short tonight- these nights seem to be catching up to me and I am having trouble focusing. But, here is where I am at:
Development & Deployment Log: NodeBB Treasury & Membership Plugin
Date: October 16, 2026
Environment: NodeBB v4.16.2 running inside Docker (
app-nodebb-1) on Elestio host (nodebb-vklpj-u73921) backed by Redis (app-redis-1). Staging URL:[https://multitool.ninja](https://multitool.ninja)(production domain cutover target:multitool.org).
1. Summary of Work Completed
A. Sidebar Widget Fixes & Visual Polish
-
Widget Crash Resolution: Resolved an unhandled
TypeError: Cannot read properties of undefined (reading 'renderAsync')inlibrary.jsby capturing the Expressappinstance duringplugin.init({ app, router, middleware })and wrappingapp.renderin a native Promise. -
Theme Icon & Contrast Styling:
-
Removed the heart icon from the Make A Donation button and replaced it with a wrench/screwdriver tool motif (
fa-solid fa-screwdriver-wrench). -
Locked button text and icons to deep charcoal (
#141414 !important; font-weight: 700;) on an amber/yellow background (#fca311), eliminating washed-out white text in dark mode. -
Adjusted widget table numbers to soft muted body colors (
var(--bs-body-color)/text-body fw-semibold) instead of harsh pure white. -
Header Simplification:
-
Removed the misaligned, clipped inline
fa-vaulticon from the top of the card. -
Eliminated the redundant uppercase
DONATIONSheader, leaving a clean, centered title: Operational Funds.
B. Member Privacy & Forum Scoping
-
Restricting Member-Facing Treasury View (
/treasury
-
Removed all public access to raw transaction ledgers, individual line-item payouts, and internal account balance sheets to protect financial privacy.
-
Transformed
/treasuryinto a focused member contribution and goal progress page featuring monthly target metrics, quick-donation buttons, and a link to/subscriptions. -
Retained the double-entry ledger, project allocation tracking, and complete audit trail strictly inside the Admin Control Panel (
/admin/plugins/treasury). -
Donation Calculation Scoping:
-
Updated
getForumDonationsMonthTotal()inlibrary.jsto strictly tally credits wherecategory === 'donation'orcategory === 'forum-donation'for the current calendar month. -
Excluded paid membership fees (
category: 'subscription'), initial seed funding, merchandise sales, and cross-site external income from the public progress bar to maintain contest and giveaway eligibility rules. -
Updated the ACP transaction posting modal to distinguish between Forum Donation, Seed / Opening Balance, and Merch / External.
C. PayPal Integration & Domain Agnosticism
-
Public Donation Form Buttons:
-
Built direct donation form actions ($10, $25, $50, $100, and Custom) on
/treasurysubmitting directly to PayPal's standard checkout via POST, avoiding brittle inline client-side scripts. -
Tagged submissions with
custom="{uid}:donation"for backend tracking. -
Subscriptions Store Integration:
-
Added direct PayPal checkout forms to tier cards on
/subscriptionspassingcustom="{uid}:{planId}". -
Backend IPN Listener (
/api/v3/plugins/treasury/ipn
-
Configured an unauthenticated POST webhook that performs an immediate 200 OK receipt and executes an asynchronous
cmd=_notify-validatehandshake back toipnpb.paypal.com. -
Automatically joins members to designated NodeBB usergroups upon confirmed payment of subscription plans.
-
Logs verified donation transactions directly into the default financial ledger in integer cents.
-
Live Merchant Verification:
-
Updated the template merchant identity from placeholder
donations@multitool.orgto the live account (Defender Web & Tool), successfully validating checkout generation for$10.00 CAD. -
Dynamic Domain Resolution for Production Cutover:
-
Injected
baseUrl = nconf.get('url')into both controllers and templates. -
All form
returnandnotify_urlparameters now dynamically bind to whatever domain is active inconfig.json(multitool.ninjaduring testing, transitioning tomultitool.orgat launch without code edits). -
Crash Fix (
ReferenceError: donationsCents is not defined
-
Resolved variable naming mismatch in
library.jsand wrapped controllers in robusttry/catcherror boundaries to prevent worker process drops and 502 Bad Gateway proxy errors.
2. Technical Architecture & File Reference
File Path Description /opt/app/nodebb-plugin-treasury/library.jsCore plugin entrypoint: controllers, routes, widget renderer, PayPal IPN listener, and hourly subscription expiry cron. /opt/app/nodebb-plugin-treasury/lib/db.jsRedis data access layer: double-entry ledger, subscriptions, projects, and audit logs. /opt/app/nodebb-plugin-treasury/templates/treasury.tplPublic donation and monthly operational goal view. /opt/app/nodebb-plugin-treasury/templates/subscriptions.tplPublic membership tiers and active subscription status store. /opt/app/nodebb-plugin-treasury/templates/widgets/treasury-funds.tplGlobal sidebar widget template for operational funds progress. /opt/app/nodebb-plugin-treasury/templates/admin/treasury-overview.tplACP management interface for ledger, accounts, plans, and audit logs. /opt/app/backups/treasury_*Local restore point containing compressed plugin source and Redis database dump.
3. Next Steps & Implementation Plan
Phase 1: End-to-End Payment & Webhook Verification
- Configure PayPal IPN in Dashboard: In the live PayPal merchant account, set the Instant Payment Notification (IPN) URL to
[https://multitool.ninja/api/v3/plugins/treasury/ipn](https://multitool.ninja/api/v3/plugins/treasury/ipn)and enable IPN delivery. - Live Test Transaction ($1.00 or test tier): Run a live subscription or direct donation test using a secondary PayPal account to verify that:
- The payment completes successfully on PayPal.
- The IPN callback receives a 200 OK and validates with
VERIFIED. - The test user is automatically added to the target group (e.g., Charter Members) without admin intervention.
- The amount is credited to the internal ACP ledger in integer cents.
Phase 2: Expiration & Renewal Notifications
- Renewal Reminder Alerts: Hook into the hourly background cron in
library.js(TreasuryDB.checkExpiredSubscriptions) to send automated NodeBB in-app notifications and emails to members 7 days and 1 day prior to subscription expiration. - Grace Period / Expiration Handling: Confirm the automated group removal (
groups.leave) fires accurately whenexpiryDate <= nowwithout breaking permissions.
Phase 3: Final Production Polish & Cutover Checklist
- Seed Transaction Database Cleanup: Using
redis-clidirectly insideapp-redis-1, clean up the category tag on the initial hypothetical seed transaction so the public widget begins cleanly at$0.00for live launch. - DNS Cutover Verification: When switching from
multitool.ninjatomultitool.org: - Update
urlin/usr/src/app/config.json. - Update the IPN URL inside the PayPal merchant settings to
[https://multitool.org/api/v3/plugins/treasury/ipn](https://multitool.org/api/v3/plugins/treasury/ipn). - Run
./nodebb buildand restart container.
-
-
Will there be a Moderate button at the top of the page for moderation log and reported posts ?
-
@SteveC said:
Will there be a Moderate button at the top of the page for moderation log and reported posts ?I am hoping so.

I have been noticing that the options for moderators are either well hidden or kind of limited. Looking into making it easier for you guys to do your thing is high on my list.
Def
-
Sorry haven't been following much.
I can generate sfs key, for when domain migrates.
I haven't made any progress on my local migration attempt.
Somehow my docker setup is confusing me and I seem to have some sort of duplicate running, preventing me from installing scripts on my local copy of nodebb.
Gemini wasn't particularly helpful to figure it out yet.
Also I should probably apply all your updates once content is imported to see if it's working correctly.
Don't be afraid to leave some crap out for implementation later, that is if anyone noticed it is missing. The cleaner the base install the less headaches keeping up to date.
-
-
@Grant Lamontagne said:
I am working on the Treasury module now- if there are any more functional/operational changes you guys think should be made, let me know. Currently it appears as if the forum is functioning as a forum should.Def
How about a Like button with emojis ?
Also, did we lose notifications, profile editing ?
-
Finally got some progress with my local testing.
SMF mysql restored (2gb)
nodebb functional
Import plugin functional
started import this morning;1.5h for 9500 users
1h for nearly 300000 PMs
now into topics, it's been going for hours...I don't have any attachments setup for this first test, wanted to see how we go first with posts before I give it 50gb of files to dig through.
It seems like it doesn't like repeated emails, so if there are profiles with the same email, one will override.
Also, I believe passwords will not migrate; they will need to be regenerated and users will need to use recovery to update. For this PLEASE try to put some sort of notice/newsletter that all users ensure their profile has an updated email or they will be blocked when we migrate.
Additionally based on the experience so far, looks like we will have to put the current site in read only mode, backup, download, migrate, create a db/attachments backup and upload migrated forum to new platform. This will take a few days, unless there is some way to just sync latest... still early to say.
-
So it was in a restart loop.
89k topics took about 40 min once I got the hiccups sorted, it's now about 160k through the 2.4million replies, estimated time 13-17h...
We definitely need a few days downtime to migrate all posts.
Attachments is likely to be even more.
-
I am holding off on any further modifications to NodeBB until Micah says it's clear to continue.
Def
-
My testing will not affect the live setup.
Posts completed during the night, now there's some post import bbcode to markdown that is supposed to work, but I don't see any activity yet... But I had to go to work...
-
Yes, work is definitely a four letter word.
Still, great job man.

Def
-
Donations module is now set up.
================================================================================
ENGINEERING DAILY LOG: NODEBB TREASURY & MEMBERSHIP PLUGINDate: October 21, 2026
Environment: NodeBB v4.16.2 on Elestio (nodebb-vklpj-u73921)
Containers: app-nodebb-1 (NodeBB), app-redis-1 (Redis)
Host Root: /opt/app
Staging URL: https://multitool.ninja (Target: multitool.org)
Git Commit: a91b6f5 ("feat(treasury): complete plugin verification, bind mount and auto-link")
- EXECUTIVE SUMMARY
Successfully verified, hardened, and locked in the end-to-end implementation
of the custom Treasury & Subscriptions plugin (nodebb-plugin-treasury). All
ledger accounting, IPN webhooks, automated group provisioning, and expiration
cleanup jobs were validated in the live container. Docker Compose bind-mounts
and entrypoint startup scripts were permanently wired so the module survives all
future Elestio updates, rebuilds, and container restarts.
- KEY ARCHITECTURE & LOGIC
-
Webhook Route:
Mounted at /treasury/ipn directly via Express router to cleanly bypass
NodeBB's core /api/v3/* schema validation requirements. -
Double-Entry Ledger Math:
All financial amounts and account balances are stored and calculated strictly
in integer cents in Redis (lib/db.js) to avoid floating-point drift. -
Subscription Indexing & Group Provisioning:
When a valid subscription IPN is received:- Writes sub details to Redis hash: treasury:sub:<uid>:<planId>
- Indexes expiration in sorted set: treasury:subscriptions:byExpiry
- Adds user to target group: groups.join(plan.groupName, uid)
- Tracks user sub keys in: treasury:user:<uid>:subs
-
Expiration & Revocation Engine:
- Hourly background timer triggers: TreasuryDB.checkExpiredSubscriptions()
- Queries sorted set using range: ['-inf' to now] via getSortedSetRangeByScore
- Calls NodeBB core: groups.leave(sub.groupName, uid)
- Purges hashes and keys: treasury:sub:* and all tracking sets.
- VERIFICATION & HARDENING STEPS COMPLETED
Security Hardening:
- Removed all diagnostic bypass headers ('x-treasury-test').
- Enforced strict requirement for PayPal 'VERIFIED' handshakes.Expiry Engine Testing:
- Fixed sorted set query lower-bound parameter in lib/db.js to use '-inf'.
- Tested expired subscription record for UID 3 in 'Charter Members'.
- Verified complete automated removal from NodeBB user group.
- Verified cleanup of all Redis hash keys and sorted set indexes.
- Confirmed active subscriptions (UID 1) remained intact and untouched.Test Data Cleanup:
- Purged ephemeral mock transactions and test subscription hashes from Redis.
- DEPLOYMENT & CONTAINER PERSISTENCE SETUP
To ensure zero data loss during container recreation or image pulls:
-
Host Directory:
Source repository lives at /opt/app/nodebb-plugin-treasury -
Docker Compose Bind-Mount (/opt/app/docker-compose.yml):
Added under app-nodebb-1 service volumes:- ./nodebb-plugin-treasury:/usr/src/app/nodebb-plugin-treasury
-
Startup Auto-Symlink (/opt/app/entrypoint.sh):
Added startup routine to dynamically link into container node_modules:TREASURY_SRC=/usr/src/app/nodebb-plugin-treasury
TREASURY_DST=/usr/src/app/node_modules/nodebb-plugin-treasury
if [ -d "$TREASURY_SRC" ]; then
ln -sfn "$TREASURY_SRC" "$TREASURY_DST"
echo "MTO NodeBB startup: linked nodebb-plugin-treasury into node_modules."
fi -
Verification:
Recreated container viadocker compose up -d --force-recreate nodebb.
Verified symlink inside container:
/usr/src/app/node_modules/nodebb-plugin-treasury -> /usr/src/app/nodebb-plugin-treasury -
Git Tracking:
Committed all 15 plugin files, templates, entrypoint, and compose configs
under commit a91b6f5.
STATUS: COMPLETE & PRODUCTION-READY
-
Summary of What We Hardened on NodeBB TonightComposer Runtime Restored & Persisted: Added the null-check to scheduler.js and baked it directly into /opt/app/entrypoint.sh so restarts/rebuilds never break the composer again. Ghost Plugin Cleaned: Purged nodebb-plugin-poll from Redis plugins:active, eliminating asset compiler warnings and missing module errors.Theme Repository Synchronized: Committed the composer duplicate submit button, post count metadata, and button styling cleanly into git. Registration Hardened: Active hCaptcha challenge enabled on registration without requiring SMTP email verification. Brute-Force Throttle Active: Enforced a 60-second cooldown after 5 failed login attempts to prevent credential stuffing.
-
================================================================================
MULTITOOL.ORG (MTO) MIGRATION & SYSTEM AUDIT LOG
Date: October 28, 2026
Host Environment: nodebb-vklpj-u73921 (/opt/app)
Container: app-nodebb-1 (NodeBB v4.16.4 on Node.js v24.22.1 / Redis)- SUMMARY OF CHANGES & ACTIONS COMPLETED
A. FULL SYSTEM & COMPONENT AUDIT
- Audited active plugins in Redis (
plugins:active) and the physical filesystem. - Verified 5 custom MTO components are present, validly formed, and loaded:
- nodebb-plugin-mto-bbcode (legacy SMF BBCode parser, quick-mod bar, client scripts)
- nodebb-plugin-mto-messages (custom private messaging module)
- nodebb-plugin-mto-awards (badges / user awards system)
- nodebb-plugin-treasury (ledger, subscriptions, and PayPal IPN listener)
- nodebb-theme-mto (custom Harmony-based skin, brand header, widget areas)
- Audited all theme template anchors against registered Express backend routes.
Confirmed that header buttons (Home, Search, Admin, Profile, Messages,
Bookmarks, Members, Badges) map to live route endpoints.
B. PRIVATE MESSAGES (MTO-MESSAGES) NAVIGATION & UX FIX
- Problem Identified: Clicking "MESSAGES" in the top navbar failed silently;
only right-clicking "Open in new window" worked. - Root Cause: NodeBB's single-page router (Ajaxify) attempted to intercept
the custom route (/mto-messages) without an in-memory client template,
halting page transition. - Solution Implemented:
- Patched
brand.tplinside the custom theme to include an inline
navigation bypass:
onclick="window.location.href=this.href; return false;" - Now standard left-clicking routes cleanly and directly into the inbox.
- Patched
C. REAL-TIME UNREAD PRIVATE MESSAGE TRACKING & BELL NOTIFICATIONS
- Problem Identified: Unread counters remained static or failed to clear.
- Solution Implemented in
nodebb-plugin-mto-messages/library.js:- Implemented per-thread read timestamps in Redis:
Key:mto:pm:read:<threadId>:<uid> - Thread views at
/mto-messages/:threadIdautomatically update this
timestamp toDate.now(). - Re-engineered endpoint
GET /mto-messages/unread-countto dynamically
compute unread threads where latest post timestamp > user's lastRead timestamp. - Added NodeBB bell notification dispatch on message send (
notifications.create
andnotifications.push) to alert recipients across desktop/mobile. - Injected a lightweight client poller in
nodebb-plugin-mto-bbcode/static/client.js
hooked toaction:ajaxify.endand a 60-second interval to keep the red
navbar badge (.mtorg-pm-count) updated in real time.
- Implemented per-thread read timestamps in Redis:
D. TREASURY PLUGIN & MULTI-SITE DONATION FEDERATION
- Audited the "OPERATIONAL FUNDS" sidebar widget; verified it is dynamically
driven bynodebb-plugin-treasuryviarenderFundsWidgetrecalculating
monthly targets, dates, receipts, and percentage progress against ledger entries. - Re-engineered PayPal IPN listener (
POST /treasury/ipn) in
nodebb-plugin-treasury/library.js:- Enhanced IPN
custompayload parsing fromtargetUid:actionTypeto:
targetUid:actionType:sourceSite - Added fallback extraction from
item_nameto auto-detect "SAKSelector"
or "EDC-TV". - Updated
TreasuryDB.recordTransactionto recordprojectId('sakselector',
'edctv', or 'forum') and append site origin tags to transaction descriptions
(e.g.,PayPal Donation [SAKSELECTOR]: donor@email.com). - Verified that incoming satellite donations maintain
category: 'donation',
allowing external contributions to automatically advance the forum's
operational funds thermometer.
- Enhanced IPN
E. PERSISTENCE & HARDENING (PREVENTING REGRESSION ON REBOOT/UPDATE)
- Converted
node_modulescopies of custom plugins and theme into persistent
symbolic links pointing directly to the root source directories. - Created host-level external backups in
/opt/app/mto-custom-backup/to protect
custom code against container recreations or image resets. - Created a one-line self-healing restoration script at
/opt/app/restore-mto.sh.
================================================================================
2. SATELLITE SITE INTEGRATION PAYLOAD SPECIFICATIONSTo feed incoming donations from SAKSelector and EDC-TV into the MTO Treasury,
ensure external forms use the following parameters:- POST Target URL: https://www.paypal.com/cgi-bin/webscr
- Business: admin@def-it.com
- IPN Notification URL (notify_url): https://multitool.ninja/treasury/ipn
SAKSelector Payload:
- item_name: SAKSelector Donation
- custom: 0:donation:sakselector
- return: https://sakselector.org
EDC-TV Payload:
- item_name: EDC-TV Donation
- custom: 0:donation:edctv
- return: https://edctv.org
================================================================================
3. CHECKLIST OF POTENTIAL FAILURE POINTS & FAST REMEDIES1. SYMLINKS OVERWRITTEN BY NPM / NODEBB BUILD
- Risk: Runningnpm installinside the container can replace directory
symlinks with static folder trees or delete unindexed packages.
- Check:
docker exec -it app-nodebb-1 ls -la /usr/src/app/node_modules/ | grep -E "nodebb-(plugin-mto|theme-mto|plugin-treasury)"
- Remedy: If entries do not show-> /usr/src/app/..., re-run:
/opt/app/restore-mto.sh2. CONTAINER RECREATION / ELESTIO WATCHTOWER UPDATES
- Risk: If Elestio updates or recreates the container image, any file not
mapped to a persistent Docker volume will revert to default.
- Check: Confirm Elestio "Auto-Update" is disabled for the NodeBB service.
- Remedy: If a container reset occurs, run on the host:
/opt/app/restore-mto.sh3. PAYPAL IPN DROPS OR SILENT REJECTIONS
- Risk: PayPal changes TLS/SSL handshakes, or your firewall/reverse proxy
blocks POST requests to/treasury/ipn.
- Check:
docker exec -it app-nodebb-1 grep "Treasury IPN" /usr/src/app/logs/output.log
Check for "IPN unverified" or "Handshake error".
- Remedy: Confirm SSL certificates are valid on the domain and that PayPal's
IPN history dashboard reports HTTP 200 responses.4. PM UNREAD BADGE NOT DECREMENTING
- Risk: User navigates via back-button cache or WebSocket disconnects.
- Check: Open browser DevTools (F12) -> Network tab, and verify that
/mto-messages/unread-countreturns valid JSON{ count: X }.
- Remedy: Verify the thread visit endpoint is reached (/mto-messages/:threadId)
which resetsmto:pm:read:<threadId>:<uid>in Redis.5. REDIS OBJECT / WIDGET SYNC CONFLICT
- Risk: Editing widgets in NodeBB ACP (/admin/extend/widgets) can
inadvertently overwrite the customtreasury_fundsor HTML containers.
- Check: Ensurewidgets:globalstill containstreasury_fundsin the
sidebar area via Redis CLI or inspection script.
- Remedy: Re-drag the "Treasury Funds" widget into the Global Sidebar in ACP.================================================================================
END OF LOG -
Smurf filter and MTO smileys moved over and set up.
================================================================================
MTO NODEBB - CUSTOM SMURF CENSOR & LEGACY SMF SMILEY ENGINE BUILD LOG
Date: October 30, 2026
Host: nodebb-vklpj-u73921 (Elestio VPS)
Container: app-nodebb-1
Domain: multitool.ninja- SYSTEM ARCHITECTURE & PERSISTENCE
- Custom Plugin Path on Host:
/opt/app/nodebb-plugin-smurf-censor/ - Mounted Inside Container via docker-compose.yml:
/usr/src/app/nodebb-plugin-smurf-censor - NodeBB modules resolution:
NodeBB resolves plugins strictly from /usr/src/app/node_modules/.
Because node_modules is rebuilt/pruned on container updates, an automated
symlink is recreated on boot via /opt/app/entrypoint.sh:
/usr/src/app/node_modules/nodebb-plugin-smurf-censor -> /usr/src/app/nodebb-plugin-smurf-censor - Asset Storage:
141 legacy animated GIF/PNG smileys reside in:
/usr/src/app/public/uploads/smileys/
(Host mount: /var/lib/docker/volumes/app_nodebb-files/_data/smileys/)
A persistent static fallback backup copy is preserved at:
/opt/app/nodebb-plugin-smurf-censor/smileys-backup/
- CONFLICT RESOLUTION
- Problem: The stock 'nodebb-plugin-emoji' intercepted colon codes (e.g.
,
,
), causing broken image squares, duplicate scrapers, and missing
emoji pack errors. - Fix: Uninstalled/deactivated 'nodebb-plugin-emoji'.
Native OS emojis (Win + ., macOS shortcuts, mobile keyboards) continue to
work natively in Unicode, while our custom plugin maintains exclusive control
over all forum smileys.
- CORE COMPONENT MANIFEST
File: /opt/app/nodebb-plugin-smurf-censor/package.json
{
"name": "nodebb-plugin-smurf-censor",
"version": "1.0.0",
"description": "Smurf censor and classic SMF smiley engine",
"main": "library.js"
}File: /opt/app/nodebb-plugin-smurf-censor/plugin.json
{
"id": "nodebb-plugin-smurf-censor",
"name": "Smurf Censor",
"library": "./library.js",
"scripts": [
"./client.js"
],
"css": [
"./style.css"
],
"hooks": [
{ "hook": "filter:post.save", "method": "filterPostSave" },
{ "hook": "filter:parse.post", "method": "filterParse" },
{ "hook": "filter:parse.raw", "method": "filterParseRaw" },
{ "hook": "filter:posts.get", "method": "filterPostsGet" },
{ "hook": "filter:topic.get", "method": "filterTopicGet" },
{ "hook": "filter:topics.get", "method": "filterTopicsGet" },
{ "hook": "filter:topic.create", "method": "filterTopicCreate" },
{ "hook": "filter:topic.edit", "method": "filterTopicEdit" }
]
}File: /opt/app/nodebb-plugin-smurf-censor/library.js
- Reads /opt/app/nodebb-plugin-smurf-censor/smileys.json at startup.
- Word Filter / Censor:
Replaces profane terms with "smurf", "smurfing", "smurfed", "smurfer",
"smurfhole", "smurflicker", and pharmaceutical terms with "Smurfpills".
Reroutes competitive/spam retail domains ([url=http://forum.multitool.org]multitool[/url], [url=http://forum.multitool.org]multitool[/url], [url=http://forum.multitool.org]multitool[/url])
to multitool. - Smiley Parsing Pipeline:
Splits content by HTML tags (/(<[^>]+>)/g) to prevent rewriting attributes.
Transforms exact :name: shortcodes directly into:
<img src="/assets/uploads/smileys/<file>" alt=":code:" title="desc" class="forum-smiley emoji" /> - Server Hooks:
- filterPostSave: Executes before WebSocket broadcast so new posts are
pre-rendered before pushing to clients. - filterParse / filterParseRaw: Parses strings, post objects, and composer data.
- filterPostsGet: Guarantees full post hydration on page loads.
- filterTopicGet / filterTopicsGet / filterTopicCreate / filterTopicEdit:
Cleans topic titles through the smurf censor.
- filterPostSave: Executes before WebSocket broadcast so new posts are
File: /opt/app/nodebb-plugin-smurf-censor/client.js
- Top Bar Smiley Strip:
Appends the classic SMF quick-smiley bar directly below the composer
formatting toolbar with active hover zoom animations. - [more] Modal Selector:
Clicking [more] launches an overlay modal housing the full secondary
and historical smiley catalog. Clicking any smiley inserts the normalized
code at cursor position and closes the window. - Live Real-Time Typing Preview:
Hooks 'filter:parse.raw', 'action:composer.preview', and text input listeners
so that typing or inserting smileys instantly renders the animated GIF in
the composer preview pane without delay. - Real-Time WebSocket Delivery (Zero Page Refresh):
Initializes a MutationObserver on document.body coupled with hooks on
'action:posts.loaded' and 'action:posts.edited'. When another member posts,
new post DOM elements are scanned and rendered instantly.
File: /opt/app/nodebb-plugin-smurf-censor/style.css
- Universal Reset:
Forces img.forum-smiley to display inline-block, background transparent,
border none, margin 0, padding 0 1px, vertical-align middle. - Card/Frame Suppression:
Strips card wrappers and margins in light and dark modes. Preserves
natural background readability for classic indexed GIFs. - Composer & Modal Styling:
Styles the .mto-smiley-bar, .mto-composer-smiley, .mto-more-btn,
and popup modal grid.
- DOCKER & SYSTEM HARDENING CONFIGURATION
A. /opt/app/docker-compose.yml
Under services -> nodebb -> volumes:
- /opt/app/nodebb-plugin-smurf-censor:/usr/src/app/nodebb-plugin-smurf-censorB. /opt/app/entrypoint.sh
Inserted above the final 'exit 0':SMURF_SRC=/usr/src/app/nodebb-plugin-smurf-censor
SMURF_DST=/usr/src/app/node_modules/nodebb-plugin-smurf-censor
if [ -d "$SMURF_SRC" ]; then
ln -sfn "$SMURF_SRC" "$SMURF_DST"
echo "MTO NodeBB startup: linked nodebb-plugin-smurf-censor into node_modules."
else
echo "MTO NodeBB startup: WARNING - $SMURF_SRC introuvable, plugin non lie."
fiC. Persistent Archive
Timestamped complete archive created on host:
/opt/app/smurf-censor-and-smileys-backup-2026-10-30.tar.gz- REBUILD / DISASTER RECOVERY PROCEDURES
If container is rebuilt from scratch or node_modules is completely pruned:
-
Restore plugin directory (if missing):
cd /opt/app
tar -xzvf smurf-censor-and-smileys-backup-2026-10-30.tar.gz -
Ensure docker-compose.yml contains the volume mount:
/opt/app/nodebb-plugin-smurf-censor:/usr/src/app/nodebb-plugin-smurf-censor -
Ensure entrypoint.sh has the symlink block for nodebb-plugin-smurf-censor.
-
If smiley images in /usr/src/app/public/uploads/smileys are missing:
docker exec -i app-nodebb-1 mkdir -p /usr/src/app/public/uploads/smileys
docker cp /opt/app/nodebb-plugin-smurf-censor/smileys-backup/. app-nodebb-1:/usr/src/app/public/uploads/smileys/
docker exec -i app-nodebb-1 chown -R node:node /usr/src/app/public/uploads/smileys -
Activate and rebuild NodeBB:
docker exec -i app-nodebb-1 /usr/src/app/nodebb activate nodebb-plugin-smurf-censor
docker exec -i app-nodebb-1 /usr/src/app/nodebb build
docker restart app-nodebb-1 -
Status Verification:
docker exec -i app-nodebb-1 ls -la /usr/src/app/node_modules/nodebb-plugin-smurf-censor
(Must output symlink -> /usr/src/app/nodebb-plugin-smurf-censor)
================================================================================
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login