MTO- NodeBB on Elestio
-
New forum acting a bit squirrely today. Having trouble editing my own post but only in one topic

Reply button is including previous post.
-
I am currently editing tomorrow's episode of EDC-TV so I can get that out on time. As soon as I am done with that I will head on over and see what the issue may be.
Def
-
-
I almost have a handle on the poste editing issue, but I don't have the wherewithall to deal with it tonight. I'll get at it tomorrow.
On the bright side, multitool.ninja has been set to find the new forum to make it easier to test. No need to go through this thread anymore and try to find the long, generic server defined domain to get to it.
Multitool.Ninja - when you positively, absolutely need to kill someone with a set of pliers by 9am, guaranteed.
Def
-
Found a bit of a clustersmurf this morning, but it explains a lot of why I have been trying to make fixes that won't fix.

Originally I was making changes in the Custom CSS, Custom JS and Custom Header in the Admin Control Panel (ACP) but then determined that creating an MTO Theme would be a better choice over modifying an existing one, so I started working on the code itself to develop a new theme.... while forgetting to turn off the theme modifications in the ACP.
So all the theme changes I have been making I have had to fight to get them to work because they are trying to override the things I'd already built to override things like the original, generic theme.

Anyways, I have other smurf to do right now so I am going to go and do that, but when I get back I am going to clean up my mess and re-evaluate what actually needs doing now that I am done fighting with myself over it.
For now though, the edit box should be fully visible and functional, so there's that at least.
Def
Def -
First spam on new site ?
https://nodebb-vklpj-u73921.vm.elestio.app/post-queue/topic-1787568190680
-
I saw that and deleted it and the spammer.
It feels real now, doesn't it?

Def
-
-
I've been keeping these daily logs of the work I have been doing but it occurred to me that I should probably be keeping them here so they are easy for Micah to find, and proof for the rest of you that I am not just sitting on my ass.

