Skip to content

Bug in Nodebb route when clicking title

Moved Configure
3 2 1.0k 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
  • 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.
  • www. Infront stops website access?

    Solved Configure nodebb
    10
    1 Votes
    10 Posts
    2k Views
    @Panda because there is no match for the DNS entry specified. The receiving web server parses the headers looking for a destination hostname to match, and anything the web server is unable to resolve will be sent back to the root.
  • Further Widgets question

    Solved Configure nodebb
    4
    1
    1 Votes
    4 Posts
    1k Views
    @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.
  • NodeBB v3 Android Problem

    Solved Configure nodebb android
    4
    4 Votes
    4 Posts
    1k Views
    thank you fixed.
  • NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    5k Views
    @DownPW I still do not see any issues.
  • NodeBB: Favicon upload issue

    Solved Configure nodebb favicon
    12
    1
    3 Votes
    12 Posts
    3k Views
    @phenomlab I am on a Mac, so I used the “Option + Command + I”, and then performed the steps. It loaded my favicon! I checked on Firefox which I haven’t used before, and it showed my favicon also! That’s fantastic and thank you for the help!
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    11k 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.
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    3k Views
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.