Skip to content

Bug Report

Solved Bugs
47 3 16.3k 1
  • @phenomlab yeah, but isn’t it too up? I thought ideal place would be right above the menu bar on those pages?

    @crazycells Hmm, yes, I see what you mean, but that would require 2 sets of code. Worth thinking about though 🙂

  • additionally, do you think a similar button can be made for “go back one page” button? something I have mentioned here before?

    https://community.nodebb.org/topic/17931/page-control-arrows-for-pwa

    @crazycells Yes, easily. Wouldn’t be difficult at all.

  • @crazycells Yes, easily. Wouldn’t be difficult at all.

  • composer previews have problems… when I show the preview, it becomes transparent.

    Screenshot 2024-04-03 at 12.04.12.png
    Screenshot 2024-04-03 at 12.04.02.png

  • composer previews have problems… when I show the preview, it becomes transparent.

    Screenshot 2024-04-03 at 12.04.12.png
    Screenshot 2024-04-03 at 12.04.02.png

    @crazycells Can you reload your browser and try again?

  • @crazycells Can you reload your browser and try again?

    @phenomlab yeap, it is fixed… somehow I was on the wrong theme… what is the theme that was loaded first? cache issue?

  • @phenomlab yeap, it is fixed… somehow I was on the wrong theme… what is the theme that was loaded first? cache issue?

    @crazycells Yes - sorry. It’s because I’ve been changing the theme names so the old ones aren’t officially supported (as such - they have been renamed). If you are using light mode on your OS, then you’ll get the light theme (which you clearly have). Reloading forces the JS to reevaluate and select the right theme.

    Should have made an announcement about this. Sorry.

  • @crazycells Yes - sorry. It’s because I’ve been changing the theme names so the old ones aren’t officially supported (as such - they have been renamed). If you are using light mode on your OS, then you’ll get the light theme (which you clearly have). Reloading forces the JS to reevaluate and select the right theme.

    Should have made an announcement about this. Sorry.

    @phenomlab no problem at all 🙂 next time before reporting, I will refresh the page…

  • @crazycells Yes - sorry. It’s because I’ve been changing the theme names so the old ones aren’t officially supported (as such - they have been renamed). If you are using light mode on your OS, then you’ll get the light theme (which you clearly have). Reloading forces the JS to reevaluate and select the right theme.

    Should have made an announcement about this. Sorry.

    @phenomlab There is one thing I have to mention, yesterday I was checking sudonix as PWA (but my comment can be thought as related to general mobile design) and I realized that there is no easy way to go to /categories page… It is indirect through the category panel…

    If someone is accessing your website first time, I believe that is the page they would want to see to understand the general theme/aim of the forum… This is usually done either clicking the title or clicking the home icon…

    But for this website, they both direct you to the /recent page… I knew how to reach there since I use NodeBB daily but if I was outside user, I would struggle little bit 😄

    Of course, if everything is intentional, then there is no problem… I just wanted to bring this to your attention…

  • @phenomlab There is one thing I have to mention, yesterday I was checking sudonix as PWA (but my comment can be thought as related to general mobile design) and I realized that there is no easy way to go to /categories page… It is indirect through the category panel…

    If someone is accessing your website first time, I believe that is the page they would want to see to understand the general theme/aim of the forum… This is usually done either clicking the title or clicking the home icon…

    But for this website, they both direct you to the /recent page… I knew how to reach there since I use NodeBB daily but if I was outside user, I would struggle little bit 😄

    Of course, if everything is intentional, then there is no problem… I just wanted to bring this to your attention…

    @crazycells Good points. Thanks. I will review this.

  • @phenomlab There is one thing I have to mention, yesterday I was checking sudonix as PWA (but my comment can be thought as related to general mobile design) and I realized that there is no easy way to go to /categories page… It is indirect through the category panel…

    If someone is accessing your website first time, I believe that is the page they would want to see to understand the general theme/aim of the forum… This is usually done either clicking the title or clicking the home icon…

    But for this website, they both direct you to the /recent page… I knew how to reach there since I use NodeBB daily but if I was outside user, I would struggle little bit 😄

    Of course, if everything is intentional, then there is no problem… I just wanted to bring this to your attention…

    @crazycells hmm. Just looking at this and I do see what you mean but if you tap the category icon it should auto expand with the first option in the list being “All Categories” which will take you to /categories.

    In addition, it’s possible to change the default home page in your profile settings.

  • @crazycells hmm. Just looking at this and I do see what you mean but if you tap the category icon it should auto expand with the first option in the list being “All Categories” which will take you to /categories.

    In addition, it’s possible to change the default home page in your profile settings.

    @phenomlab yes I know, but that is “two clicks”… nowadays “two” is too much to get the main page 😄

    it is ok for me, I know how to navigate, but I was talking from a new user’s perspective (even unregistered one)… no need for any change if it is OK for you 🙂

  • @phenomlab yes I know, but that is “two clicks”… nowadays “two” is too much to get the main page 😄

    it is ok for me, I know how to navigate, but I was talking from a new user’s perspective (even unregistered one)… no need for any change if it is OK for you 🙂

    @crazycells yep. I get it! Good point.

  • @crazycells yep. I get it! Good point.

    Hi @phenomlab , upvote icon is better as a triangle, however I would love to see my upvoted posts more clearly, because currently, when I upvote, nothing on the post tool is changing, it would be nicer if there is an indication that I have upvoted (like a filled or colored triangle?) .

  • Hi @phenomlab , upvote icon is better as a triangle, however I would love to see my upvoted posts more clearly, because currently, when I upvote, nothing on the post tool is changing, it would be nicer if there is an indication that I have upvoted (like a filled or colored triangle?) .

    @crazycells hmm. Nice idea, but not that easy to implement unless there’s a hook that fires (not sure there is). Could be done with JS but that could be too the detriment of page loads and ajax calls.

  • @crazycells hmm. Nice idea, but not that easy to implement unless there’s a hook that fires (not sure there is). Could be done with JS but that could be too the detriment of page loads and ajax calls.

    @phenomlab I think in this case a custom CSS code suffice…

    we were using something like this:

    .topic [component="post/upvote"].upvoted {
        color: #085EAC;
    }
    
    .topic [component="post/upvote"].upvoted {
      border: 0px !important;
    }
    
    .topic [component="post/downvote"].downvoted {
            color: #EF4042;
    }
    
    .topic [component="post/downvote"].downvoted {
      border: 0px !important;
    }
    
    
  • @phenomlab I think in this case a custom CSS code suffice…

    we were using something like this:

    .topic [component="post/upvote"].upvoted {
        color: #085EAC;
    }
    
    .topic [component="post/upvote"].upvoted {
      border: 0px !important;
    }
    
    .topic [component="post/downvote"].downvoted {
            color: #EF4042;
    }
    
    .topic [component="post/downvote"].downvoted {
      border: 0px !important;
    }
    
    

    @crazycells Good points, thanks. I completely forgot that classes are added - makes life much simpler!

    EDIT - seems this is pretty straightforward, and only needs the below CSS

    .upvoted i {
        color: var(--bs-user-level) !important;
    }
    

    This then yields

    3f072f8a-ebfa-4910-8723-73c493b8e4eb-image.png

    However, the caveat here is that the .upvoted class will only show for your upvotes, and nobody else’s. However, this does satisfy the original request

    however I would love to see my upvoted posts more clearly, because currently, when I upvote, nothing on the post tool is changing, it would be nicer if there is an indication that I have upvoted (like a filled or colored triangle?)


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 html in nodebb to prevent cache

    Unsolved Configure nodebb
    18
    2 Votes
    18 Posts
    4k Views
    @Panda You’ll need to do that with js. With some quick CSS changes, it looks like this [image: 1690796279348-d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png] The colour choice is still really hard on the eye, but at least you can now read the text
  • 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.
  • SEO and Nodebb

    Performance nodebb seo
    2
    2 Votes
    2 Posts
    1k Views
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • 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 Android Problem

    Solved Configure nodebb android
    4
    4 Votes
    4 Posts
    2k Views
    thank you fixed.
  • 0 Votes
    5 Posts
    2k Views
    @qwinter this particular site uses the code I wrote if you want to see it in action. It’s a information and intelligence gatherer I designed for collecting various information security articles from around the globe and consolidating them in one place. Essentially, each “post” is in fact generated by the script, and the NodeBB API. https://hostrisk.com/
  • CSS codes for fa-info icon

    Solved Customisation nodebb
    9
    1
    6 Votes
    9 Posts
    3k Views
    I have just figured it out… it can be targeted with text-decoration-color: I was mistakenly using color
  • FIXED: Annoying cosmetic bug on mobile view

    Moved Bugs bugs
    13
    3 Votes
    13 Posts
    3k Views
    And now, after all this time I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block .tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; } And, add this below to make it more specific. .emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }