@oplik0 said in snowing theme:

<script src="https://cdn.jsdelivr.net/gh/nextapps-de/snowflake@master/snowflake.min.js"></script>

try it in combination with nodebb-plugin-night-mode!  it becomes a heartwarming winter dream.

hi.

i'm pretty new to nodeBB - it's my first thread/post.  we are a group of seven enthusiasts who moved a nearly 20 year old voluntary sports-forum in germany from a proprietary internet forum software to nodeBB.  first of all: we are really happy with our choice =;^)  it's a great piece of software!

but there are some wishes.  of course.  after some investigation on the topic "counts for /flags and /post-queue" i felt asking here should be the best option.

we are using the /post-queue as a part of our spam-protection strategy.  our /post-queue is in the navigation visible to moderators and admins.  it would be great to have the count of posts inside as a marker on it like for /unread.  the same for /flags.  we would love to see the open issues marked there.

well.  if you have any advice because we missed something obvious feel free to help.  thank you.

ober!schöne grüße,
mrx.

@psychobunny said in Question and Answer plugin:

@murcs ah okay. Could you add a new issue here: https://github.com/NodeBB/nodebb-plugin-question-and-answer/issues

If you have client side errors / server side logs to paste there + info regarding your NodeBB setup (version, theme, etc.) then that would make it a lot easier to reproduce and fix. Thanks!

the easiest would be to reproduce it here.  just edit my first post!

@pitaj it worked.

someone wanted to tag a topic with 2021/22 but it was shown as 202122.  we tried single and double quotes as well as a \ to escape a / (aka. slash) but all we got from 2021\/22 was 2021\22 - which is far more than 202122.  any ideas?

@julian /admin/extend/plugins#trending shows v0.8.7 as the newest version of nodebb-plugin-question-and-answer plus a green update button aside which is a bit confusing.  /admin/extend/plugins#upgrade doesn't show anything.

"ahem"

running nodeBB v1.16.2 we are not able to load the current nodebb-plugin-question-and-answer v0.8.7 - we need a newer version of nodeBB first.  did we miss a major upgrade of nodeBB???  =;^)

@psychobunny said in Question and Answer plugin:

@murcs ah okay. Could you add a new issue here: https://github.com/NodeBB/nodebb-plugin-question-and-answer/issues

If you have client side errors / server side logs to paste there + info regarding your NodeBB setup (version, theme, etc.) then that would make it a lot easier to reproduce and fix. Thanks!

the easiest would be to reproduce it here.  just edit my first post!

@psychobunny said in Question and Answer plugin:

On your note though, it should work as expected after refreshing the page after you edit at the very least?

no.  it doesn't.  even after a refresh.

@pitaj it worked.

@pitaj mongoDB.  but if they are just moved, it's okay.  you are right.  thank you.

@pitaj you are right.  but resetting ALL widgets would mean i had to recap all (20?) other widgets.  okay.  no way to manipulate the DB from command line?

@psychobunny if one edits the first post of a topic "ask a question" becomes deactivated in "topic tools".  i would call it a kind of unexpected behaviour.

hi.

i added a HTML-widget to the global header section under /admin/extend/widgets with the following code

<script>var images = [
  "/assets/uploads/system/header_0.png",
  "/assets/uploads/system/header_1.png",
  "/assets/uploads/system/header_2.png"
]; function getImageTag() { var randomIndex = Math.floor(Math.random() * images.length); var img = '<img src=\"' + images[randomIndex] + '\" alt=\"headerimage\" width=\"100\%\"/>'; return img; }</script><div style="padding-bottom:30px"><script>document.write(getImageTag());</script></div>

which gave me the expected result: three randomly shown header images.  great!  but then i had to realize that the header image kind of overwrites the login.  in some browsers one can snatch the input form before its suddenly replaced by one of the three header images.

is it a feature or a bug?  decide yourselves.  but it doesn't matter.  what i need for the moment is just quick help to fix the problem!

as far as i know the HTML-widget should be found somewhere in the DB under the widgets:global keyword.  it would be great if one of you - with more experience in manipulating or changing an existing line of a DB entry - could help me with some script-code i could use from command line.  i'm still not confident in writing a small script which replaces the line which starts with "header": inside the widgets:global keyword to

"header": "[]"

which should just empty the global header section under /admin/extend/widgets and prevent the login form to be hidden by accident.  thank you.

ober!schöne grüße,
mrx.