3.0.0 Bug Report Thread
-
@brazzerstop should be fixed in https://github.com/NodeBB/NodeBB/commit/00be053e948f0db210ba23527aa0ae594540418c, thanks for reporting.
-
next thing: if a
user
becomes flaged for the second (or more?) time, thenotification
shows the first and not the lastuser
who reported. ... and while we are at this topic: we would love to see thetarget
pointing to thepost
it came from with the last report and not to the flaggeduser
or both. [v3.2.3] -
Dear NodeBB Team,
I noticed that the Chats route doesn't display the top menu unlike the Notifications one in v3.2.1 and also v3.2.2.
This is easily replicable here too when navigating to:
https://community.nodebb.org/user/"insertyourusernamehere"/chats
This might be intended or should I create a Github issue?
Thanks in advance! -
@baris May I ask why this is so?
To me, it feels inconsistent with the other routes.
The issue I'm trying to solve is, without the "Home" which isn't a default route if I'm not mistaken, all the page elements, including the menus are moved up and the top ones rendered outside the viewport so it definitely looks broken.
Any pointer to circumvent this (custom css?) is highly appreciated, thanks! -
@erkki70 if you want to bring the header back you can use custom css.
.page-user-chats .brand-container { display: block; }
You will have to modify some of the css for the chat page though as it is designed to be height: 100% to take up all the available space. The
#content
element is height: 100% which will not play nice if you display the header element above it. -
@baris said in 3.0.0 Bug Report Thread:
@erkki70 if you want to bring the header back you can use custom css.
.page-user-chats .brand-container { display: block; }
You will have to modify some of the css for the chat page though as it is designed to be height: 100% to take up all the available space. The
#content
element is height: 100% which will not play nice if you display the header element above it.Thanks for your help!
-
-
This rules not work for guest users?
/admin/settings/post
I mean post delay. -
Blocking by IP address is ineffective in cases of a real attack.
If I want some user to be unable to log into the forum, I will simply block his account. The IP blacklist should block the ability to enter the forum and show a custom error page, instead, users with blocked IP addresses continue to attack the forum with requests.
-
@brazzerstop Thanks for reporting, created an issue to track https://github.com/NodeBB/NodeBB/issues/11868
-
I'm not sure if this can be attributed to the bug branch, but I think this result is a bit strange...
If we create a subcategory and set
0
incid-subcategories-per-page
in parent category (because I don't want display this subcategory, but I want to show posts in widget from this hidden subcategory), this subcategory is not displayed, but next I can't found this subcategory in dropdown menu with categories in ACP and category selector in Composer. -
-
Please add function to clear history of searches
/admin/dashboard/searches
-