25-08-2026 Daily Log
MTO / NodeBB β Daily Migration Report
Date: 2026-08-25
Environment:app-nodebb-1/ NodeBB /nodebb-theme-mto
Session: ACP Custom CSS β Theme ownership migration
Status: Successful β stable stopping point
1. Session objective
Continued the migration of MTO-specific CSS out of NodeBB's ACP
customCSSand into the MTO-owned theme:/usr/src/app/nodebb-theme-mto/theme.scssThe goal is to eliminate duplicate/legacy ACP styling where the theme already provides the authoritative implementation, while preserving rollback checkpoints and validating each migration independently.
2. Header CSS migration β completed
Theme change
Added the MTO global header implementation to:
/usr/src/app/nodebb-theme-mto/theme.scssInserted immediately before:
General cards and surfacesTheme header section:
MTO β Global HeaderIt owns:
#mtorg-header.mtorg-logo.mtorg-nav- logo sizing
- navigation layout
- navigation hover/focus state
- MTO sand/green presentation
Theme checkpoint
Before migration:
8a5279b079aad34257b3ae96aaa273e88259dce3fcc27f42b88c4d2be1931b56After migration:
f516664233cdf3be1a839d43195508fd855fd2b59b3afa846eace9df08851b02Rollback
Created inside the theme:
theme.scss.before-header-css-migration-20260825Original checksum:
8a5279b079aad34257b3ae96aaa273e88259dce3fcc27f42b88c4d2be1931b56Build
Successful:
Asset compilation successful. Completed in 6.72sec.
3. ACP header CSS removal β completed
Created a rollback copy:
~/nodebb-backups/acp-legacy-20260824/customCSS-before-header-removal-20260825.txtOriginal:
704 lines 15930 bytes b23b51e4b694eae95fbce8477f69f13f416451033cab2b9d476fdb964726f705Removed the legacy:
#mtorg-header .mtorg-logo .mtorg-navrules, including responsive rules.
Validated result:
629 lines 14182 bytesConfirmed:
Header selectors remaining: 0Applied to Redis
config customCSS.Live post-removal:
627 lines 14180 bytes 8638ac923e1b18683683ffb2fec9f56bee38ae4d4157f7d7897a8a7a87d83d02Confirmed:
NONE β cleanfor the former header selectors.
Build successful.
Restart successful.
4. Cards / sidebars migration β completed
Audited existing theme implementation.
Theme already owned:
.card .card-header .card-bodyand sidebar styling through:
body.template-category [component="sidebar"] body.template-topic [data-widget-area="sidebar"]Therefore the following ACP block was determined to be legacy/duplicate:
Cards / sidebarsRemoved:
.card .sidebar .card [data-widget-area="sidebar"] .card .sidebar .card-header [data-widget-area="sidebar"] .card-header .sidebar .card-body [data-widget-area="sidebar"] .card-bodyValidation:
627 β 595 lines 14180 β 13358 bytesValidated SHA:
8aa5b25a239ebe7980ab2c6857f90f14172faffa3dcb1f027b1d0fbb1f692fe6Applied to Redis.
Live result:
595 lines 13358 bytes 8aa5b25a239ebe7980ab2c6857f90f14172faffa3dcb1f027b1d0fbb1f692fe6Legacy selectors:
NONE β cleanBuild successful.
Restart successful.
Browser smoke test indicated everything remained where expected.
5. Categories / topic lists migration β completed
Audited ACP rules against the theme.
ACP legacy block included:
.categories .category .categories .category-header .categories .category-title .categories .category-description .topic-list-item .topic-list-item:hover .topic-list-item:last-child .topic-list-item .title .topic-list-item .timeago .category-stat .topic-stats .lastpost .topic-list-item.unread .category .unreadTheme already had equivalent category/topic ownership using:
[component="category"] [component="category/list"] [component="topic"] [component="category/topic"] .category-headerRemoved the legacy category/topic block.
Preserved intentionally for a later pass:
.badge .pagination .page-item .page-linkValidation:
627 β 568 lines 14180 β 12877 bytesValidated proposed checksum:
c9ff7d622374ad42ce286517abacc22d2be6d2308d56f20d4da1ee1ed48d0814Applied to Redis.
Live result:
568 lines 12877 bytes c9ff7d622374ad42ce286517abacc22d2be6d2308d56f20d4da1ee1ed48d0814Former selectors:
NONE β cleanPreserved rules verified:
.badge .pagination .page-item .page-linkBuild successful:
Asset compilation successful. Completed in 6.565sec.Restart successful.
Browser check: everything appeared to be working normally.
6. Bottom topic bar migration β completed
This was the final migration of the day.
Audited ACP:
#mto-bottom-topic-bar .mto-bottom-topic-bar .mto-bottom-topic-row .mto-bottom-topic-title .mto-bottom-topic-replyCompared against the theme.
The theme already owns a newer/more complete bottom topic bar implementation, including:
- normal document flow
- breadcrumb trail
- reply/action area
- responsive/mobile behavior
- overflow handling
- Watch dropdown stacking
- dark mode
- native NodeBB Watch behavior
Important theme implementation:
.mto-bottom-topic-bar .mto-bottom-topic-breadcrumbs .mto-bottom-topic-actionsand associated responsive/dark-mode rules.
Therefore the older ACP block was determined to be obsolete.
Validation
Removed only:
Existing bottom topic barblock.
Validation:
568 β 530 lines 12877 β 11979 bytesValidated checksum:
f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9deApplied to Redis.
Live result:
530 lines 11979 bytes f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9deFormer selectors:
NONE β clean
7. Final build/restart β successful
After the bottom-topic-bar migration:
./nodebb buildcompleted successfully:
Asset compilation successful. Completed in 6.625sec.Then:
docker restart app-nodebb-1successful.
Current containers at the checkpoint:
elestio-nginx Up 2 days app-nodebb-1 Up Less than a second app-redis-1 Up 2 days elestio-postfix Up 2 daysapp-nodebb-1came back successfully.
8. Functional smoke test
After the final restart, browser testing was performed.
Confirmed:
Topics can be watched and unwatched successfully.
This is particularly important because the bottom-topic-bar migration involved the native NodeBB Watch control and its dropdown positioning.
User report:
βThat seems to be working. I can watch/unwatch topicsβ
Therefore the critical Watch/Unwatch functionality survived the CSS ownership migration.
9. Known build warnings
Every build continues to report these existing warnings:
[nodebb-plugin-blog-comments] is active but not installed. [nodebb-plugin-calendar] is active but not installed.These were present throughout today's builds and did not prevent successful asset compilation.
No new build errors were introduced by today's migrations.
10. Current theme checksum
Current:
f516664233cdf3be1a839d43195508fd855fd2b59b3afa846eace9df08851b02Theme:
/usr/src/app/nodebb-theme-mto/theme.scss
11. Current ACP CSS state
The last validated/live ACP CSS is:
530 lines 11979 bytes f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9deThe following legacy areas have now been removed from ACP
customCSS:1. MTO global header 2. Cards / sidebars 3. Categories / topic lists 4. Bottom topic bar
12. Remaining ACP CSS
The remaining ACP CSS is primarily the more complicated/custom structural layer.
The last inventory showed these major areas remaining:
Global Navigation Badge Pagination Topic/post layout MTO author/post structure Breadcrumbs Bottom topic controls Composer / smileys YouTube/media fallback Responsive rules UtilitiesThe remaining ACP file was:
530 lines 11979 bytesafter the bottom-topic-bar removal.
Important: do NOT blindly remove the remaining CSS.
Today's audits showed that some of the remaining ACP rules have only partial or structurally different counterparts in the theme.
The next session should continue with ownership audits, not bulk deletion.
13. Recommended next step tomorrow
The most logical next investigation is:
Composer / smileys
The ACP still contains:
.composer .composer textarea .mto-smiley-bar .mto-smiley .mto-smiley:hover .mto-smiley:focus topic/post smiley image sizingThe theme already contains some
.mto-smiley-barand composer-related rules, so there may be another migration opportunity.However, this should be audited carefully because the ACP contains actual behavioral/presentation rules that may not yet have a complete theme equivalent.
Do not remove anything until the exact ownership comparison is done.
The YouTube fallback should probably remain untouched until separately audited because today's theme search did not establish a corresponding theme implementation.
14. Rollback/checkpoint files created today
Important files under:
~/nodebb-backups/acp-legacy-20260824/include:
customCSS-before-header-removal-20260825.txt customCSS-live-before-header-removal-20260825.txt customCSS-live-after-header-removal-20260825.txt customCSS-live-before-card-removal-20260825.txt customCSS-live-after-card-removal-20260825.txt customCSS-live-before-category-topic-removal-20260825.txt customCSS-live-after-category-topic-removal-20260825.txt customCSS-live-before-bottom-topic-bar-removal-20260825.txt customCSS-live-after-bottom-topic-bar-removal-20260825.txtTheme rollback:
/usr/src/app/nodebb-theme-mto/theme.scss.before-header-css-migration-20260825
15. End-of-day status
Overall: GREEN / stable.
Today's work successfully moved several major pieces of MTO presentation into the theme and removed their duplicate ACP implementations.
No known functional regression.
The final functional test confirmed:
Watch topic β works Unwatch topic β works -
MTO Theme Cleanup β Daily Log
Date: August 26, 2026
NodeBB: 4.15.1
Container: app-nodebb-1
Theme: nodebb-theme-mto
Working directory: /usr/src/app/nodebb-theme-mtoObjective
Continue migrating the remaining MTO presentation/functionality into the custom Harmony-based theme, remove redundant/legacy CSS, restore native Harmony behavior where appropriate, and move toward eliminating the old NodeBB ACP Custom CSS/Header/JS layer.
Work completed
- Dead quick-smiley CSS removed
Audited all MTO references to:
smiley
emoji
quick-smiley
.mto-smiley
.mto-smiley-barFound only two obsolete CSS blocks in theme.scss and no corresponding MTO template, JS, or library implementation.
Removed:
.mto-smiley-bar .mto-smiley { ... }
.mto-smiley-bar {
display: none !important;
}Result: 245 bytes / 15 lines removed.
Final checksum after this stage:
36f124f6ce7e6085dabb5d7ef6f641b2293b055c93985d900c4d6805f64390c0
2. Harmony post-number behavior audited and restoredCompared MTO's topic.tpl against the installed Harmony theme.
Harmony provides:
<a href="{config.relative_path}/post/{encodeURIComponent(./pid)}"
class="post-index text-muted d-none d-md-inline">
#{increment(./index, "1")}
</a>MTO retained the native post anchor:
<a component="post/anchor" data-index="{./index}" id="{increment(./index, "1")}"></a>
but had lost the visible post-index link.
Restored the post-index into:
templates/partials/topic/post.tpl
Then corrected the numbering behavior.
Final desired behavior
Original topic post (./index == 0) β no visible number
First reply (./index == 1) β #1
Subsequent replies β native ./indexFinal implementation uses:
{{{ if (./index != 0) }}}
<a href="{config.relative_path}/post/{encodeURIComponent(./pid)}"
class="post-index text-muted d-none d-md-inline">#{./index}</a>
{{{ end }}}This was tested in the browser and confirmed to produce the desired result.
Final post.tpl checksum:
7f33bc6aaaf0abc33cbf096f0eb781d99488443dd60194796f6092fe0706d4e8
3. Bottom topic bar CSS consolidatedAudited the entire .mto-bottom-topic-bar region.
The same selector had been declared in multiple separate blocks:
primary layout block
overflow block
dropdown stacking blockConsolidated:
position: relative;
z-index: 2000;
overflow: visible !important;into the primary declaration.
Removed redundant standalone declarations.
Result:
75 bytes removed
mobile behavior preserved
print behavior preserved
Watch dropdown behavior preserved
dropdown-specific selector retainedInstalled validated checksum:
f55381de942ae0f44de26c01b048746311e4b9cc720cf7921e46e37cf3de5b43
Browser verification subsequently confirmed:
desktop good
mobile good
4. Bottom-bar comments cleanedRemoved redundant/repetitive section headings around the Watch/dropdown rules.
Functional rules were deliberately left untouched.
Result:
400 bytes removed
11 lines removed
Watch behavior preserved
mobile behavior preserved
print behavior preservedProposed checksum after comment cleanup:
b15ac234f403030bfa7b6180372dabce71f8289dd32dbd3c48399d15b7d8e31b
This was then the live theme state before the next cleanup.
- Legacy top-breadcrumb CSS removed
Audited the top breadcrumb against the actual Harmony breadcrumb template.
Found an obsolete desktop block:
.mto-top-topic-breadcrumbs {
min-width: 0;
overflow: hidden;
}.mto-top-topic-breadcrumbs .breadcrumb {
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}The active MTO implementation instead deliberately provides the flat/SMF-style breadcrumb treatment and mobile hiding.
Removed only the obsolete overflow/ellipsis block.
Preserved:
mobile hiding
transparent background
border removal
inline-flex breadcrumb
breadcrumb item styling
MTO topic-title arrow separatorInstalled checksum:
b93e8454f8b3cd19335976c3a4d7fc593072bababc29a2189ee65da0e538edee
Final theme architecture confirmedMTO is now structured as a Harmony-derived theme rather than a pile of ACP overrides.
Important ownership:
Function MTO location
Base theme Harmony
MTO CSS theme.scss
Header/brand templates/partials/header/brand.tpl
Post presentation templates/partials/topic/post.tpl
Topic layout templates/topic.tpl
Top topic controls/breadcrumb templates/partials/post_bar.tpl
Topic JS static/lib/mto-topic-actions.js
Theme library library.js
Theme metadata package.json, plugin.json, theme.jsonCSS import chain confirmed:
@import "../nodebb-theme-harmony/theme.scss";
and:
@import "nodebb-theme-harmony/scss/overrides";
The MTO scss/overrides.scss is only a Harmony compatibility import; it contains no MTO-specific customization.
MTO JS confirmed
static/lib/mto-topic-actions.js remains the active custom JavaScript.
It handles MTO-specific post functionality including the author/post-count behavior.
No mto-bottom-topic-bar JavaScript dependency was found.
Final checksum:
325fdf96f42edcf1acf3c9d38711c4706f3a2e457c47c1319a7e0980d994fe97
Header confirmedMTO has its own:
templates/partials/header/brand.tpl
Final checksum:
7bef5ae6134cfffd35e3f24832c676ff694198b1e0a78607aa4833b7eef98acf
This is part of the theme and therefore does not depend on ACP custom header content.
Topic template confirmed
Final:
templates/topic.tpl
checksum:
290e54181bfc95c58a020874fe512901af2d1474c5a8b0e00f17d414f476ba5d
Current final checkpointsAs of the end of today's work:
theme.scss
b93e8454f8b3cd19335976c3a4d7fc593072bababc29a2189ee65da0e538edeetemplates/partials/topic/post.tpl
7f33bc6aaaf0abc33cbf096f0eb781d99488443dd60194796f6092fe0706d4e8static/lib/mto-topic-actions.js
325fdf96f42edcf1acf3c9d38711c4706f3a2e457c47c1319a7e0980d994fe97templates/partials/header/brand.tpl
7bef5ae6134cfffd35e3f24832c676ff694198b1e0a78607aa4833b7eef98acftemplates/topic.tpl
290e54181bfc95c58a020874fe512901af2d1474c5a8b0e00f17d414f476ba5dNodeBB: 4.15.1
ACP handoff status
This is the only significant unfinished item.
We attempted to determine whether NodeBB's ACP Custom CSS / Custom JS / Custom HTML settings were still populated.
./nodebb config get returned empty results, but that was determined to be insufficient evidence.
A direct meta.configs.get() attempt also failed to produce the expected config object and generated a Winston logging warning.
config.json was inspected and confirmed to contain the Redis connection configuration, but does not contain the ACP customization values.
Therefore:
Do NOT disable or delete the ACP customization layer yet.
The actual ACP settings appear to be stored in NodeBB's Redis-backed settings/configuration rather than config.json.
Recommended next session
The next instance should start here, not redo the CSS cleanup.
Priority 1 β Locate actual persisted ACP settings
Find the Redis-backed NodeBB settings corresponding to:
useCustomCSS
customCSS
useCustomJS
customJS
useCustomHTML
customHTMLRead-only first.
Priority 2 β Compare ACP contents against MTO ownership
Classify every ACP customization:
REMOVE β already implemented by MTO
KEEP β still genuinely required
MOVE β functionality not yet migrated
OBSOLETE β experimental/dead code
Priority 3 β Only then disable ACP customizationBefore changing anything:
checkpoint current Redis values
disable the redundant ACP layers
rebuild/restart NodeBB if required
verify desktop
verify mobile
verify dark mode
verify topic posting/reply/watch/share/mark-unread
verify post numbering
verify header
verify no missing custom behavior
ImportantDo not start another broad theme.scss cleanup.
The theme is in a good, working state. The remaining work is infrastructure/handoff, not cosmetic cleanup.
End-of-day status
MTO theme cleanup:
Essentially complete
Post numbering:
Correct
Bottom bar:
Cleaned and verified
Top breadcrumbs:
Cleaned and verified
Mobile:
Verified
Desktop:
Verified
Harmony integration:
Confirmed
MTO JS/header ownership:
Confirmed
ACP CSS/JS/header retirement:
Final remaining task
Working rollback/checkpoints:
PreservedBest stopping point: leave the current live theme untouched and resume with the Redis-backed ACP settings audit.
-
31-08-2026 Daily Log
MultiTool.Org NodeBB Theme β Daily Log / Handoff
Date: 2026-08-31
Session: End of day
Current status: π’ Good stopping point1. Where we started
The project is a custom NodeBB theme for MultiTool.Org, with the goal of getting the UI closer to the site's preferred/older visual language while fixing several NodeBB/Harmony layout annoyances.
The immediate work over the last stretch has concentrated on:
- post/topic layout
- the bottom topic navigation/footer
- the standalone NodeBB Composer/reply page
- dark mode
- getting the theme controls into a globally consistent location
- avoiding the giant blank-space problems we'd been seeing
2. Major wins completed
A. Fixed the topic-page bottom bar/footer
We had been fighting a floating/badly positioned footer/bottom action area that could leave a ridiculous amount of empty space underneath it.
The current implementation is working correctly.
Browser testing showed:
- footer is at the bottom where it belongs
- no giant empty area beneath it
- topic page looks substantially cleaner
- the bottom topic controls remain usable
This was explicitly tested visually and declared a win.
The current live theme contains the post-footer styling around
theme.scssline ~584 and the topic template still contains the normal widget footer area.Do not casually rewrite this tomorrow. It is currently working.
B. Fixed / improved the standalone Composer/reply page
We discovered that clicking Reply takes us to the native NodeBB Composer route rather than simply opening an inline editor.
We deliberately styled that page rather than trying to force the ordinary topic Composer rules onto it.
The current theme has a dedicated
body.page-composesection covering:- overall compose-page layout
- composer positioning
- composer container
- reply context
- formatting bar
- writing area
- preview
- action bar
- sidebar
- responsive/mobile behavior
The CSS itself explicitly documents the distinction between the native Composer route and ordinary topic Composer instances.
Browser testing produced a very good-looking reply page with:
- proper header
- clean "Post a Reply" presentation
- properly contained editor
- preview area
- Community Links sidebar
- no giant blank space underneath
This was the second big win of the evening.
Again: don't start ripping apart the Composer CSS tomorrow. It is currently a success.
3. Dark Mode β major change completed
Originally the light/dark switch existed only on topic pages.
We decided that was wrong because theme selection is a global preference, not a topic-specific function.
The control has now been moved into the global header.
Current
brand.tplcontains the global light/dark-mode import:<!-- Global light / dark mode --> <!-- IMPORT partials/topic/dark-mode.tpl -->The audit confirms this is currently in the global header.
Result
The screenshots show the switch now appearing in the top navigation on:
- Home
- Category pages
- Topic pages
- presumably the standalone Composer page as well, because it uses the global header
And importantly, it looks good in both modes.
Light mode
The current light homepage has:
- MultiTool logo
- Home / Search / Profile / Notifications / Bookmarks / Members
- dark-mode control at the right
- category listing
- Community Links
- sane page height
Dark mode
The dark homepage now has:
- dark global page background
- dark header
- dark content surfaces
- readable green/blue/orange accents
- theme control in the header
- navigation remaining visible
- Community Links correctly styled
The category page and topic page were also visually checked in dark mode.
This was the other major win.
4. Dark-mode implementation details
The actual theme switch implementation is still in:
templates/partials/topic/dark-mode.tplDespite the
topicdirectory name, this is NOT dead code.It is now imported by the global header, so its filename is historical rather than indicative of its scope.
The JavaScript in that template:
- finds the toggle
- reads/applies the selected theme
- sets
data-bs-theme - updates the checkbox state
- updates the slider state
The audit confirms those references.
The current
theme.scsscontains the switch styling around lines 1340 onward and the actual[data-bs-theme="dark"]styling beginning around 1189.There are also later dark-mode finishing overrides dealing with Bootstrap/Harmony inheritance, post containers, navigation surfaces, the bottom topic bar, etc.
Important design decision
We decided the toggle belongs globally in the header/top menu, rather than keeping a special topic-page control.
That should also make the behavior much more sensible on mobile.
5. Header/navigation state
The theme now owns the global MultiTool header presentation.
Current header CSS begins around line 100 and defines:
#mtorg-header- logo
.mtorg-nav- icon-over-label navigation
- hover/focus states
- mobile stacking/wrapping
The mobile breakpoint is already present at
767.98px.The current visual navigation is:
Home | Search | Profile | Notifications | Bookmarks | Members | Dark Mode
That is currently looking good.
6. NodeBB/container state
We restarted the container:
docker restart app-nodebb-1It successfully restarted.
The running process tree afterward was:
node ./nodebb start /usr/local/bin/node /usr/src/app/loader.js /usr/local/bin/node /usr/src/app/app.jsSo NodeBB was up normally after the restart.
The restart was therefore successful and the subsequent browser testing was against the running application.
7. What we deliberately did NOT do
This is important for tomorrow's instance.
We have not done the advertising/layout pass yet.
The decision at the end of the successful visual testing was essentially:
We've got two good wins. Don't screw them up. Do the advertising/layout pass tomorrow.
So tomorrow's work should begin from the assumption that:
footer + Composer + global dark mode are working and should be preserved.
Don't treat them as unfinished merely because the broader theme isn't finished.
8. End-of-day cleanup audit
We then ran a read-only cleanup audit.
The audit explicitly made no changes.
The live theme files are currently:
library.js package.json plugin.json scss/overrides.scss static/lib/mto-topic-actions.js templates/partials/post_bar.tpl templates/topic.tpl templates/partials/header/brand.tpl templates/partials/topic/dark-mode.tpl theme.json theme.scssThe audit's initial file listing showed the core set, with the template tree containing the other files referenced by the grep output.
9. Cleanup opportunity identified
We discovered that the theme directory has accumulated a pile of historical working copies/backups.
Examples include:
theme.scss.bottom-bar-working theme.scss.before-cleanup theme.scss.corrupt-backup theme.scss.before-quote-style theme.scss.before-header-css-migration-20260825 theme.scss.before-user-panel theme.scss.before-avatar-size theme.scss.before-mobile-identity templates/topic.tpl.before-bookmark-removal-20260825 templates/topic.tpl.bottom-bar-working templates/topic.tpl.before-bottom-bar templates/partials/topic/post.tpl.before-quote-reorder templates/partials/topic/post.tpl.before-avatar-size templates/partials/topic/post.tpl.before-author-panel templates/partials/topic/post.tpl.before-mobile-identity templates/partials/topic/post.tpl.checkpoint-author-layout static/lib/mto-topic-actions.js.before-bookmark-removal-20260825 static/lib/mto-topic-actions.js.before-direct-bookmark-20260824 static/lib/mto-topic-actions.js.bookmark-fix-final-20260824 static/lib/mto-topic-actions.js.before-bookmark-fix-20260824 static/lib/mto-topic-actions.js.before-post-counts-20260824The audit confirms these are old historical copies, with timestamps going back to August 12β26.
Decision
We have not deleted them yet.
The proposed cleanup is:
- Make one known-good current checkpoint/archive.
- Delete the obsolete individual
.before-*,.working,.corrupt-backup, etc. files. - Keep the actual live files clean.
- Going forward, don't accumulate a new backup file for every experiment.
That is housekeeping, not a code change.
10. Things we specifically decided NOT to clean up tonight
Don't refactor
theme.scssyettheme.scssis now around 1,800 lines and contains a lot of accumulated CSS.There are almost certainly opportunities to consolidate duplicate selectors/overrides.
But do not undertake that tonight/tomorrow morning blindly.
The dark-mode CSS has several layers of intentional overrides because Bootstrap/Harmony is fighting us in places.
A visual refactor should happen later, when we can test each change.
Don't remove
dark-mode.tplEven though its directory name says
topic, it is now globally imported and is doing useful work.Don't remove current footer code
The current footer behavior is one of today's successes.
Don't remove current Composer code
The standalone Composer styling is also a success.
Don't touch
mto-topic-actions.jsmerely because old copies existThe current JS file is the live one:
static/lib/mto-topic-actions.jsThe audit records its checksum as:
325fdf96f42edcf1acf3c9d38711c4706f3a2e457c47c1319a7e0980d994fe97The old JS copies are what should eventually be cleaned out.
11. Current known-good state
As of the end of this session:
π’ Working
- Global MultiTool header
- Header navigation
- Mobile header structure
- Global dark-mode control
- Light mode
- Dark mode
- Homepage/category dark-mode appearance
- Topic dark-mode appearance
- Topic bottom action/footer area
- Standalone Reply/Composer page
- Composer responsive layout
- Community Links sidebar
- No huge footer whitespace
- No huge Composer whitespace
- NodeBB running after restart
π‘ Deliberately deferred
- Advertising/layout pass
- Broader visual polish
- More extensive mobile testing
- CSS consolidation/refactoring
- Final cleanup of historical backup files
- Any larger architectural cleanup
Not currently a problemNothing from today's browser testing suggests that we need to roll back the work.
12. Recommended starting point tomorrow
I'd start tomorrow in this order:
Step 1 β Preserve tonight's win
Make one checkpoint of the current working theme.
Step 2 β Remove the archaeological layers
Delete the obsolete backup/working files after the checkpoint.
Step 3 β Do the advertising/layout pass
This was explicitly deferred until tomorrow.
Step 4 β Test the global theme control on the pages we care about
At minimum:
- Home
- Category
- Topic
- Reply/Composer
- mobile viewport
Step 5 β Only then consider CSS cleanup
Look for:
- duplicate selectors
- superseded overrides
- comments referring to changes that no longer exist
- rules that are no longer needed
- old temporary experiments
But one cleanup at a time, browser test after each meaningful group.
13. One-sentence handoff
If I had to give tomorrow's instance the whole state in one paragraph:
MultiTool.Org's custom NodeBB theme had two major successful fixes today: the topic bottom/footer layout and standalone Reply/Composer page are now clean with no giant empty-space problems, and the dark-mode toggle was moved from the topic template into the global header so light/dark mode is available throughout the site; Home, Category, Topic and dark-mode views were visually tested and look good, NodeBB was restarted successfully, the advertising/layout pass is intentionally deferred to tomorrow, and the only immediate housekeeping task is to checkpoint the working theme and remove the pile of old
.before-*/.working/backup files without touching the current working CSS or templates. -
I have fixed the colors that no one but me seemed to like. I have made a secondary reply page, similar to SMF, which will eventually be populated with smileys. I have put the toggle for Dark Mode at the top so it's accessible and available on each page, rather than just at the bottom of threads, and I got rid of that sticky floating footer thing that was such a huge annoyance that I decided a separate page for replying was better than any continued smurfery.
Plus that's the way we do it here anyway, so I guess it would have been done sooner or later.
There should be more visible changes over the next few days now that the cleanup is (mostly) out of the way, so any additional fixes or issues that you see, please let me know.
Def
-
Multitool.Org / NodeBB β Daily Handoff Log
Date: 2026-09-01
Project: Multitool.Org self-hosted NodeBB forum
Environment: Docker / Elestio
NodeBB: 4.15.1
Container: app-nodebb-1
Theme: /usr/src/app/nodebb-theme-mto
Primary stylesheet: /usr/src/app/nodebb-theme-mto/theme.scss- Today's objective
Continue moving the MTO NodeBB UI toward the visual/UX feel of the old SMF forum while:
preserving native NodeBB functionality;
maintaining responsive/mobile behavior;
consolidating styling into the custom child theme;
avoiding unnecessary ACP Custom CSS/JS;
making reversible, incremental changes;
keeping the codebase clean enough to maintain later.
2. Completed today
A. SMF-style quote treatment β DONE
ProblemNodeBB was presenting quoted material as a large secondary card/block, which looked visually heavy and consumed unnecessary vertical space.
The original MTO CSS treated:
[component="post/parent"]
as though it were the quote body.
Investigation showed that this element is actually NodeBB's small parent-post preview/button, not the actual quote.
The actual quoted material is rendered as:
<blockquote>
<p>...</p>
</blockquote>inside:
[component="post/content"]
SolutionThe MTO theme now:
hides Harmony's duplicate parent-post preview;
styles the actual <blockquote>;
removes the card/background treatment;
uses a thin vertical quote indicator;
reduces font size;
keeps quoted text muted;
preserves links;
has a smaller mobile treatment.Current permanent CSS:
/* =========================================================
MTO quote treatment
Use the actual blockquote as the quoted context.
Hide Harmony's duplicate parent-post preview.
========================================================= */body.template-topic [component="post/parent"] {
display: none !important;
}body.template-topic [component="post/content"] > blockquote {
margin: 0.35rem 0 0.8rem 0 !important;
padding: 0.2rem 0 0.2rem 0.7rem !important;
background: transparent !important;
border: 0 !important;
border-left: 2px solid var(--mto-border-dark) !important;
border-radius: 0 !important;
box-shadow: none !important;
color: var(--mto-muted) !important;
font-size: 0.8125rem !important;
line-height: 1.4 !important;
}body.template-topic [component="post/content"] > blockquote p {
margin: 0 !important;
color: var(--mto-muted) !important;
font-size: 0.8125rem !important;
line-height: 1.4 !important;
}body.template-topic [component="post/content"] > blockquote a {
color: var(--mto-green) !important;
}body.template-topic [component="post/content"] > blockquote a:hover {
color: var(--mto-orange) !important;
}@media (max-width: 991.98px) {
body.template-topic [component="post/content"] > blockquote {
margin: 0.25rem 0 0.65rem 0 !important;
padding: 0.15rem 0 0.15rem 0.55rem !important;
font-size: 0.78rem !important;
line-height: 1.35 !important;
}body.template-topic [component="post/content"] > blockquote p { font-size: 0.78rem !important; line-height: 1.35 !important; }}
ResultVisually successful.
The quote now reads as quoted context within the reply, rather than another post/card.
B. Removed redundant "1 Reply / Last reply..." box β DONE
ProblemPosts could display a box such as:
1 Reply Β· Last reply about 4 hours ago
Clicking it produced another rendering of a reply further down the thread.
This was:
redundant;
confusing;
taking up space;
contrary to the desired dense SMF-style presentation.
InvestigationThe actual NodeBB element was identified as:
<a component="post/reply-count" ...>
rather than the initially guessed:
[component="post/summary"]
Working CSSTemporary browser test confirmed this exact selector works:
body.template-topic [component="post/reply-count"] {
display: none !important;
}
Permanent versionThis was added to theme.scss:
/* =========================================================
MTO topic cleanup
Hide Harmony's embedded reply-count summary.
The actual replies remain fully functional.
========================================================= */body.template-topic [component="post/reply-count"] {
display: none !important;
}
ImportantThis only hides the redundant reply-count UI.
It does not intentionally disable:
Reply;
Quote;
Post tools;
actual replies;
topic functionality.The user subsequently confirmed that Reply/Quote were working.
- Backups created today
Quote backup:
theme.scss.backup-quote-20260901-184928
Reply-count backup was created by the permanent-install command as:
theme.scss.backup-reply-count-YYYYMMDD-HHMMSS
Do not delete these yet.
Eventually the project should have a cleaner archival/checkpoint strategy rather than accumulating timestamped backup files in the theme source directory.
- Git state
At the quote checkpoint:
M theme.scss
?? theme.scss.backup-quote-20260901-184928The quote diff was limited to the intended quote treatment.
After the reply-count change, theme.scss contains the additional post/reply-count rule.
Before the next major change, inspect:
cd /usr/src/app/nodebb-theme-mto
git status --short
git diff -- theme.scssDo not assume the working tree is clean.
- Important discovery from today's debugging
This is worth preserving for future work.
NodeBB quote structure
The relevant DOM structure is approximately:
<div component="post/parent" ...>
...
<div component="post/parent/content">
<p>quoted preview...</p>
</div>
</div><div component="post/content">
<p>root <a>said</a>:</p><blockquote> <p>actual quoted text...</p> </blockquote> <p>actual reply...</p></div>
Therefore:
Do not confuse post/parent with the actual quote body.
The actual quote is the <blockquote> inside post/content.
This distinction saved us from continuing to style the wrong element.
- Current visual direction
The target remains an SMF-inspired NodeBB, not a literal SMF clone.
Desired characteristics:
compact;
information dense;
broad post content;
relatively narrow author column;
restrained borders;
less "card-based" Harmony appearance;
green/olive MTO branding;
light/dark themes that feel related;
useful sidebar/ad space;
native NodeBB responsiveness;
native NodeBB functionality wherever practical.The user supplied SMF reference screenshots showing:
compact header/navigation;
dense category rows;
dense topic lists;
avatar/author column on topic posts;
broad post body;
embedded quote context;
sidebar space;
banner/ad areas.
7. Existing work from previous sessionsThese are important because future changes should not accidentally undo them.
Header
Custom MTO global header exists, with:
logo;
Home;
Categories;
Members;
Bookmarks;
Search;
Login/Register;
global light/dark toggle.The dark-mode toggle was moved from topic-only behavior to the global header and tested on forum index/category pages.
Topic layout
Topic/sidebar proportions have been adjusted toward approximately:
80% topic
20% sidebarrather than Harmony's default 75/25.
There is also a deliberate ~3rem relationship/margin around topic action bars to align them visually with the post content width.
Post counts
MTO has work in place to display:
Posts: N
under the author name.
There was a known issue around dynamically loaded posts, and action:posts.loaded was being used to update counts.
Future work should verify that the handler uses the event's supplied post data where appropriate rather than relying only on initial ajaxify.data.posts.
Post numbering
Desired behavior:
main/original topic post: no #1
first reply: #1
second reply: #2
etc.This was being handled at the template level.
Native post actions
Native:
Reply
Quote
Post tools
Watch/follow
Share
Printshould remain functional.
Do not replace native behavior unnecessarily.
- Known unresolved items
A. Composer
The composer has been the most troublesome area.
NodeBB's default composer is fixed/full-viewport and is appended to document.body.
A CSS-only attempt to make it a normal inline element caused large blank-space/positioning problems.
NodeBB's composer resize code also manipulates inline positioning and content padding.
Do not casually revisit composer CSS without first inspecting its actual DOM/JS behavior.
The desired eventual result is more like a conventional SMF reply area:
normal-sized large textarea;
sensible positioning;
previous posts visible;
potentially ad space;
mobile friendly.But this should be treated as a separate project.
B. Post action dropdown clipping
There has been a known issue where the native post-tools dropdown can be clipped on short posts.
Inspection previously found:
[component="post"]
.post-containeramong ancestors with overflow: hidden.
Making overflow visible temporarily improved dropdown behavior.
However, this should be handled carefully so it doesn't destabilize post layout or editing.
C. Post editing
Editing a short post has occasionally caused the editor to appear under subsequent posts.
Likely related to positioning/overflow/composer behavior.
Not solved yet.
D. Dark-mode polish
Dark mode works globally, but there are still some palette/cascade issues to address eventually:
some outer/gutter areas have remained light;
some list backgrounds remain light;
dark-mode green links were initially too dark;
CSS variable overrides were being overridden by a later stylesheet.Important discovery:
A computed-style inspection showed MTO dark variables were being overridden by a later stylesheet containing :root declarations.
Therefore future dark-mode fixes may need:
stronger specificity;
later placement;
or another deliberate cascade strategy.Do not assume the current [data-bs-theme=dark] variables automatically win.
- ACP cleanup still planned
There is a substantial legacy ACP Custom CSS and ACP Custom JS implementation.
They have been backed up.
Long-term goal:
Move required MTO functionality into the child theme and then remove/disable redundant ACP code.
Do not remove ACP CSS/JS casually yet.
First establish that the corresponding theme implementation fully replaces it.
Same applies to the custom global header currently injected through ACP Custom Header/Custom HTML.
Long-term desired location:
nodebb-theme-mto
βββ templates
βββ partials / brand.tplor the appropriate Harmony child-theme template override.
- Future roadmap
Suggested order when work resumes:
Priority 1 β Preserve functionality
Before visual work:
verify Reply;
verify Quote;
verify editing;
verify post tools;
verify watching;
verify mobile.
Priority 2 β Category/topic densityMove the topic/category pages further toward SMF:
tighter row spacing;
cleaner metadata;
stronger topic/title hierarchy;
compact pagination;
less Harmony card feeling.
Priority 3 β Post layoutContinue refining:
author column;
post body width;
post spacing;
action bars;
post separators;
signatures.
Priority 4 β SidebarEventually add:
Community Links;
Sponsors box;
banner/ad space;
appropriate responsive behavior.
Priority 5 β Header/footerFurther SMF-inspired polish:
compact navigation;
social icons;
footer structure;
banner/ad slot.
Priority 6 β ComposerTreat as its own controlled project.
Priority 7 β ACP cleanup
Once theme functionality is stable:
migrate remaining required code;
disable redundant ACP Custom CSS;
disable redundant ACP Custom JS;
migrate header;
archive old code cleanly.
11. Working philosophyDo not optimize aesthetics at the expense of native NodeBB functionality.
Preferred workflow:
Identify actual DOM/template structure.
Test a change live in browser when practical.
If successful, put it in theme.scss/theme template.
Back up before permanent modification.
Build.
Restart only when necessary.
Hard refresh.
Test functionality.
Check Git diff.
Establish a checkpoint.Avoid:
editing compiled build/public/client.css directly;
piling on ACP Custom CSS;
duplicate JS implementations;
speculative selectors;
changing several unrelated things at once.
12. Current stopping pointThe forum is in a better state than at the start of the session.
The two visual changes completed today are:
Quote = compact embedded context
and
Reply summary box = hidden
Both have been browser-tested.
The user explicitly chose to stop here for the day.
Next session starting instruction
Do not immediately start changing things.
-
I forgot yesterday's daily log. Sorry.
MTO β Daily Log / Handoff
Date: September 2, 2026
Project: Multitool.Org NodeBB rebuild/customization
NodeBB: 4.15.1
Theme: nodebb-theme-mto / Harmony-derived
Current test domain: https://multitool.ninja
Canonical NodeBB config URL: still https://nodebb-vklpj-u73921.vm.elestio.app β intentionally unchangedπ’ COMPLETED / WORKING
- Topic/sidebar width β 85/15
We changed the desktop topic layout from the previous 80/20 target to:
Topic/post area: 85%
Sidebar: 15%The additional 24px width on the topic's breadcrumb/action/reply bars was also made permanent.
Status:
Done and approved by eyeball test.There is a duplicate copy of the +24px alignment CSS in theme.scss. It is harmless, but should eventually be cleaned up.
- Category/topic list density
We tightened the vertical spacing on topic/category rows.
Permanent change:
.topics-list category items reduced to 10px top/bottom padding.
Status:
Done.- Category header tightened
Reduced the category header spacing/padding.
Status:
Done.- Composer Submit button moved to bottom
This was one of the bigger little victories.
NodeBB's native composer originally had the Submit action up in the top action area. We moved the native submit container to the bottom of the composer using:
static/lib/mto-topic-actions.js
The JavaScript watches for the composer being loaded and handles the dynamically created composer.
CSS puts the button on the bottom/right.
Status:
Permanent and tested.The native button still has NodeBB's checkmark and current labeling behavior. We decided not to mess with changing its text because...
οΈ Important historical footnoteWe tried a MutationObserver-based approach to change the button text.
It caused a site-wide hang because the observer effectively chased its own tail.
That code was removed.
DO NOT resurrect that approach.
Backups exist:
mto-topic-actions.js.backup-composer-20260902-115803
mto-topic-actions.js.backup-reply-label-20260902-121335
theme.scss.backup-composer-20260902-115803The current simple composer-move code is the good stuff.
π’ 5. Quote styling
We changed NodeBB's topic quotes to look much more like the old MTO/SMF presentation:
Removed the large Harmony quote box treatment.
Removed the parent-post display.
Added a simple left border.
Smaller/muted text.
Tight spacing.
Green links, orange hover.
Mobile gets slightly smaller spacing/text.Status:
Permanent.π’ 6. Harmony reply-count summary hidden
We hid:
[component="post/reply-count"]
because it was adding UI that wasn't useful for the MTO look.
Status:
Done.π’ 7. Post footer/signature compacted
We tightened:
post footer padding
signature spacing
signature paragraph margins
footer action spacingThis helped make the posts much denser and more SMF-like.
Status:
Done.π’ 8. Author panel rebuilt
This was another major visual change.
The post author column is now:
~145px wide
light grey background
darker dividing border
centered content
128px avatar area
80px actual avatar
username emphasized
post count underneathWe also added the divider between the author panel and post body.
Status:
Approved.Deferred
We deliberately didn't hard-code SMF-style member ranks/groups yet.
Those should come from the eventual SMF data/import rather than us inventing them now.
Default-avatar work is also deferred.
π’ 9. Post action menus no longer get clipped
We found that the post action menu could be clipped by the post/container overflow rules.
Permanent fix:
body.template-topic [component="post"],
body.template-topic [component="post"] .post-container {
overflow: visible !important;
}Tested against:
short posts
long postsStatus:
Confirmed working.π’ 10. Mobile blue navigator/progress bar β KILLED WITH EXTREME PREJUDICE
NodeBB was displaying the blue mobile navigator/progress thing β the one showing something like:
39 out of 40
We tracked it to:
.navigator-mobile
and hid it on mobile.
Desktop pagination navigator was also hidden.
The actual pagination controls remain available as desired.
Status:
DONE.You tested this on the actual phone, and the blue bar was gone.
This one is officially closed.
π’ 11. NodeBB pagination enabled
We went into:
ACP β Settings β Pagination
and enabled pagination.
Current settings:
Setting Value
Posts per Page 20
Maximum Posts per Page 20
Topics per Page 20
Maximum Topics per Page 20
Categories per Page 50You said you're happy with 20 posts/page.
This is important because we had previously been considering the infinite-scroll behavior, and you made it clear that you do not want infinite scrolling, especially on giant threads.
Status:
DONE.If necessary later, 25 is an easy change, but there is currently no reason to touch it.
π‘ CURRENTLY UNDER INVESTIGATION: SMF-STYLE REPLY PAGE HISTORY
This is where we stopped.
The goal is to reproduce an important old SMF behavior.
When you're replying from, say, page 16 of a 112-page topic, the reply/composer page should show the posts surrounding the page you were readingβnot just some generic latest-post summary.
Your desired starting point is:
Show the 20 posts from the page the user was replying from, newest β oldest, below the composer.
And:
works on desktop
works on mobile
respects the new 20-post pagination
ideally preserves the current page context
final topic page naturally shows the final/latest 20You said we'd consider 10 or 15 if performance becomes an issue, but 20 is the starting target.
What we discovered
NodeBB already knows how to retrieve a post by topic indexWe found this in NodeBB's socket post handling.
There is already:
SocketPosts.getPostSummaryByIndex
which ultimately gets a post based on:
topic ID
post index
sort orderThat is exactly the sort of machinery we need.
So we're not trying to invent a way for NodeBB to understand topic position.
That's good news.
NodeBB's summary function isn't the problem
We inspected:
/usr/src/app/src/posts/summary.js
The important discovery is that:
Posts.getPostSummaryByPids(...)
doesn't decide which posts to show.
It receives the PIDs and then:
fetches them
parses them
enriches them
returns the summariesSo the real question is:
How do we give the composer the correct 20 PIDs/indexes?
That's much more manageable.
The current Reply link only carries the topic ID
Harmony's reply link currently looks essentially like:
<a href="{config.relative_path}/compose?tid={tid}" ...>
So when you click Reply, NodeBB knows:
"I'm replying to topic 9."
But it doesn't appear to know:
"I came here from page 16."
We confirmed the /compose URL
Browser testing showed:
/compose?tid=9&title=...
and the composer page's ajaxify.data had:
tid = 9
no useful pid
no page
no postcount
no sort informationSo the originating page context is currently being lost when Reply is clicked.
That's probably the first piece we need to solve.
NEXT TECHNICAL STEPWe had just reached the point of inspecting NodeBB's reply handling in:
/usr/src/app/public/src/client/topic/postTools.js
Specifically:
docker exec app-nodebb-1 sh -lc 'sed -n "250,345p" /usr/src/app/public/src/client/topic/postTools.js'
The reason for this is simple:
We want to see what information NodeBB has at the exact moment the Reply button is clicked.
If the clicked post/page/index is accessible there, there's a very good chance we can do this with the existing MTO client JS rather than creating another plugin.
π‘ BBCode β DELIBERATELY PARKED
We also did a fair amount of investigation here, but we explicitly decided not to start implementing it yet.
Current SMF tags were catalogued.
Your important ones are:
[b] [i] [u] [s] [spoiler] [img] [code] [quote] [url] Potentially useful cheap additions: [pre] --- You don't particularly care about preserving old font-size/color formatting, provided the actual text survives. Important BBCode discovery NodeBB currently does not parse the old SMF syntax. We confirmed this by seeing the literal: in a post. That's actually useful because it tells us the compatibility layer is genuinely needed. Plugin research We found an old nodebb-plugin-bbcodes, but it's roughly 11 years old and geared around an older WysiBB/composer ecosystem. Given we're on NodeBB 4.15.1: We do not want to throw that ancient plugin into production and see what catches fire. There were also old BBCode-to-Markdown/vBulletin migration plugins, but those aren't what we want either. The likely eventual approach is a small MTO-specific compatibility layer, probably extending the existing Markdown parsing pipeline rather than trying to bolt an archaeological NodeBB plugin onto 4.15.1. But: BBCode day is tomorrow. No BBCode implementation was made yesterday. 🟢 IMPORTANT: SMF ARCHIVE REMAINS SACRED We also established the migration philosophy. The SMF archive is roughly: 2,475,188 posts. You consider that archive your life's work/legacy, and you are not personally doing the SMF import, even with assistance. That is now a hard project constraint. If/when migration happens: work from copies/snapshots never experiment directly against the production archive extensive sample validation preserve original content preferably render legacy BBCode on output rather than rewriting millions of stored posts In other words: We do not poke the dragon because we happen to own a very large stick. 🟢 DOMAIN / WARNING STATUS We deliberately did nothing about the various browser-console warnings. They are expected consequences of testing the site at: multitool.ninja while NodeBB's configured canonical URL remains: nodebb-vklpj-u73921.vm.elestio.app We've seen warnings involving things like: emoji assets manifest/start URL Harmony fonts WebSockets service-worker/web-push origin mismatches DO NOT FIX THESE YET. When the real .org cutover happens, we'll deal with the canonical URL/proxy/origin alignment as one controlled operation. 🧹 BACKLOG / CLEANUP These aren't today's jobs. Theme cleanup Remove duplicate +24px CSS block. Eventually clean up old backup files once we're confident they're unnecessary. Legacy ACP customization There is still a substantial amount of older: ACP Custom CSS ACP Custom JS Custom Header / Custom HTML Those are backed up. Long-term, we want to migrate the useful pieces into the MTO child theme and eventually retire the ACP hacks. But not while we're still actively discovering what we need. 📌 CURRENT STATE β ONE GLANCE Visual work 🟢 Good Desktop topic width 🟢 85/15 Mobile topic width 🟢 Fine Pagination 🟢 20/page Infinite scroll 🔴 Not wanted Mobile blue navigator 🔴 Gone Composer Submit 🟢 Bottom Quotes 🟢 SMF-ish Author panel 🟢 SMF-ish Post action menus 🟢 Fixed Reply-page history 🟡 Next thing we're working on SMF BBCode compatibility 🟡 Investigated, intentionally postponed SMF import 🔴 Not happening yet / treat archive as read-only .org cutover 🔴 Later Def -
MTO NodeBB Daily Log β 2026-09-08
Completed / Significant WorkTopic layout and density
Established permanent 85/15 topic/sidebar layout on desktop.
Extended the topic action/reply bars by 24px so they align with the wider topic column.
Tightened category/topic row spacing for a denser, more SMF-like presentation.
Tightened category header spacing.
Confirmed the wider post column is visually preferable.Composer / Reply behavior
Moved the native NodeBB Submit control from the composer action area to the bottom of the composer.
Preserved the native NodeBB button and submission behavior.
Confirmed:
Bottom Reply opens a blank composer.
Per-post Reply opens a blank composer.
Quote opens with the expected quoted material.
Fixed the normal per-post Reply behavior where NodeBB's compose route was populating the original post body.
Added a clickable topic-title return link to the Reply composer.
Deliberately retained the composer Preview behavior where the original post can initially appear until the member starts typing; this is considered a useful reminder rather than a bug.Reply History
Implemented an MTO Reply History beneath the composer.
Reply History loads the latest 20 posts, independent of which post/page initiated the reply.
Uses NodeBB's native post rendering rather than recreating post content.
Added MTO author rail styling to Reply History.
Added compact quote/footer/signature styling.
Added mobile structural handling.
Fixed Quote actions within Reply History so they work despite the history being outside NodeBB's normal topic delegation.
Confirmed multiple quotes from Reply History work.
Confirmed normal post Reply/Quote behavior remains functional.Post presentation
Implemented the MTO author panel/rail:
145px author column
128px avatar area
80px displayed avatar
grey MTO-style author background
post-count placement
author/content divider
Hid the native Harmony reply-count summary.
Tightened post footer/signature spacing.
Changed quotes to a compact SMF-inspired left-border treatment.
Hid the redundant native parent-post display.
Fixed post action-menu clipping on long/short posts.Mobile
Removed the unwanted blue NodeBB mobile topic progress/navigation bar.
Confirmed the blue β39 out of 40β style navigator is gone on the actual Android phone.
Desktop pagination remains enabled and functional at 20 posts per page.
Confirmed direct page-2 navigation returns the expected 20 posts.Header / navigation
Added Login to the custom MTO header for logged-out visitors.
Login disappears for authenticated members.
Confirmed the Login link routes correctly to NodeBB's native login page.
Confirmed successful login through the new header link.
Preserved the existing MTO navigation and dark-mode control.Logged-out experience
Reviewed the logged-out topic experience in Incognito.
Confirmed guests can browse/read/share/page through topics and receive clear Register/Login calls to action.
Per-post Reply controls are appropriately unavailable to guests.
Decided the existing guest experience is good enough and DONE.
Deferred rewriting the generic NodeBB guest CTA because it does not affect current members and is not worth spending migration-time effort on.
MTO-specific smileys, including the Multitool.Org smiley and Swiss Army Knight, remain deferred until the eventual smiley-set work.Registration page
Redesigned the registration page as an MTO-specific experience rather than a generic NodeBB form.
Preserved native NodeBB registration functionality.
Established a wider registration area and approximately 600px form width on desktop.
Removed the unnecessary form-card treatment.
Preserved the dedicated Community Links component.
Added MTO-specific introductory copy explaining:
what Multitool.Org is
the community's focus
the relationship with EDC-TV, SAKWiki.com, and GearFeed
why prospective members should join
Added βCreate your accountβ as the form heading.
Tested the finished page in Incognito and judged it good enough to bank rather than over-polish.Registration features intentionally deferred
Registration approval
Email verification
Registration email configuration
CAPTCHA/anti-spam registration policy
Registration agreements/rules
Welcome/activation email
Final username policy
Account/permission mappingReason: the permanent domain, email infrastructure, and SMF migration have not happened yet, and some settings may be affected by the eventual migration. These will be addressed later.
Maintenance / Safety
Created fresh LKG backups of mto-topic-actions.js and theme.scss.
Created additional registration-specific backups before permanent registration work.
Removed temporary Reply debugging code.
Removed duplicate 24px alignment CSS.
Verified mto-topic-actions.js with node --check.
Built NodeBB successfully after the registration changes.
Restarted the NodeBB container and confirmed the finished registration page.
No NodeBB core registration templates were modified.
No SMF archive/database work was performed.
Current StateRegistration presentation: DONE / deferred functional settings.
Logged-out experience: DONE.
Reply/Quote/Reply History: DONE and tested.
Header/Login: DONE.
Topic/post presentation: substantially established.
SMF import: deliberately untouched.
Next work: prioritize something that benefits existing members or is independent of the eventual migration, rather than spending time configuring infrastructure that will need to be revisited later.
-
MTO SMF β NodeBB Migration β Daily Handoff Log
Date: 2026-09-09
Purpose: Preserve the full state of today's work so another ChatGPT session/model can continue without re-discovering the project.- Overall Project
We are migrating the MTO forum from SMF to NodeBB.
Production forum remains on SMF.
NodeBB is a test instance on Elestio.
We are deliberately building and testing the NodeBB implementation before touching production.
User is not a coder and prefers:
exact copy/paste commands
one small command block at a time
read-only inspection before changes where practical
explanations of what output means
avoiding unnecessary complexity
Do not "nuke" the NodeBB instance unless absolutely necessary.
- Current NodeBB Environment
Container: app-nodebb-1
Redis container: app-redis-1
NodeBB image: elestio/nodebb:latest
NodeBB version confirmed in ACP: 4.15.2
NodeBB URL:
https://nodebb-vklpj-u73921.vm.elestio.appDatabase: Redis
Health check previously returned HTTP 200.
NodeBB uploads volume:
/usr/src/app/public/uploadsHost bind mounts:
/opt/app/nodebb-theme-mto β /usr/src/app/nodebb-theme-mto
/opt/app/nodebb-plugin-mto-awards β /usr/src/app/nodebb-plugin-mto-awards
Compose backup:
/opt/app/docker-compose.yml.backup-before-mto-awardsNo systemd NodeBB service.
Docker logging uses journald.
SMF server is NOT on this NodeBB host.
Badge artwork files are now available.
- Installed NodeBB Plugins/Themes
Current installed/enabled list includes:
nodebb-plugin-2factor 8.0.8
nodebb-plugin-composer-default 11.0.14
nodebb-plugin-dbsearch 7.0.0
nodebb-plugin-emoji 6.0.16
nodebb-plugin-emoji-android 4.1.1
nodebb-plugin-link-preview 2.2.9
nodebb-plugin-markdown 13.2.10
nodebb-plugin-mentions 5.0.3
nodebb-plugin-spam-be-gone 2.3.7
nodebb-plugin-web-push 0.9.3
nodebb-rewards-essentials 1.0.3
nodebb-theme-harmony 3.2.16
nodebb-theme-lavender 8.1.0
nodebb-theme-mto 0.1.0
nodebb-theme-peace 3.1.3
nodebb-theme-persona 15.2.10
nodebb-widget-essentials 8.0.9
There is no dedicated awards plugin currently installed. nodebb-plugin-ns-awards was considered as an architectural reference only; it is old/unverified.
Rewards Essentials is NOT the intended workflow.
- MTO Custom Theme
Theme:
nodebb-theme-mto
Child theme of Harmony.
Version 0.1.0.
Separate from the awards plugin.
Theme owns presentation.
Custom author rail and signature placement already exist.
Merit Badges should appear beneath each member's signature, NOT in the author rail.
Badge artwork:
full badge: 50 Γ 60 PNG
mini badge: 25 Γ 25 PNG
transparent corners
Badges should NOT display on mobile.
Current legacy SMF Awards "In Post" display limit: 21.
Architecture decision:
nodebb-plugin-mto-awards owns badge data/business rules; nodebb-theme-mto owns badge presentation beneath the signature.
- Legacy SMF Awards Requirements
Legacy SMF catalogue has 194 badges:
Site: 18
Collector: 32
Modification: 5
User: 27
Challenge: 112
Staff manually award badges. Automatic triggers are NOT needed for Phase 1.
Members can request awards manually with evidence URLs. Moderators approve/reject.
No limit on how many badges a member can own.
Per-post display limit is 21.
Desired Phase 1
Badge catalogue
Five categories
Full + mini artwork
Manual staff awarding
Remove/revoke award
Member awards page
Display beneath signature
Display limit
Requestable awards
Historical migration
Phase 2
Request queue
Favorite badge
Automatic triggers
Old package "cleverness"/advanced automation
Guiding principle:
The computer handles the paperwork; humans make the award decision.
Legacy workflow
Member sees catalogue / available awards.
Member completes requirements.
Member copies evidence URL.
Profile β Forum Profile β Awards β Show Available Awards.
Member requests award and pastes evidence.
Staff receive alert.
Staff verify and approve.
Award appears beneath signature.
User specifically wants a remove option because some badges will need pruning.
Important distinction:
Delete/remove badge definition = remove a badge from catalogue.
Revoke member award = remove a badge from one member while keeping the badge definition.
Both need deliberate management UI.
- Legacy SMF Package Archaeology
The uploaded/analyzed legacy package was:
Package ID: spuds:member_awards
Version: 3.0
Target: SMF 2.0β2.0.99
Core data structures identified:
awards
Fields include:
id_award
award_name
description
id_category
time_added
filename
minifile
award_trigger
award_type
award_location
award_requestable
award_assignable
awards_members
Contains member/badge assignments including:
member
badge
date received
favorite
award type
active
comments
Request rows are inactive.
awards_categories
Stores categories.
Legacy award types
Manual
Post count
Top posters
Topic count
Top topic starters
Time online
Member since
Karma
Legacy display locations
Below avatar
Above avatar
Signature
Off
Legacy image formats
Full frame
Heading
No frame
Manual assignment supports member(s), award, and date received.
Unassign/removal is separate from badge definition deletion.
Request approval/rejection exists.
- MTO Awards Plugin
Plugin directory:
/opt/app/nodebb-plugin-mto-awards
Inside container:
/usr/src/app/nodebb-plugin-mto-awards
Package:
{
"name": "nodebb-plugin-mto-awards",
"version": "0.1.0",
"description": "MTO Merit Badges prototype",
"main": "library.js",
"nbbpm": {
"compatibility": "^4.15.0"
}
}Plugin manifest:
{
"id": "nodebb-plugin-mto-awards",
"templates": "templates",
"hooks": [
{
"hook": "static:app.load",
"method": "init"
}
]
}NodeBB CLI initially refused installation without a suggested package version, so the plugin was made available via symlink:
/usr/src/app/node_modules/nodebb-plugin-mto-awards -> /usr/src/app/nodebb-plugin-mto-awards
It was then activated successfully.
./nodebb plugins | grep -i "mto-awards" showed it installed/enabled.
Important NodeBB convention discovered:
Installed plugins use:
const db = nodebb.require('./src/database');
and similar NodeBB context requires at module scope.
The earlier standalone require.main.require test was wrong and should NOT be repeated.
Data layer loaded successfully and a database test passed.
Temporary test data was removed.
- Awards Data Layer
Current /lib/awards.js is the known-good working data layer.
Current content:
'use strict';
const db = nodebb.require('./src/database');
const PREFIX = 'mto:awards';
const keys = {
badges:${PREFIX}:badges,
badge: id =>${PREFIX}:badge:${id},
member: uid =>${PREFIX}:member:${uid},
memberAward: (uid, badgeId) =>${PREFIX}:member:${uid}:${badgeId},
requests:${PREFIX}:requests,
request: id =>${PREFIX}:request:${id},
};const Awards = {};
Awards.keys = keys;
Awards.createBadge = async function (badge) {
await db.setObject(keys.badge(badge.id), badge);
const score = Number.isFinite(Number(badge.displayOrder)) ? Number(badge.displayOrder) : (Number(badge.timeAdded) || 0);
await db.sortedSetAdd(keys.badges, score, badge.id);
return badge;
};Awards.getBadge = async function (id) {
return await db.getObject(keys.badge(id));
};Awards.deleteBadge = async function (id) {
await db.delete(keys.badge(id));
await db.sortedSetRemove(keys.badges, id);
};module.exports = Awards;
Awards.listBadges = async function () {
const ids = await db.getSortedSetRange(keys.badges, 0, -1);
return await Promise.all(ids.map(id => Awards.getBadge(id)));
};Awards.awardMember = async function (award) {
const key = keys.memberAward(award.uid, award.badgeId);
const existing = await db.getObject(key);if (existing && existing.active !== false) { throw new Error(`Member ${award.uid} already has badge ${award.badgeId}`); } const dateAwarded = Number(award.dateAwarded) || Date.now(); award.dateAwarded = dateAwarded; award.active = true; await db.setObject(key, award); await db.sortedSetAdd(keys.member(award.uid), dateAwarded, award.badgeId); await db.sortedSetAdd(keys.badge(award.badgeId) + ':members', dateAwarded, award.uid); return award;};
Awards.getMemberAward = async function (uid, badgeId) {
return await db.getObject(keys.memberAward(uid, badgeId));
};Awards.listMemberAwards = async function (uid) {
const badgeIds = await db.getSortedSetRange(keys.member(uid), 0, -1);
return await Promise.all(badgeIds.map(badgeId => Awards.getMemberAward(uid, badgeId)));
};Awards.listBadgeMembers = async function (badgeId) {
return await db.getSortedSetRange(keys.badge(badgeId) + ':members', 0, -1);
};Awards.revokeMember = async function (uid, badgeId) {
const award = await Awards.getMemberAward(uid, badgeId);if (!award) { return null; } award.active = false; award.dateRevoked = Date.now(); await db.setObject(keys.memberAward(uid, badgeId), award); await db.sortedSetRemove(keys.member(uid), badgeId); await db.sortedSetRemove(keys.badge(badgeId) + ':members', uid); return award;};
Awards.updateBadge = async function (badge) {
if (!badge || !badge.id) {
throw new Error('Badge id is required');
}const existing = await Awards.getBadge(badge.id); if (!existing) { throw new Error(`Badge ${badge.id} does not exist`); } const updated = Object.assign({}, existing, badge); await db.setObject(keys.badge(badge.id), updated); const score = Number.isFinite(Number(updated.displayOrder)) ? Number(updated.displayOrder) : (Number(updated.timeAdded) || 0); await db.sortedSetAdd(keys.badges, score, updated.id); return updated;};
Backups:
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.before-schema
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.before-member-awards
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.working-db-test
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.known-good-data-layer
/opt/app/nodebb-plugin-mto-awards/library.js.known-good
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-manage-page
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-editor
/usr/src/app/nodebb-plugin-mto-awards/templates/mto-awards-manage.tpl.before-editor
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-real-save
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-real-save-2
/usr/src/app/nodebb-plugin-mto-awards/templates/mto-awards-edit.tpl.before-real-save
One backup command previously failed because /opt/app/... is a host path and isn't visible inside the container. Correct container path is /usr/src/app/....
One accidental node --check was run on the host due to missing docker exec; host reported node: command not found. Later in-container syntax check passed. Do not interpret the old host error as a NodeBB problem.
- Current library.js Architecture
Current library.js begins with:
'use strict';
const user = nodebb.require('./src/user');
const Awards = require('./lib/awards');const plugin = {};
async function canManageAwards(uid) {
const isAdministrator = await user.isAdministrator(uid);
if (isAdministrator) {
return true;
}return await user.isModeratorOfAnyCategory(uid);}
Important policy:
ALL moderators have full Merit Badge management access across the entire forum, plus administrators.
Do NOT give moderators ACP access merely to manage badges.
plugin.init = async function (params) { ... }
The plugin currently has:
Catalogue route
router.get('/mto-awards', middleware.buildHeader, async function (req, res) {
try {
const badges = await Awards.listBadges();
console.log('[MTO Awards] Catalogue requested:', badges.map(badge => badge && badge.id));
res.render('mto-awards', { badges: badges || [] });
} catch (err) {
console.error('[MTO Awards] Catalogue error:', err);
res.status(500).send('Unable to load Merit Badges.');
}
});Management route
router.get('/mto-awards/manage', middleware.buildHeader, async function (req, res) {
try {
if (!await canManageAwards(req.uid)) {
return res.status(403).send('[[error:no-privileges]]');
}const badges = await Awards.listBadges(); res.render('mto-awards-manage', { badges: badges || [], }); } catch (err) { console.error('[MTO Awards] Management access error:', err); res.status(500).send('Unable to load Merit Badge Management.'); }});
Add badge GET
router.get('/mto-awards/manage/add', middleware.buildHeader, async function (req, res) {
try {
if (!await canManageAwards(req.uid)) {
return res.status(403).send('[[error:no-privileges]]');
}res.render('mto-awards-edit'); } catch (err) { console.error('[MTO Awards] Add badge page error:', err); res.status(500).send('Unable to load Merit Badge editor.'); }});
Current Add badge POST
The POST route currently ONLY proves that protected submission works:
router.post('/mto-awards/manage/add', middleware.applyCSRF, async function (req, res) {
try {
if (!await canManageAwards(req.uid)) {
return res.status(403).send('[[error:no-privileges]]');
}console.log('[MTO Awards] Add badge POST received.'); res.status(200).send('Add badge POST received.'); } catch (err) { console.error('[MTO Awards] Add badge POST error:', err); res.status(500).send('Unable to process Merit Badge.'); }});
This is the ONLY unfinished part of today's Add Badge work.
- Management Template
Current /templates/mto-awards-manage.tpl:
<div class="container">
<div class="row">
<div class="col-12">
<div class="d-flex justify-content-between align-items-center mb-3">
<div>
<h1>Merit Badge Management</h1>
<p class="text-muted mb-0">Manage the MTO Merit Badge catalogue.</p>
</div>
<button type="button" class="btn btn-primary" disabled>
Add Merit Badge
</button>
</div>{{{ if badges.length }}} <div class="table-responsive"> <table class="table table-bordered table-hover align-middle"> <thead> <tr> <th>Badge</th> <th>Category</th> <th>Requestable</th> <th>Assignable</th> <th>Action</th> </tr> </thead> <tbody> {{{ each badges }}} <tr> <td><strong>{badges.name}</strong></td> <td>{badges.category}</td> <td> {{{ if badges.requestable }}} Yes {{{ else }}} No {{{ end }}} </td> <td> {{{ if badges.assignable }}} Yes {{{ else }}} No {{{ end }}} </td> <td> <button type="button" class="btn btn-sm btn-secondary" disabled> Edit </button> </td> </tr> {{{ end }}} </tbody> </table> </div> {{{ else }}} <div class="alert alert-info"> No Merit Badges have been added yet. </div> {{{ end }}} </div> </div></div>
The Add button is still disabled and should eventually become a link to:
/mto-awards/manage/add
The Edit button is also currently disabled and will be implemented later.
A Delete/Remove action will also be needed because the user expects badge pruning.
- Add Badge Editor
Current /templates/mto-awards-edit.tpl has:
Badge name
Category
Description
Requestable checkbox
Assignable checkbox
Full badge upload placeholder
Mini badge upload placeholder
Save Badge
Cancel
The artwork file inputs remain disabled intentionally until editor/permissions are tested.
Important change made today
The form fields were just wired with name attributes:
name β name="name"
category β name="category"
description β name="description"
requestable β name="requestable" value="1"
assignable β name="assignable" value="1"
Name/category/description are required.
This template change was successfully written before the last failed library replacement attempt.
- Today's Successful Test
We tested the Add Badge form with harmless test data.
The browser returned:
Add badge POST received.
This confirmed:
Form submits correctly.
POST route is reachable.
CSRF protection works.
Moderator/admin authorization works.
NodeBB loaded the route correctly.
No Redis write happens yet.
The test did NOT create a badge.
- Last Two Failed Replacement Attempts
Two attempts were made to replace the placeholder POST route with the real Redis-saving implementation.
First attempt
Failed because the replacement string did not match the route's exact indentation.
Error:
Error: Could not find the existing Add badge POST route.
No library change occurred.
Second attempt
Attempted to locate route boundaries using:
const start = l.indexOf("router.post('/mto-awards/manage/add'");
const end = l.indexOf("\n\t\trouter.get('/mto-awards/manage/add'", start);It failed because the actual file uses spaces rather than the exact tab sequence assumed.
Error:
Error: Could not locate Add badge POST route boundaries.
Again, no library change occurred.
The syntax check after the attempt reported:
LIBRARY_SYNTAX_EXIT=0
This only confirms the existing library.js remains valid. It does NOT mean the real save route was installed.
- Where We Intentionally Stopped
User said they may be running out of daytime and wants a sensible stopping point.
We agreed to STOP HERE.
Do not restart NodeBB tonight.
Do not run additional edits tonight unless absolutely necessary.
Current state is safe.
Next session should begin by inspecting or carefully editing the actual POST route rather than using brittle whitespace-dependent replacement.
- Exact Next Step
The intended next implementation is:
Replace the placeholder POST handler with a real protected save handler that:
Checks canManageAwards(req.uid).
Reads:
req.body.category
req.body.description
req.body.requestable
req.body.assignable
Validates required fields.
Validates category against:
User
Site
Modification
Collector
Challenge
Generates a unique internal badge ID.
Creates a badge object with approximately:
id
name
category
description
requestable
assignable
timeAdded
displayOrder
Calls:
await Awards.createBadge(badge)Redirects to:
/mto-awards/manageThen:
syntax check
restart NodeBB
create one harmless test badge
verify it appears in management/catalogue
then move on to Edit/Delete
Do NOT implement artwork upload in the same step.
- Planned Future Work
After real badge creation is verified:
A. Management UI
Enable Add button.
Add Edit.
Add Delete/Remove with confirmation.
Preserve moderator/admin permission check.
Possibly show artwork status.
B. Artwork Upload
Need protected upload handling using NodeBB's upload infrastructure.
Requirements:
full artwork exactly 50 Γ 60 PNG
mini artwork exactly 25 Γ 25 PNG
transparent corners
moderator/admin only
CSRF protection
files stored in NodeBB uploads volume
do NOT simply rely on normal post image upload permissions
C. Member Awarding
Staff can select member.
Staff can select badge.
Staff can award.
Date received should be supported for historical migration.
Revoke/remove member award.
Avoid duplicate active awards.
D. Member Awards Page
Show owned badges.
Eventually favorites.
Historical dates/comments as appropriate.
E. Requests
Phase 1 should support requestable awards.
Desired workflow:
Member submits evidence URL β staff reviews β approve/reject β award.
Phase 2 can make this into a more polished request queue.
F. Theme Presentation
Theme should render mini badges beneath signatures.
Max 21 displayed in a post.
No mobile display.
Plugin supplies badge data.
Theme handles visual presentation.
G. Historical Migration
Eventually migrate:
194 legacy badge definitions
legacy categories
artwork
member award assignments
dates
active status
relevant comments/favorites where useful
Do this only after the new system is stable.
- Useful Existing Backups
If something goes wrong, known backups include:
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.known-good-data-layer
/opt/app/nodebb-plugin-mto-awards/library.js.known-good
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-manage-page
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-editor
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-real-save
/usr/src/app/nodebb-plugin-mto-awards/library.js.before-real-save-2
/usr/src/app/nodebb-plugin-mto-awards/templates/mto-awards-manage.tpl.before-editor
/usr/src/app/nodebb-plugin-mto-awards/templates/mto-awards-edit.tpl.before-real-saveRemember:
/opt/app/... is the host-side path.
/usr/src/app/... is the container-side path.
- User Preferences / Working Style
The user wants this project handled incrementally.
Preferred rhythm:
Give one small command block.
User runs it.
User pastes exact output.
Interpret it.
Only then give next command.
Avoid giving a huge sequence of commands.
The user appreciates practical reassurance when a failed edit is harmless.
When there is a natural stopping point, say so rather than pushing onward.
Current stopping point is intentional and safe.
- Handoff Summary
The MTO Merit Badge system is not broken.
We have a working NodeBB plugin skeleton, working Redis data layer, working management route, working Add Badge page, working CSRF protection, and working moderator/admin authorization.
The remaining immediate task is simply:
Turn the already-tested Add Badge POST handler from a proof-of-concept response into a real Awards.createBadge() call.
Do that carefully next session, then restart NodeBB and test one badge.
Do not jump ahead to artwork uploads, migration, requests, or theme rendering until badge creation is verified.
-
And to keep things straight, here is the list of rules I have developed:
The MTO project rules
- The SMF database/data is the highest authority
This is the most important rule going forward.
We are migrating an existing community, not inventing a new one.
So when something already exists in SMFβmembers, usernames, groups/ranks, posts, topics, awards, dates, historical relationships, etc.βwe should treat the SMF data as the authoritative source and build NodeBB around it.
That means:
Don't invent data that should come from SMF.
Don't hard-code member ranks/groups when those should eventually be imported.
Don't make up award assignments.
Don't replace historical data with approximations merely because it's easier.
Don't design a new data model that loses information from SMF without a deliberate decision.
When we aren't sure how something worked historically, inspect the SMF data/package/code first.
UI decisions that depend on migration data should generally wait until we understand that data.The awards work makes this especially explicit: the legacy system contains the badge definitions, categories, member assignments, dates, active status, etc., and the intention is to preserve those during historical migration.
In short:
SMF tells us what the community is. NodeBB provides the platform on which we reproduce it.
- Prefer simplicity over cleverness
This has become one of our strongest recurring rules.
If a simple native NodeBB mechanism works, use it.
If a small CSS rule solves the problem, don't build JavaScript.
If a template can do something, don't build a DOM-rewriting system to accomplish the same thing.
If something is already "good enough," stop.
We've repeatedly backed away from increasingly clever implementations in favor of simpler onesβfor example, using native Harmony/NodeBB controls rather than recreating them, and replacing a complicated JavaScript bottom-bar approach with a normal server-rendered template.
The practical rule is:
The simplest solution that preserves the required behavior wins.
- Preserve native NodeBB functionality wherever possible
The goal is SMF-inspired NodeBB, not a literal SMF clone.
We want the appearance and workflow to feel familiar, but underneath it should remain NodeBB.
So:
Use native Reply.
Use native Quote.
Use native Watch.
Use native Share.
Use native Print.
Use native pagination.
Use native login/registration.
Use native composer functionality.
Use native NodeBB events/hooks where available.We shouldn't sacrifice a reliable NodeBB mechanism merely to reproduce a tiny visual difference from SMF.
This principle appears repeatedly in the logs: keep Harmony/NodeBB functionality, modify the MTO theme, and prefer existing functionality over custom implementations.
- SMF-inspired, not pixel-perfect SMF
The visual target is very clear:
compact, dense, traditional forum, MTO-branded, less "Bootstrap card," broad posts, narrow author rail.
But we are not trying to reproduce every pixel of the old SMF installation.
The desired characteristics are explicitly described as:
compact
information-dense
broad post content
relatively narrow author column
restrained borders
less card-based
green/olive MTO branding
related light/dark themes
useful sidebar/ad space
native responsive behavior
native NodeBB functionalityAnd we've explicitly accepted small imperfections when they're not worth the effort.
For example, toolbar spacing and the sidebar gap were consciously left alone because the result was already good enough.
So:
Get the big SMF characteristics right. Don't spend an hour perfecting a minor detail while major discrepancies remain.
- Functionality beats aesthetics
This is probably the second-most important rule after data preservation.
We do not make the site look more like SMF if doing so makes NodeBB less reliable.
The logs actually state this directly:
Do not optimize aesthetics at the expense of native NodeBB functionality.
That means, for example:
Don't replace native Watch just because SMF calls it "Notify."
Don't invent a poll system simply because SMF has one.
Don't use unsupported API shortcuts to make Bookmark behave differently.
Don't break editing to make post layout prettier.
Don't remove a NodeBB feature merely because it doesn't look exactly like SMF.
6. Inspect before changingThis is a major technical rule we've developed through experience.
Never guess what a NodeBB element is.
Before changing something:
Inspect the actual template.
Inspect the actual rendered DOM.
Identify the real selector/component.
Determine what owns the behavior.
Test the proposed change.
Only then make it permanent.The quote problem is a perfect example: we initially treated post/parent as the quote, but inspection showed that the actual quoted content was the <blockquote> inside post/content.
Likewise, we learned not to assume an element such as post/summary was responsible when the actual component was post/reply-count.
So:
Inspect the real DOM/template. Don't work from assumptions.
- One focused change at a time
Don't combine unrelated modifications.
The preferred editing sequence is:
inspect β checkpoint β one change β verify β build β test β checkpoint
The older handoff gives this almost verbatim as the editing safety procedure.
This makes it possible to answer:
"What did we just change, and did that cause the problem?"
rather than having ten simultaneous variables.
- Read-only investigation first
Whenever practical, investigate without changing anything.
Especially for:
databases
Redis
ACP settings
NodeBB configuration
existing templates
installed plugins
legacy SMF structuresWe've specifically adopted this for the ACP retirement work: locate the actual persisted configuration first, classify it, and only then change it.
That same philosophy should apply even more strongly to the SMF database.
- Never blindly delete or overwrite something
This applies particularly to:
SMF data
Redis
ACP CSS/JS
theme files
NodeBB configuration
existing functionalityFor example, the ACP CSS was not simply deleted wholesale. Each area was audited against the MTO theme and classified as:
REMOVE / KEEP / MOVE / OBSOLETE.
Only after that should the redundant layer be disabled.
The same principle should govern the migration database:
Understand ownership and dependencies before removing anything.
- Back up before permanent changes
This has become standard operating procedure.
Before a significant modification:
make a known-good backup/checkpoint
make the change
verify it
record the resulting state/hash where usefulWe've done this repeatedly for theme.scss, JavaScript, ACP CSS, templates, and the awards data layer.
The newer philosophy is also to eventually have a clean archival/checkpoint strategy, rather than accumulating random timestamped backup files forever.
- Known-good beats theoretically cleaner
This is an important practical rule.
If something is working, don't rewrite it just because it could theoretically be cleaner.
We've explicitly recorded:
don't casually rewrite the working bottom footer;
don't rip apart the working Composer CSS;
don't revisit accepted imperfections;
don't perform another broad theme.scss cleanup merely because there are things that could be tidied.The current theme was considered stable enough that the next work should focus elsewhere rather than cosmetic cleanup.
So:
A working ugly solution is preferable to a beautiful regression.
- Prototype first; refactor later
We've recognized that incremental patching is useful during discoveryβbut it should not become the final architecture.
The intended lifecycle is:
prototype β stabilize β freeze baseline β audit β refactor
The logs explicitly say that the incremental changes are acceptable as prototyping but should not become the final architecture.
Once the UI/data model is stable:
inventory files
identify active code
remove dead code
consolidate CSS
remove duplicates
clarify Harmony ownership
keep only intentional MTO overrides
document why customizations exist
ideally put the cleaned project under Git/version control
13. One owner for each responsibilityWe've also established a much cleaner architecture.
Harmony
Owns the underlying NodeBB theme/platform behavior.
MTO theme
Owns presentation:
MTO visual styling
templates
author rail
signatures
layout
presentation of badges
MTO pluginOwns data and business rules.
The awards system makes this explicit:
nodebb-plugin-mto-awards owns badge data/business rules; nodebb-theme-mto owns badge presentation.
That separation should extend to the whole project.
- Don't duplicate functionality
If NodeBB already provides something, don't create an MTO version of it unless there's a compelling reason.
This is why we're moving away from:
duplicate JavaScript
fake buttons
DOM cloning
timing hacks
direct API calls that bypass NodeBB's normal mechanisms
unnecessary ACP overridesThe Bookmark investigation is a good example: direct fetch() produced a 403, and the decision was to use NodeBB's proper internal mechanism if we ever revisit it.
- Don't resurrect abandoned approaches
If an approach was found to be wrong or dangerous, it's part of the project's institutional knowledge.
Examples:
Don't resurrect the MutationObserver button-label experimentβit caused a site-wide hang.
Don't revive the old JavaScript bottom-topic-bar implementation.
Don't use direct Bookmark API fetch().
Don't simply set entire post containers to overflow: visible.
Don't paste browser JavaScript into the Linux shell.
Don't return to old CSS hacks simply because they're still visible somewhere.In other words:
A failed experiment becomes a constraint on future solutions.
- Use the right layer for the job
We've gradually established:
Need Preferred location
Core NodeBB behavior NodeBB
Base visual framework Harmony
MTO presentation nodebb-theme-mto
MTO CSS theme.scss
MTO templates theme templates
MTO-specific client behavior MTO JS
MTO data/business rules MTO plugin
Historical community data SMF database/import
Temporary experimentation browser/dev tools
Legacy ACP customization eventually retiredThe current theme architecture explicitly reflects this separation.
- ACP Custom CSS/JS is not the permanent home
The long-term direction is to move MTO-specific functionality out of the ACP and into the actual theme/plugin.
But not blindly.
The rule is:
Determine what ACP code does.
Determine whether MTO already owns it.
If fully duplicated β remove it.
If still needed β keep it.
If functionality belongs in the theme β move it.
Only disable the ACP layer once the replacement is proven.That's why the ACP cleanup was deliberately treated as an ownership audit rather than a deletion exercise.
- Test the actual user experience, not just the code
A successful build isn't enough.
We repeatedly use:
browser testing
actual rendered HTML
desktop checks
mobile checks
Incognito/logged-out checks
actual phone testing
functional interaction testingFor example, the mobile NodeBB navigator wasn't considered fixed until it was confirmed gone on the actual Android phone.
Likewise, registration wasn't simply considered done because the template rendered; it was tested in Incognito.
- Mobile is not an afterthought
The target isn't just "desktop SMF-looking."
Every significant UI change should consider:
responsive layout
touch interaction
mobile spacing
mobile navigation
whether a desktop-only element should disappear
whether information density becomes oppressive on small screensWe've deliberately hidden things like the mobile progress navigator and badge display where appropriate, while preserving native responsive behavior.
- Defer things that depend on the migration
This has become particularly important now.
If a decision depends on:
the permanent domain
email infrastructure
SMF member data
account mapping
groups/ranks
permissions
historical imports
legacy configurationdon't prematurely lock it in.
The registration settings are a good example: approval, email verification, username policy, account mapping, etc. were deliberately deferred because the SMF migration and permanent infrastructure hadn't happened yet.
- Phase things instead of building everything at once
The Awards project demonstrates this especially well.
Phase 1
Build the core:
catalogue
categories
artwork
manual awarding
revoke/remove
member awards
display
requestable awards
historical migration
Phase 2Add more sophisticated features:
request queue
favorite badge
automatic triggers
advanced legacy "cleverness"The explicit philosophy is:
The computer handles the paperwork; humans make the award decision.
That's a good general model for the whole project.
- Don't build Phase 2 complexity before Phase 1 works
This is particularly important for the database/plugin work we're entering now.
For example, the current Awards instruction is essentially:
Get the already-tested Add Badge POST handler to actually create a badge β test one badge β only then proceed to artwork, migration, requests, rendering, etc.
That's exactly how we should approach the SMF migration.
- Get the big things right first
The project has a natural priority hierarchy:
Preserve data
Preserve functionality
Get major SMF workflows/UI right
Make the architecture clean
Polish
Tiny visual differencesThe logs literally summarize the philosophy as:
"Get the big things right first."
- When something is good enough, bank it
This is another surprisingly important rule.
Once something is:
working,
visually acceptable,
tested,
backed up,stop touching it.
Examples include:
bottom topic footer
standalone Composer
global dark mode
logged-out experience
registration presentation
quote treatment
reply history
paginationThe logs repeatedly mark these as DONE and explicitly warn against reopening them unnecessarily.
- The operational rule: small command blocks
Because you're not working as a full-time coder, we've also established a workflow rule for how I should guide you:
One small command block β you run it β you paste the exact output β I interpret it β next command.
Not a 40-command wall of shell commands.
And commands must be clearly separated by environment:
Linux/Docker commands β SSH shell
browser JavaScript β browser DevTools
SCSS/template content β filesThat distinction was explicitly documented after some painful shell/browser confusion.
The "constitution" I'd use from now on
If I boil everything down to the rules that matter most, I'd write them like this:
MTO/NodeBB Development Rules
SMF data is authoritative. Preserve historical truth; don't invent data.
NodeBB is the application platform; don't fight its native architecture unnecessarily.
Prefer the simplest solution that works.
Preserve native NodeBB functionality unless there is a compelling reason not to.
Make the result SMF-inspired, not obsessively pixel-perfect.
Functionality beats aesthetics.
Inspect the real DOM, templates, database structures, and code before changing anything.
Never guess at ownership or selectors.
Make one focused change at a time.
Read-only investigation before destructive changes.
Back up/checkpoint before permanent changes.
Never blindly delete, overwrite, or migrate data.
Don't disturb a known-good system just to make it theoretically cleaner.
Prototype incrementally; refactor only after the design is stable.
Keep responsibilities separated: NodeBB / Harmony / MTO theme / MTO plugin / SMF data.
Avoid duplicate implementations and unnecessary JavaScript.
Don't resurrect approaches we've already rejected because they caused problems.
Test the actual user experience on desktop, mobile, logged-in, and logged-out states where relevant.
Defer configuration that depends on the eventual SMF migration or production infrastructure.
Build in phases; prove the smallest working piece before adding complexity.
Get the major things right before polishing minor things.
When something is tested and good enough, freeze it and move on.
Keep the final system maintainable, documented, and free of dead/duplicate code.
When guiding implementation, use small, understandable command steps and explain what the result means.And I think there is one new overarching rule that has become necessary now that we're moving deeper into the SMF migration:
Data first, UI second.
If a proposed NodeBB feature requires us to make assumptions about what the old forum's members, awards, permissions, ranks, groups, or historical records mean, we stop and inspect the SMF database/package first.
That is the natural evolution of everything we've learned so far. The UI we've been building is essentially a shell around the community's existing identity and history. The SMF migration needs to determine what goes inside that shellβnot the other way around
-
Good news everyone!
While taking a short break from the task of creating the whole merit badge system, I have changed the Default Avatar on the new forum from a bland circle with a first initial in it to this one, which was inspired by a certain lobster who tried to use his (terrible) company's health plan to get a new shell.
Def


