Skip to content

Further Widgets question

Solved Configure
4 2 1.3k 1
  • Continuing my Widgets struggle here as although I asked about it on NodeBB forum, I still have remaining areas of confusion.
    I dont find the menu intuitive. In particular now Ive understood that the global .tpl will apply everywhere, are these Category / Topic settings irrelevant?
    20230526_163355~2.jpg

    Excuse the blurry photo, but what is the point of that
    Category 0
    Topic 0
    If its going to apply globally anyway?

  • Continuing my Widgets struggle here as although I asked about it on NodeBB forum, I still have remaining areas of confusion.
    I dont find the menu intuitive. In particular now Ive understood that the global .tpl will apply everywhere, are these Category / Topic settings irrelevant?
    20230526_163355~2.jpg

    Excuse the blurry photo, but what is the point of that
    Category 0
    Topic 0
    If its going to apply globally anyway?

    @Panda is there any reason not to include a screenshot rather than a photo of the screen? It’s a bit hard to decipher a blurry image 🙂

  • Apologies, was having technical difficulties with laptop with no PrtSrn button!
    widget.png

    Update
    There are tpl files for category and categories
    It seems this field works under category.tpl and not categories.tpl

    Im confused what the categories.tpl is for, but the category.tpl is working now, so problem solved

  • Pandaundefined Panda has marked this topic as solved on
  • Apologies, was having technical difficulties with laptop with no PrtSrn button!
    widget.png

    Update
    There are tpl files for category and categories
    It seems this field works under category.tpl and not categories.tpl

    Im confused what the categories.tpl is for, but the category.tpl is working now, so problem solved

    @Panda category is for a category in its own, so for example, “fruit” whereas categories is the page that contains all categories as a list.


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
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Where are widgets stored?

    Solved Configure nodebb
    3
    1 Votes
    3 Posts
    1k Views
    @phenomlab Thanks, have DMed you
  • 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
  • 4 Votes
    8 Posts
    2k Views
    @Panda said in Upgrade to NodeBB v3? 2BB or not 2BB, that is the question!: So although thats a plugin it has Widget like element and stopped working on the Theme change Which is normal based on the widgets being reset when you change themes.
  • NodeBB v3

    Announcements nodebb v3 nodebb
    2
    3 Votes
    2 Posts
    1k Views
    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    12k Views
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 1645128773854-47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • [NodeBB] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    4k Views
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.
  • NodeBB - Created pages not found?

    General
    20
    3 Votes
    20 Posts
    5k Views
    @jac Exactly. Hard point to argue.