Skip to content

Where are widgets stored?

Solved Configure
3 2 992 1
  • Im away from home and only have access to mobile devices, and none of those allow me to create a widget. Can’t drag the html element into the (say) header section. Thats not working in mobile or ‘Desktop mode’ mobile, as the touch screen wont grab the item like a mouse click does.
    I was curious if I can create this widget directly as can SSH into my nodebb file system. So question:
    Is Widget code stored in the MongoDB database, or is it just a file in the NodeBB file system?
    In principle can I create a file that would then be picked up as a Widget. I guess if it is stored as a file, somewhere it must say what category and position on screen it applies to.

  • Im away from home and only have access to mobile devices, and none of those allow me to create a widget. Can’t drag the html element into the (say) header section. Thats not working in mobile or ‘Desktop mode’ mobile, as the touch screen wont grab the item like a mouse click does.
    I was curious if I can create this widget directly as can SSH into my nodebb file system. So question:
    Is Widget code stored in the MongoDB database, or is it just a file in the NodeBB file system?
    In principle can I create a file that would then be picked up as a Widget. I guess if it is stored as a file, somewhere it must say what category and position on screen it applies to.

    @Panda widgets are stored in the Mongo database. I can set the widget up for you if you PM me site details etc.

  • @Panda widgets are stored in the Mongo database. I can set the widget up for you if you PM me site details etc.

    @phenomlab Thanks, have DMed you

  • Pandaundefined Panda has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Custom Page - nodebb

    Solved Customisation custom-pages nodebb
    13
    2
    5 Votes
    13 Posts
    1k Views
    I’m happy to see this
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    2k Views
    @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.
  • Opening links in nodebb widget

    Solved Configure nodebb
    6
    4 Votes
    6 Posts
    2k Views
    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe> This works first time every time on your site as intended.
  • 1 Votes
    1 Posts
    692 Views
    No one has replied
  • Smart Widgets

    Solved Configure nodebb
    9
    3 Votes
    9 Posts
    2k Views
    @Panda said in Smart Widgets: So why is that, or conversely why would the function to expose username ever be required, as it seems app.user is already an available global object? It is, yes, but not if you are using it outside of a widget. The function I wrote is also historical and comes from the 2.x train
  • optional "snow falling" theme

    Solved Customisation nodebb
    6
    6 Votes
    6 Posts
    2k Views
    @Sala ok, but that’s still the same loop which is going to have an impact on the CPU.
  • ineffecient use of space on mobile

    Solved Customisation nodebb
    10
    2
    7 Votes
    10 Posts
    2k Views
    @phenomlab Thanks
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    10k Views
    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.