Skip to content

Bug Report

Solved Bugs
47 3 11.6k 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
  • 4 Votes
    3 Posts
    385 Views
    thanks @DownPW ! this is definitely very helpful.
  • Nodebb vs Wordpress vs Other

    General wordpress nodebb woocomerce business
    4
    2 Votes
    4 Posts
    592 Views
    PrestaShop + modules IA https://www.prestashop.com Magento https://developer.adobe.com/open/magento
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    2k Views
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • navigation menu panel on mobile

    Solved Customisation nodebb css
    8
    1
    7 Votes
    8 Posts
    2k Views
    @crazycells hmm. That’s odd. I haven’t made any changes from recollection but I could be wrong. I’ll need to check. EDIT - very strange. I honestly don’t recall adding the below CSS block to alter the bottom bar, but you’re right… .bottombar-nav { padding: 0px !important; } I’ve removed this so it reflects stock Harmony.
  • Composer Zen icon?

    Solved Configure nodebb
    8
    1
    2 Votes
    8 Posts
    1k Views
    @DownPW exactly. Not really a new concept, and in all honesty, not something I’ve ever used. If you consider the need to add links and references, or citations, you’d need to be able to see other parts of the screen!
  • 36 Votes
    55 Posts
    15k Views
    @DownPW I see why. The code relies on the existence of [component="topic/quickreply/container"] However, this by definition means that the below has to be enabled [image: 1679077966615-aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png] It will then work [image: 1679077992245-7fb38631-e0f3-46ef-b652-00929d927b13-image.png] For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component. The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on
  • Fresher in Nodebb install

    General nodebb
    24
    15 Votes
    24 Posts
    7k Views
    @Hari I’ve been reading a lot about APO. Looks impressive.
  • [NODEBB] Reply Button/arrow answer

    Solved Customisation css nodebb
    25
    4
    4 Votes
    25 Posts
    8k Views
    Topic open https://sudonix.com/topic/207/nodebb-help-for-my-custom-css