Skip to content

Bug in Nodebb route when clicking title

Moved Configure
3 2 926 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
  • 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; }
  • 2 Votes
    6 Posts
    1k Views
    @dave1904 I’d start by adding a console.log function to hookData so you can see what is being returned return hookData; console.log(hookData):
  • NodeBB: Creating pages

    Solved Configure nodebb create page
    9
    0 Votes
    9 Posts
    3k Views
    OK, I think I have figured out how to place a link in the footer which will click to a new page.
  • nodebb loading emojis

    Solved Configure nodebb emojis
    16
    1
    1 Votes
    16 Posts
    3k Views
    @DownPW sure. Let me have a look at this in more detail. I know nginx plus has extensive support for this, but it’s not impossible to get somewhere near acceptable with the standard version. You might be better off handling this at the Cloudflare level given that it sits in between the requesting client and your server.
  • restarting nodebb on boot

    Unsolved Configure nodebb
    3
    1 Votes
    3 Posts
    1k Views
    @eeeee said in restarting nodebb on boot: can I just run nodebb under nodemon for auto restarts? It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.
  • who is read NodeBB

    Customisation read post nodebb
    6
    0 Votes
    6 Posts
    2k Views
    @cagatay You should ask in the NodeBB forums. Perhaps reference this post https://discuss.flarum.org/d/23066-who-read
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    3k Views
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • 0 Votes
    9 Posts
    2k Views
    @downpw I’m inclined to agree with this. There isn’t much else you can do, and provided it works with no odd looking artefacts in other browsers, then ok. The :before and :after are pseudo classes and very well supported across all browsers (except perhaps Internet Exploder, but who uses that these days ?)