-
I didn't get as much as I wanted done today, but here is what I did get done:
MTO Merit Badges β Daily Handoff Log
Date: 2026-09-23
Project: Multitool.Org (MTO) NodeBB Merit Badge recreation
Status: Phase 1 prototype is working; historical migration not yet started.Operating rules
-
SMF is authoritative for historical data: badge definitions, IDs, names, categories, descriptions, artwork associations, member awards, dates, active/revoked state, historical comments/favorites/request information.
-
Do not invent migration data or reconcile discrepancies by guessing.
-
Ownership:
- SMF = historical/source data
- MTO Awards plugin = badge definitions, awards, requests, business rules, artwork serving
- MTO theme = presentation
- Harmony/NodeBB = native functionality where practical
-
Inspect before changing.
-
One focused change at a time.
-
Back up before permanent changes.
-
Test actual UX.
-
Mobile matters.
-
Known-good > theoretically cleaner.
-
Prototype first, refactor later.
-
Operational pattern: inspect β checkpoint β one change β verify β build/test β checkpoint.
-
User prefers one small command block at a time, then exact output pasted back.
Current environment
NodeBB
- Container:
app-nodebb-1 - NodeBB: v4.16.0
- Image:
elestio/nodebb:latest - Container root:
/usr/src/app - Host plugin:
/opt/app/nodebb-plugin-mto-awards - Container plugin:
/usr/src/app/nodebb-plugin-mto-awards - Host theme:
/opt/app/nodebb-theme-mto - Container theme:
/usr/src/app/nodebb-theme-mto - NodeBB listens on
0.0.0.0:4567 - Public site:
https://multitool.ninja - Canonical URL currently seen in NodeBB logs is the Elestio URL.
- Public site/routes have returned HTTP 200.
Do not revisit Chrome QUIC/browser networking experiments. Those were investigated already and are not the MTO problem.
Phase 1 functionality now working
Catalogue
-
Merit Badge catalogue route:
/mto-awards -
Five categories:
- Site
- Collector
- Modification
- User
- Challenge
-
Demo badges currently seed if no badges exist.
-
Requestable badges show request forms.
-
Full/mini artwork infrastructure exists.
Manual awarding
Working:
- Staff can manually award a badge.
- Badge appears on member profile.
- Duplicate active award is prevented.
- Badge can be revoked/removed.
- Revoke was tested.
Profile integration
Native Harmony/NodeBB widget works:
Merit Badges widget appears in member profile.
MTO theme registered widget areas and the widget was successfully placed in:
About me (after)
Member request workflow
Fully tested end-to-end.
Flow:
Member submits request β Pending Requests β Staff reviews β Approve OR RejectBoth branches have been tested.
Approve
- Request submitted by Fred.
- Admin saw it in Pending Requests.
- Approval worked.
- Badge was awarded.
- Badge appeared on Fred's profile.
Reject
- Fred's request was rejected.
- Confirmation was displayed.
- Request rejection appeared to work.
- Fred's profile was checked afterward.
- No new badge appeared.
Therefore:
request submission
pending queue
approval
award on approval
rejection
no award on rejection
Management navigation
Previously broken because NodeBB v4.16 Ajaxify was intercepting plugin links and attempting to load nonexistent client templates.
The final working solution was adding:
onclick="event.stopPropagation();" target="_self"to MTO management links.
This has now been tested successfully.
Verified working:
Pending Requests
Award Merit Badge
Add Merit Badge
Back to Management
Edit link was the remaining planned check; Pending/Award/Add were confirmed working after the fix. Back to Management was explicitly confirmed working.
Do not reopen this issue unless a new regression appears.
There is also a theme capture-phase navigation handler in:
/opt/app/nodebb-theme-mto/static/lib/mto-topic-actions.jsIt was tried during diagnosis and may now be redundant, but it is currently known-good and should not be removed casually.
Current known caveat
Approve currently does:
Awards.awardMember()Awards.updateRequest()
If step 1 succeeds and step 2 fails, theoretically the badge could be awarded while the request remains pending.
This is a robustness/transaction-ordering improvement for later.
Do not derail the working Phase 1 workflow for this unless we deliberately decide to harden it.
Current plugin architecture
Package:
nodebb-plugin-mto-awardsVersion:
0.1.0Compatibility:
^4.15.0Main:
library.jsPlugin hooks:
{ "hook": "static:app.load", "method": "init" }, { "hook": "filter:widget.render:mto-awards", "method": "renderMemberAwardsWidget" }, { "hook": "filter:widgets.getWidgets", "method": "defineWidgets" }Static images:
"staticDirs": { "images": "public/images" }
Core Redis data model
Prefix:
mto:awardsKeys include:
mto:awards:badges mto:awards:badge:<id> mto:awards:member:<uid> mto:awards:member:<uid>:<badgeId> mto:awards:requests mto:awards:request:<id>Badge creation stores the badge object and sorted-set membership.
Member awards are stored separately and indexed by member and badge.
Requests have their own objects and sorted-set index.
Boolean normalization fix
Redis
setObjectstringifies booleans.This caused
requestable/assignablevalues to come back as strings.Awards.getBadge()now normalizes them:if (typeof badge.requestable === 'string') { badge.requestable = badge.requestable === 'true'; } if (typeof badge.assignable === 'string') { badge.assignable = badge.assignable === 'true'; }Backup:
/opt/app/nodebb-plugin-mto-awards/lib/awards.js.before-boolean-normalizationThis is working.
Demo badges
Currently seeded:
ID Badge Category Requestable demo-userHelpful Human User No demo-siteMTO Citizen Site No demo-modificationMod Squad Modification Yes demo-collectorCollector Collector Yes demo-challengeChallenge Accepted Challenge Yes initalso deletes:__mto_test_badge__
Fred test data
Fred UID:
3Currently known historical/demo awards include:
demo-userβ Helpful Humandemo-siteβ MTO Citizendemo-modificationβ Mod Squad
These were manually awarded test/demo awards.
Do not delete yet.
They should eventually be deliberately cleaned up before/when the real SMF historical migration occurs.
Fred's request for Challenge Accepted was used to test the request workflow and was subsequently rejected.
Artwork archive
Uploaded archive:
awards.zipAvailable at:
/mnt/data/mto-awards-inspect/awards.zipInspection found:
-
401 total archive entries
-
396 PNGs
-
205 distinct artwork IDs
-
Full artwork: 50Γ60
-
Mini artwork: 25Γ25 where present
-
191 minis
-
14 missing minis:
- 15
- 16
- 91
- 112
- 207
- 208
- 209
- 210
- 211
- 212
- 214
- 215
- 217
- 218
Important:
205 artwork IDs β 194 legacy badges.
Do not assume a one-to-one relationship.
Historical SMF data
This is the next major Phase 1 task, but migration has NOT started.
Legacy plugin:
spuds:member_awardsVersion:
3.0Target SMF:
2.0β2.0.99Expected historical catalogue:
Category Count Site 18 Collector 32 Modification 5 User 27 Challenge 112 Total 194 SMF
awardsfields requested:id_award award_name description id_category time_added filename minifile award_trigger award_type award_location award_requestable award_assignableAward types include:
- Manual
- Post count
- Top posters
- Topic count
- Top topic starters
- Time online
- Member since
- Karma
Display locations:
- Below avatar
- Above avatar
- Signature
- Off
Image formats:
- Full frame
- Heading
- No frame
Historical member-award data:
awards_membersNeed:
- member/user ID
- award/badge ID
- date received
- favorite
- award type
- active
- comments
- any additional columns
Historical requests may be represented by inactive
awards_membersrows; preserve them exactly.Need SMF member ID β username and existing SMFβNodeBB mapping.
Need original artwork archive including unused artwork.
Need schemas /
SHOW CREATE TABLEfor:- awards
- awards_members
- categories
- requests
Also:
- SMF version
- plugin version/configuration
Requested sysadmin package:
smf-awards/ βββ awards.sql βββ awards_members.sql βββ categories.sql βββ requests.sql βββ members-award-map.csv βββ artwork/ βββ schema/Instruction to sysadmin:
Preserve historical/inactive/revoked records. Do not clean, dedupe, rename, reconcile, or import yet.
Checkpoint created tonight
This is important.
At:
2026-09-23 23:08:29
Full filesystem checkpoint was successfully created.
Plugin:
/opt/app/nodebb-plugin-mto-awards.checkpoint-20260923-230829Theme:
/opt/app/nodebb-theme-mto.checkpoint-20260923-230829Command completed with:
CHECKPOINT CREATED Plugin: /opt/app/nodebb-plugin-mto-awards.checkpoint-20260923-230829 Theme: /opt/app/nodebb-theme-mto.checkpoint-20260923-230829This is the known-good rollback point.
Important backups already made
Examples:
lib/awards.js.before-boolean-normalization lib/awards.js.before-member-requests lib/awards.js.before-request-review templates/mto-awards.tpl.before-catalogue-polish templates/mto-awards.tpl.before-request-form templates/mto-awards-requests.tpl.before-request-review templates/mto-awards-manage.tpl.before-requests-queue templates/mto-awards-award.tpl.before-inline-nav templates/mto-awards-requests.tpl.before-inline-nav templates/mto-awards-manage.tpl.before-inline-nav library.js.before-request-review theme/static/lib/mto-topic-actions.js.before-capture-nav-fix theme/plugin.json.before-widget-areas
What NOT to do tomorrow
- Do not redo the navigation investigation.
- Do not change working request approval/rejection merely for aesthetics.
- Do not delete demo awards yet.
- Do not start historical migration without the SMF export.
- Do not guess which artwork corresponds to which historical badge.
- Do not reconcile the 205 artwork IDs against the 194 badges without SMF evidence.
- Do not introduce Phase 2 automation/triggers yet.
- Do not chase unrelated service-worker/font warnings unless they become relevant.
- Do not experiment with Chrome QUIC/network settings.
Tomorrow's recommended starting point
First question should be:
Has the SMF sysadmin export arrived?
If NO:
Do not manufacture work. We can inspect the current implementation and identify any remaining Phase 1 gaps, but historical migration waits for authoritative data.
If YES:
Do not import immediately.
First:
- Inspect the export structure.
- Verify counts.
- Verify category IDs/names/order.
- Verify badge IDs.
- Verify member-award records.
- Verify request/inactive records.
- Verify member mapping.
- Inspect artwork filenames against the actual SMF records.
- Produce a migration mapping/dry run.
- Only then discuss import.
Bottom line
Tonight we reached a solid checkpoint:
The MTO Merit Badge prototype is operational through the complete manual/request/review lifecycle, and the working plugin + theme have been checkpointed.
The project is now ready to move from building/testing the Phase 1 machinery toward authoritative SMF historical-data preparation.
Known-good checkpoint:
20260923-230829If tomorrow's version of me reads only this handoff, it should not start over.
-
-
Working on BBCode today- Merit Badges are largely done, just need to import them.
Spoiler:
This is how the spoiler works.Def
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