Skip to content
  • Categories
  • Recent
  • Popular
  • World
Skins
  • Light
  • Dark

Collapse

NodeBB

MTO- NodeBB on Elestio

Scheduled Pinned Locked Moved Website Maintenance
83 Posts 1 Posters 338 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SteveCS
    SteveCS
    SteveC
    Global Moderators
    wrote on last edited by
    #22

    Can you add a hide the side community links button? So the page can be wider to view like we have here. Also widen the page in general.

    1 Reply Last reply
    0
    • Grant LamontagneG
      Grant LamontagneG
      Grant Lamontagne
      administrators
      wrote on last edited by
      #23

      Yeah, I am not happy with the width currently and will be widening the forum some more. It was a bit of a struggle to get it to where it was, and I will try to get it dialed in a bit better. I got to a point where good enough was good enough and decided to get onto other problems.

      But yes, I absolutely will widen it a bit.

      Def


      1 Reply Last reply
      0
      • Grant LamontagneG
        Grant LamontagneG
        Grant Lamontagne
        administrators
        wrote on last edited by
        #24

        Bookmarks, Print, and Share buttons should now be functional. Watch/Unwatch/Ignore buttons should now be functional.

        Def


        1 Reply Last reply
        0
        • SteveCS
          SteveCS
          SteveC
          Global Moderators
          wrote on last edited by
          #25

          One thing I've noticed is that the green font is hard to read in dark mode. Also the signature box being green is a bit distracting. Maybe it's just the color theme being used. I think something closer to what we have now would be better, maybe that's still in the works :dunno:

          1 Reply Last reply
          0
          • Grant LamontagneG
            Grant LamontagneG
            Grant Lamontagne
            administrators
            wrote on last edited by
            #26

            Day/night mode is working now.

            I will work on getting the text a little more visible in night mode.

            Def


            1 Reply Last reply
            0
            • SteveCS
              SteveCS
              SteveC
              Global Moderators
              wrote on last edited by
              #27

              New forum acting a bit squirrely today. Having trouble editing my own post but only in one topic :dunno:

              Reply button is including previous post.

              1 Reply Last reply
              0
              • Grant LamontagneG
                Grant LamontagneG
                Grant Lamontagne
                administrators
                wrote on last edited by
                #28

                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


                1 Reply Last reply
                0
                • SteveCS
                  SteveCS
                  SteveC
                  Global Moderators
                  wrote on last edited by
                  #29

                  @Grant Lamontagne said:
                  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

                  👍

                  1 Reply Last reply
                  0
                  • Grant LamontagneG
                    Grant LamontagneG
                    Grant Lamontagne
                    administrators
                    wrote on last edited by
                    #30

                    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


                    1 Reply Last reply
                    0
                    • Grant LamontagneG
                      Grant LamontagneG
                      Grant Lamontagne
                      administrators
                      wrote on last edited by
                      #31

                      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. :bnghd:

                      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. :facepalm:

                      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


                      1 Reply Last reply
                      0
                      • SteveCS
                        SteveCS
                        SteveC
                        Global Moderators
                        wrote on last edited by
                        #32

                        First spam on new site ?

                        https://nodebb-vklpj-u73921.vm.elestio.app/post-queue/topic-1787568190680

                        1 Reply Last reply
                        0
                        • Grant LamontagneG
                          Grant LamontagneG
                          Grant Lamontagne
                          administrators
                          wrote on last edited by
                          #33

                          I saw that and deleted it and the spammer.

                          It feels real now, doesn't it? 😄

                          Def


                          1 Reply Last reply
                          0
                          • SteveCS
                            SteveCS
                            SteveC
                            Global Moderators
                            wrote on last edited by
                            #34

                            @Grant Lamontagne said:
                            I saw that and deleted it and the spammer.

                            It feels real now, doesn't it? 😄

                            Def

                            I thought I'd leave the inaugural ban to you 😄

                            1 Reply Last reply
                            0
                            • Grant LamontagneG
                              Grant LamontagneG
                              Grant Lamontagne
                              administrators
                              wrote on last edited by
                              #35

                              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 customCSS and into the MTO-owned theme:

                              /usr/src/app/nodebb-theme-mto/theme.scss
                              

                              The 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.scss
                              

                              Inserted immediately before:

                              General cards and surfaces
                              

                              Theme header section:

                              MTO — Global Header
                              

                              It owns:

                              • #mtorg-header
                              • .mtorg-logo
                              • .mtorg-nav
                              • logo sizing
                              • navigation layout
                              • navigation hover/focus state
                              • MTO sand/green presentation

                              Theme checkpoint

                              Before migration:

                              8a5279b079aad34257b3ae96aaa273e88259dce3fcc27f42b88c4d2be1931b56
                              

                              After migration:

                              f516664233cdf3be1a839d43195508fd855fd2b59b3afa846eace9df08851b02
                              

                              Rollback

                              Created inside the theme:

                              theme.scss.before-header-css-migration-20260825
                              

                              Original checksum:

                              8a5279b079aad34257b3ae96aaa273e88259dce3fcc27f42b88c4d2be1931b56
                              

                              Build

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

                              Original:

                              704 lines
                              15930 bytes
                              b23b51e4b694eae95fbce8477f69f13f416451033cab2b9d476fdb964726f705
                              

                              Removed the legacy:

                              #mtorg-header
                              .mtorg-logo
                              .mtorg-nav
                              

                              rules, including responsive rules.

                              Validated result:

                              629 lines
                              14182 bytes
                              

                              Confirmed:

                              Header selectors remaining: 0
                              

                              Applied to Redis config customCSS.

                              Live post-removal:

                              627 lines
                              14180 bytes
                              8638ac923e1b18683683ffb2fec9f56bee38ae4d4157f7d7897a8a7a87d83d02
                              

                              Confirmed:

                              NONE — clean
                              

                              for the former header selectors.

                              Build successful.

                              Restart successful.


                              4. Cards / sidebars migration — completed

                              Audited existing theme implementation.

                              Theme already owned:

                              .card
                              .card-header
                              .card-body
                              

                              and 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 / sidebars
                              

                              Removed:

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

                              Validation:

                              627 → 595 lines
                              14180 → 13358 bytes
                              

                              Validated SHA:

                              8aa5b25a239ebe7980ab2c6857f90f14172faffa3dcb1f027b1d0fbb1f692fe6
                              

                              Applied to Redis.

                              Live result:

                              595 lines
                              13358 bytes
                              8aa5b25a239ebe7980ab2c6857f90f14172faffa3dcb1f027b1d0fbb1f692fe6
                              

                              Legacy selectors:

                              NONE — clean
                              

                              Build 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 .unread
                              

                              Theme already had equivalent category/topic ownership using:

                              [component="category"]
                              [component="category/list"]
                              [component="topic"]
                              [component="category/topic"]
                              .category-header
                              

                              Removed the legacy category/topic block.

                              Preserved intentionally for a later pass:

                              .badge
                              .pagination
                              .page-item .page-link
                              

                              Validation:

                              627 → 568 lines
                              14180 → 12877 bytes
                              

                              Validated proposed checksum:

                              c9ff7d622374ad42ce286517abacc22d2be6d2308d56f20d4da1ee1ed48d0814
                              

                              Applied to Redis.

                              Live result:

                              568 lines
                              12877 bytes
                              c9ff7d622374ad42ce286517abacc22d2be6d2308d56f20d4da1ee1ed48d0814
                              

                              Former selectors:

                              NONE — clean
                              

                              Preserved rules verified:

                              .badge
                              .pagination
                              .page-item .page-link
                              

                              Build 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-reply
                              

                              Compared 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-actions
                              

                              and associated responsive/dark-mode rules.

                              Therefore the older ACP block was determined to be obsolete.

                              Validation

                              Removed only:

                              Existing bottom topic bar
                              

                              block.

                              Validation:

                              568 → 530 lines
                              12877 → 11979 bytes
                              

                              Validated checksum:

                              f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9de
                              

                              Applied to Redis.

                              Live result:

                              530 lines
                              11979 bytes
                              f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9de
                              

                              Former selectors:

                              NONE — clean
                              

                              7. Final build/restart — successful

                              After the bottom-topic-bar migration:

                              ./nodebb build
                              

                              completed successfully:

                              Asset compilation successful. Completed in 6.625sec.
                              

                              Then:

                              docker restart app-nodebb-1
                              

                              successful.

                              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 days
                              

                              app-nodebb-1 came 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:

                              f516664233cdf3be1a839d43195508fd855fd2b59b3afa846eace9df08851b02
                              

                              Theme:

                              /usr/src/app/nodebb-theme-mto/theme.scss
                              

                              11. Current ACP CSS state

                              The last validated/live ACP CSS is:

                              530 lines
                              11979 bytes
                              f63b8e5ef859eaf1937bd21f00770882754e3271be97a3d26f86d3e5ea0fd9de
                              

                              The 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
                              Utilities
                              

                              The remaining ACP file was:

                              530 lines
                              11979 bytes
                              

                              after 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 sizing
                              

                              The theme already contains some .mto-smiley-bar and 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.txt
                              

                              Theme 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


                              1 Reply Last reply
                              0
                              • Grant LamontagneG
                                Grant LamontagneG
                                Grant Lamontagne
                                administrators
                                wrote on last edited by
                                #36

                                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-mto

                                Objective

                                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

                                1. Dead quick-smiley CSS removed

                                Audited all MTO references to:

                                smiley
                                emoji
                                quick-smiley
                                .mto-smiley
                                .mto-smiley-bar

                                Found 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 restored

                                Compared 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 ./index

                                Final 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 consolidated

                                Audited the entire .mto-bottom-topic-bar region.

                                The same selector had been declared in multiple separate blocks:

                                primary layout block
                                overflow block
                                dropdown stacking block

                                Consolidated:

                                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 retained

                                Installed validated checksum:

                                f55381de942ae0f44de26c01b048746311e4b9cc720cf7921e46e37cf3de5b43

                                Browser verification subsequently confirmed:

                                desktop good
                                mobile good
                                4. Bottom-bar comments cleaned

                                Removed 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 preserved

                                Proposed checksum after comment cleanup:

                                b15ac234f403030bfa7b6180372dabce71f8289dd32dbd3c48399d15b7d8e31b

                                This was then the live theme state before the next cleanup.

                                1. 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 separator

                                Installed checksum:

                                b93e8454f8b3cd19335976c3a4d7fc593072bababc29a2189ee65da0e538edee
                                Final theme architecture confirmed

                                MTO 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.json

                                CSS 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 confirmed

                                MTO 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 checkpoints

                                As of the end of today's work:

                                theme.scss
                                b93e8454f8b3cd19335976c3a4d7fc593072bababc29a2189ee65da0e538edee

                                templates/partials/topic/post.tpl
                                7f33bc6aaaf0abc33cbf096f0eb781d99488443dd60194796f6092fe0706d4e8

                                static/lib/mto-topic-actions.js
                                325fdf96f42edcf1acf3c9d38711c4706f3a2e457c47c1319a7e0980d994fe97

                                templates/partials/header/brand.tpl
                                7bef5ae6134cfffd35e3f24832c676ff694198b1e0a78607aa4833b7eef98acf

                                templates/topic.tpl
                                290e54181bfc95c58a020874fe512901af2d1474c5a8b0e00f17d414f476ba5d

                                NodeBB: 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
                                customHTML

                                Read-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 customization

                                Before 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
                                Important

                                Do 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: ✅ Preserved

                                Best stopping point: leave the current live theme untouched and resume with the Redis-backed ACP settings audit.


                                1 Reply Last reply
                                0
                                • Grant LamontagneG
                                  Grant LamontagneG
                                  Grant Lamontagne
                                  administrators
                                  wrote on last edited by
                                  #37

                                  31-08-2026 Daily Log

                                  MultiTool.Org NodeBB Theme — Daily Log / Handoff

                                  Date: 2026-08-31
                                  Session: End of day
                                  Current status: 🟢 Good stopping point

                                  1. 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.scss line ~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-compose section 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.tpl contains 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.tpl
                                  

                                  Despite the topic directory 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.scss contains 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-1
                                  

                                  It 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.js
                                  

                                  So 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.scss
                                  

                                  The 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-20260824
                                  

                                  The 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:

                                  1. Make one known-good current checkpoint/archive.
                                  2. Delete the obsolete individual .before-*, .working, .corrupt-backup, etc. files.
                                  3. Keep the actual live files clean.
                                  4. 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.scss yet

                                  theme.scss is 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.tpl

                                  Even 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.js merely because old copies exist

                                  The current JS file is the live one:

                                  static/lib/mto-topic-actions.js
                                  

                                  The audit records its checksum as:

                                  325fdf96f42edcf1acf3c9d38711c4706f3a2e457c47c1319a7e0980d994fe97
                                  

                                  The 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 problem

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


                                  1 Reply Last reply
                                  0
                                  • Grant LamontagneG
                                    Grant LamontagneG
                                    Grant Lamontagne
                                    administrators
                                    wrote on last edited by
                                    #38

                                    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


                                    1 Reply Last reply
                                    0
                                    • Grant LamontagneG
                                      Grant LamontagneG
                                      Grant Lamontagne
                                      administrators
                                      wrote on last edited by
                                      #39

                                      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

                                      1. 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
                                      Problem

                                      NodeBB 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"]
                                      Solution

                                      The 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;
                                      }
                                      

                                      }
                                      Result

                                      Visually 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
                                      Problem

                                      Posts 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.
                                      Investigation

                                      The actual NodeBB element was identified as:

                                      <a component="post/reply-count" ...>

                                      rather than the initially guessed:

                                      [component="post/summary"]
                                      Working CSS

                                      Temporary browser test confirmed this exact selector works:

                                      body.template-topic [component="post/reply-count"] {
                                      display: none !important;
                                      }
                                      Permanent version

                                      This 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;
                                      }
                                      Important

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

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

                                      1. Git state

                                      At the quote checkpoint:

                                      M theme.scss
                                      ?? theme.scss.backup-quote-20260901-184928

                                      The 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.scss

                                      Do not assume the working tree is clean.

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

                                      1. 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 sessions

                                      These 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% sidebar

                                      rather 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
                                      Print

                                      should remain functional.

                                      Do not replace native behavior unnecessarily.

                                      1. 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-container

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

                                      1. 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.tpl

                                      or the appropriate Harmony child-theme template override.

                                      1. 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 density

                                      Move 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 layout

                                      Continue refining:

                                      author column;
                                      post body width;
                                      post spacing;
                                      action bars;
                                      post separators;
                                      signatures.
                                      Priority 4 — Sidebar

                                      Eventually add:

                                      Community Links;
                                      Sponsors box;
                                      banner/ad space;
                                      appropriate responsive behavior.
                                      Priority 5 — Header/footer

                                      Further SMF-inspired polish:

                                      compact navigation;
                                      social icons;
                                      footer structure;
                                      banner/ad slot.
                                      Priority 6 — Composer

                                      Treat 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 philosophy

                                      Do 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 point

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


                                      1 Reply Last reply
                                      0
                                      • Grant LamontagneG
                                        Grant LamontagneG
                                        Grant Lamontagne
                                        administrators
                                        wrote on last edited by
                                        #40

                                        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

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

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

                                        1. Category header tightened

                                        Reduced the category header spacing/padding.

                                        Status: ✅ Done.

                                        1. 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 footnote

                                        We 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-115803

                                        The 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 spacing

                                        This 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 underneath

                                        We 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 posts

                                        Status: ✅ 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 50

                                        You 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 20

                                        You 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 index

                                        We 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 order

                                        That 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 summaries

                                        So 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 information

                                        So the originating page context is currently being lost when Reply is clicked.

                                        That's probably the first piece we need to solve.

                                        🔎 NEXT TECHNICAL STEP

                                        We 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.
                                        
                                        &#128994; 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.
                                        
                                        &#128994; 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.
                                        
                                        &#129529; 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.
                                        
                                        &#128204; CURRENT STATE — ONE GLANCE
                                        Visual work
                                        
                                        &#128994; Good
                                        
                                        Desktop topic width
                                        
                                        &#128994; 85/15
                                        
                                        Mobile topic width
                                        
                                        &#128994; Fine
                                        
                                        Pagination
                                        
                                        &#128994; 20/page
                                        
                                        Infinite scroll
                                        
                                        &#128308; Not wanted
                                        
                                        Mobile blue navigator
                                        
                                        &#128308; Gone
                                        
                                        Composer Submit
                                        
                                        &#128994; Bottom
                                        
                                        Quotes
                                        
                                        &#128994; SMF-ish
                                        
                                        Author panel
                                        
                                        &#128994; SMF-ish
                                        
                                        Post action menus
                                        
                                        &#128994; Fixed
                                        
                                        Reply-page history
                                        
                                        &#128993; Next thing we're working on
                                        
                                        SMF BBCode compatibility
                                        
                                        &#128993; Investigated, intentionally postponed
                                        
                                        SMF import
                                        
                                        &#128308; Not happening yet / treat archive as read-only
                                        
                                        .org cutover
                                        
                                        &#128308; Later
                                        
                                        Def
                                        
                                        


                                        1 Reply Last reply
                                        0
                                        • Grant LamontagneG
                                          Grant LamontagneG
                                          Grant Lamontagne
                                          administrators
                                          wrote on last edited by
                                          #41

                                          MTO NodeBB Daily Log — 2026-09-08
                                          Completed / Significant Work

                                          Topic 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 mapping

                                          Reason: 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 State

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


                                          1 Reply Last reply
                                          0

                                          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

                                          • Login

                                          • Don't have an account? Register

                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Popular
                                          • World