Skip to content

Configure

262 Topics 4.6k Posts

Having issues with configuration ?

Subcategories


  • Looking to revamp your site layout?

    131 2k
    131 Topics
    2k Posts
    Hey everyone, I’m not sure where to post this, I’ll let @phenomlab edit it if necessary. Already posted here : https://community.nodebb.org/topic/19318/focus-mode-simply-immersive-reading-for-nodebb I’ve been working on a small client-side script that adds an simply immersive reading mode to NodeBB. No plugin required, just a few lines of custom JS and CSS dropped into the ACP. I’m just sharing this here for fun : https://github.com/DroidBV8/nodebb-focus-mode [image: input.gif] What it does Pressing F (or clicking the icon in the right sidebar) hides everything that isn’t the content you’re trying to read: Both sidebars Header / brand bar Footer Topic thumbnails and sidebar tools (reply, follow, timeline) The content area reflows to a centered 860px column, font size bumps up slightly, and a reading progress bar appears at the top of the page. To exit: press F again, Escape, or click the floating button that appears in the bottom-right corner. Details Activation effect : a subtle CRT glitch effect plays on toggle. Three CSS variables let you dial the intensity up or down without touching the keyframes: --fm-glitch-opacity: 1; /* 0.5 = subtle | 2 = heavy */ --fm-glitch-skew: 1deg; --fm-glitch-shift: 4px; Keyboard : F to toggle. Ctrl+F, Cmd+F and Alt+F are ignored so you don’t accidentally trigger it when searching the page. Scroll preservation : when toggling, the layout shifts because sidebars appear/disappear. The script measures the position of the nearest visible post before and after the layout change, then compensates with scrollBy so you stay exactly where you were. Topic-only : the button is greyed out on non-topic pages with a tooltip explaining why. Pressing F outside a topic shows a small toast instead of doing nothing silently. Mobile: disabled entirely under 768px. No button injected, no state restored. Theming : all colors reference Bootstrap CSS variables (--bs-body-bg, --bs-border-color, --bs-primary, etc.) so it adapts automatically to any NodeBB theme, light or dark. State : saved in localStorage, restored on next visit. Uses try/catch so it degrades gracefully in private browsing. Implementation notes The script is a self-contained IIFE, hooking into the standard NodeBB client-side events: $(window).on('action:ajaxify.end', function () { focusMode(); }); $(window).on('action:topic.loaded', function () { focusMode(); }); // etc. The glitch effect is pure CSS @keyframes , the JS only adds/removes classes. Layout compensation is synchronous (getBoundingClientRect → scrollBy) with no setTimeout on the scroll itself, which avoids triggering NodeBB’s scroll-based URL updater in a loop. Compatibility Tested on NodeBB 3.x with Bootstrap 5 themes. Should work on any setup using the standard sidebar components (nav.sidebar-left, nav.sidebar-right).
  • Problems with performance ?

    21 308
    21 Topics
    308 Posts
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Get help with network issues

    6 306
    6 Topics
    306 Posts
    @phenomlab Yes, I updated it right away after I created the password when first setting it up. Then I made my configurations.