Skip to content

Bug in Nodebb route when clicking title

Moved Configure
3 2 1.1k 1
  • This forum:
    https://aignite.nodebb.com/
    is on v3.2, awaiting upgrade to latest version …

    if you go into a category, then click the forum title
    On Mobile, it doesnt go back to home page, it refreshes and stays in the same category

    On desktop, if you click on the icon (flame image) it will go to the home category list as expected, but if you click on the word (Aignite) it trys to load something, then says page not found!

    Interestingly, Sudonix site doesn’t have this flaw. Not sure if its been fixed in v 3.2.1 or @phenomlab has set something up that I haven’t?

    In Admin the Home Page route is set to Categories, (default setting)

  • This forum:
    https://aignite.nodebb.com/
    is on v3.2, awaiting upgrade to latest version …

    if you go into a category, then click the forum title
    On Mobile, it doesnt go back to home page, it refreshes and stays in the same category

    On desktop, if you click on the icon (flame image) it will go to the home category list as expected, but if you click on the word (Aignite) it trys to load something, then says page not found!

    Interestingly, Sudonix site doesn’t have this flaw. Not sure if its been fixed in v 3.2.1 or @phenomlab has set something up that I haven’t?

    In Admin the Home Page route is set to Categories, (default setting)

    @Panda That looks to be because of this setting you have

    bd21bcbc-6e6f-4af2-a355-c8cdc5a3b28a-image.png

    Title Link URL cannot be freeform text - it needs to be a hyperlink. If you leave this blank, it will use the siteUrl

  • Ah silly me, thanks for finding that!

  • phenomlabundefined phenomlab moved this topic from Bugs on

Related Topics
  • Nodebb vs Wordpress vs Other

    General wordpress nodebb woocomerce business
    4
    4 Votes
    4 Posts
    1k Views
    PrestaShop + modules IA https://www.prestashop.com Magento https://developer.adobe.com/open/magento
  • 3 Votes
    1 Posts
    858 Views
    No one has replied
  • 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.
  • Difficult to move posts now, on mobile.

    Bugs nodebb
    16
    1
    5 Votes
    16 Posts
    4k Views
    @DownPW Yes, it is. It’s set far too low meaning other elements with a higher preference will sit over the top of it.
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    2k Views
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • NodeBB: Opening the Composer for replies

    Solved Configure cms composer
    2
    0 Votes
    2 Posts
    888 Views
    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below [image: 1681314389744-82ca1209-31be-4a51-a641-9887b5a238b8-image.png] Failing that, you’ll need to use the reply button in the sticky toolbar [image: 1681314442570-1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png]
  • NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    5k Views
    @DownPW I still do not see any issues.
  • NodeBB: Creating the Swatch modes

    Solved Configure swatch
    2
    0 Votes
    2 Posts
    873 Views
    @mventures the swatch feature you refer to isn’t a NodeBB plugin, but a utility that I wrote that handles this. It is available for v2 (as you can see here) but I’ve stopped developing and releasing the code because it has been entirely rewritten to work for v3. If you’d like the code, this is possible, but you’ll need to upgrade to v3 first.