@Shaun Yeah, the master branch... might have been fixed already.

@pichalite Thanks ... I should probably learn to check those.

Fixed in https://github.com/NodeBB/NodeBB/commit/f6be4efe8bb881cb0cb5a1dfccb294dfb0950afe

I haven't logged in for a while, but when I did I found a notification waiting. But when I click on the notification area, it kind of flashes and says there are no notifications: [image: L8GdajW.png] It kind of seems like it's finding a notification for me and then possibly realizing it's old and removing it when I try to view it.

I just saw this issue on this forum. I was reading the persona preview thread, ignoring the box telling me to go where I left off. Then I quickly scrolled to the bottom. There were 5 reply buttons in a row with no posts between them. I am using the latest version of chrome.

Haha. I'm planning a refactor of the menu

@psychobunny no, I have not, but I suspect it may be plugin related or something screwy about this thread in the database. I have been distracted by a million other things and one misbehaving thread wasn't my priority, but I will look and see if I can figure something else out.

The hit area should be bigger now.

@julian Ah. I wasn't thinking about avatars.

Yeah, I don't understand. I think the modal-dialog doesn't have a z-index (which is why I had to change my workaround above to fix it). TBH, if it's fixed in 0.7.0, I'll be happy with just using my workaround until then. A few extra lines of CSS won't kill me.

I haven't tested but I'm pretty sure, given the experiences of others here, that the actual cause of my NodeBB breakage was dbsearch 0.0.16, so while it's awkward to be told there are all of these upgrades available, I don't think the problem was nbbpm, just a bad plugin.

The change should have been backported to 0.5.x, so you can just pull the latest commits from that branch to get v0.5.4

Heh ... you responded in the time it took me to update the value and restart my NodeBB. Nice.

By "dynamic" I mean any environment where these kinds of privileges may be changing frequently. It's not just about moderation, it's about their roles in general (reading and posting privileges). And I understand what an administrator is, but that's not a clean separation. Admin and moderator are roles (not specific, granular privileges) and in one case represented as a group and in another represented as a privilege. It's not that NodeBB doesn't suit my use case. After finding the moderator option, I can pretty much do what I want to do. It's about the spaghetti process it took to get there. I'd just like to see this be simplified and presented in a more coherent manner.

Thanks, @julian. I just finished the hardware migration of these VMs and I want to move them to a more stable hypervisor/host than my former Windows 7 desktop with VMWare workstation, so this is timely advice.

Thanks for another quick quality of life fix. It's appreciated!

Disabling reputation system only disables privileges tied to reputation like managing threads or content after you gain X reputation, it wasn't meant to disable the whole reputation system. Maybe it needs better wording in the ACP.

Haven't seen it happen since the pull.

@Shaun when 0.5.0 is released, their will be full documentation, but the process will be something along the lines of git checkout v0.5.x git pull ./nodebb upgrade But their will be an announcement about all of that and how to update when it's ready. If you have any other issues with plugins etc, feel free to create a topic.