Skip to content

Bug Report

Solved Bugs
47 3 19.8k 1
  • wrote on last edited by
    #17

    hi @phenomlab , this notification problem continues for me… I believe those “user_posted_to” should be changed to “user-posted-to” in the codes…

    Screenshot 2024-03-15 at 11.20.15.png

  • wrote on last edited by
    #18

    do you use “nodebb-plugin-category-notifications” plugin?

  • wrote on last edited by
    #19

    Additionally, it looks like I am not watching this topic, but I get notification… strange… Does category-notification plugin cause this?

    Screenshot 2024-03-15 at 11.33.26.png

  • do you use “nodebb-plugin-category-notifications” plugin?

    wrote on last edited by
    #20

    @crazycells said in Bug Report:

    do you use “nodebb-plugin-category-notifications” plugin?

    Yes, but am going to remove it. I think that’s the case because it’s out of date.

  • Additionally, it looks like I am not watching this topic, but I get notification… strange… Does category-notification plugin cause this?

    Screenshot 2024-03-15 at 11.33.26.png

    wrote on last edited by
    #21

    @crazycells It might do. Sudonix does not impose anything on it’s users - they have complete control over notifications and emails they receive. I’ve just disabled the plugin. Let me know if it continues.

  • @crazycells It might do. Sudonix does not impose anything on it’s users - they have complete control over notifications and emails they receive. I’ve just disabled the plugin. Let me know if it continues.

    wrote on last edited by
    #22

    @phenomlab no need to worry 🙂 I am aware how sensitive you are about GDPR compliance… You are probably the one who is the most careful regarding GDPR within the NodeBB community. I was simply trying to understand the cause of this problem, receiving notifications from your forum at any time is perfectly fine with me 🙂

  • @phenomlab no need to worry 🙂 I am aware how sensitive you are about GDPR compliance… You are probably the one who is the most careful regarding GDPR within the NodeBB community. I was simply trying to understand the cause of this problem, receiving notifications from your forum at any time is perfectly fine with me 🙂

    wrote on last edited by
    #23

    @crazycells Thanks for the comments. Yes, I take privacy very seriously, and would much rather users of this site have control over their own content.

  • wrote on last edited by
    #24

    hi Mark,

    “go to top of the page arrow” on the lower right side is overlapping with the post navigation bar on mobile, fyi…

    IMG_0028.jpg

  • hi Mark,

    “go to top of the page arrow” on the lower right side is overlapping with the post navigation bar on mobile, fyi…

    IMG_0028.jpg

    wrote on last edited by
    #25

    @crazycells Fixed. Thanks

  • @crazycells Fixed. Thanks

    wrote on last edited by
    #26

    @phenomlab yeap, it is much better now 🙂 thanks…

  • @phenomlab yeap, it is much better now 🙂 thanks…

    wrote on last edited by
    #27

    @phenomlab the arrow stays up when I am not on a topic (so there is no post navigation tool)…

    IMG_0036.PNG

  • @phenomlab the arrow stays up when I am not on a topic (so there is no post navigation tool)…

    IMG_0036.PNG

    wrote on last edited by
    #28

    @crazycells that’s intended behaviour. If you press it, it’ll return to the top of the screen and then disappear.

  • @crazycells that’s intended behaviour. If you press it, it’ll return to the top of the screen and then disappear.

    wrote on last edited by
    #29

    @phenomlab yeah, but isn’t it too up? I thought ideal place would be right above the menu bar on those pages?

  • wrote on last edited by
    #30

    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

  • @phenomlab yeah, but isn’t it too up? I thought ideal place would be right above the menu bar on those pages?

    wrote on last edited by
    #31

    @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

    wrote on last edited by
    #32

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

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

    wrote on last edited by phenomlab
    #33
  • wrote on last edited by
    #34

    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

    wrote on last edited by
    #35

    @crazycells Can you reload your browser and try again?

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

    wrote on last edited by
    #36

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


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
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k Views
    phenomlab
    @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.
  • how to hide "moved" badge with CSS?

    Solved Customisation nodebb
    12
    1
    3 Votes
    12 Posts
    4k Views
    phenomlab
    @crazycells ah, I see. That makes sense.
  • Removing blue 'moved' tag from post

    Solved Configure nodebb
    16
    2
    3 Votes
    16 Posts
    5k Views
    Panda
    @phenomlab Ah, got it working! I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters. So made the new fork title longer and button responded.
  • NodeBB: Privileges for the Announcement channel

    Solved Configure nodebb
    6
    1
    1 Votes
    6 Posts
    2k Views
    phenomlab
    Up to you really
  • NodeBB v3

    Announcements nodebb v3 nodebb
    2
    3 Votes
    2 Posts
    1k Views
    phenomlab
    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.
  • Q&A Plugin Changes NodeBB

    Solved Customisation nodebb q&a plugin
    25
    1
    6 Votes
    25 Posts
    11k Views
    cagatay
    @phenomlab said in Q&A Plugin Changes NodeBB: float: right; left: 10px; } worked thank you
  • NodeBB Theme/Skin Switcher

    Solved Customisation nodebb
    38
    7 Votes
    38 Posts
    18k Views
    phenomlab
    @Teemberland great spot ! You should create a PR for that so they can include it in the official repository. Just be aware that any subsequent releases will overwrite your fix without the PR.
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    16k Views
    DownPW
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok