NodeBB 0.9.0 Has Dropped
-
Videos are still borked in 0.9.0
-
@scottalanmiller said:
While I don't mind the landing page being the recent postings list, but Mango icon should take us to the list of groups. The lack of that shortcut seems more like a hindrance than not. I wasn't expecting the Mango shortcut to change when I voted to change the landing page.
-
@Dashrender said:
@scottalanmiller said:
While I don't mind the landing page being the recent postings list, but Mango icon should take us to the list of groups. The lack of that shortcut seems more like a hindrance than not. I wasn't expecting the Mango shortcut to change when I voted to change the landing page.
It didn't, it's always been a link to the landing page. It would be really weird if the home page and the link to the home page went different places.
-
Did you check the categories button to see where that goes?
-
@scottalanmiller said:
Did you check the categories button to see where that goes?
I just read about it.. so that solves my concern.
-
It is going to break some stuff but things are slow and our platform has been updated. We are making the leap up to NodeBB 0.9.0. Hold on, here we go.
-
nice new reply notification..
-
but wtf is this... it appears on the right top corner of a new post/reply then fades out
-
That, from what we could tell (and how the heck did you manage to get a screen cap of it!!) it is an "unread post" indicator so that you can tell which posts ML thinks that you have or have not seen.
-
@scottalanmiller said:
That, from what we could tell (and how the heck did you manage to get a screen cap of it!!) it is an "unread post" indicator so that you can tell which posts ML thinks that you have or have not seen.
greenshot ftw.. it "pauses" your screen when you hit the button.
-
@JaredBusch said:
@scottalanmiller said:
That, from what we could tell (and how the heck did you manage to get a screen cap of it!!) it is an "unread post" indicator so that you can tell which posts ML thinks that you have or have not seen.
greenshot ftw.. it "pauses" your screen when you hit the button.
Mine doesn't. Often takes up to 30 seconds for it to react and if I do anything I'll end up off of the screen that I was on. Sometimes I forget about it and it pops up for me when I'm doing something completely different. So yours is really fast? Mine varies a lot, but is never exactly instant but probably two seconds when fast, thirty on average and has certainly had times where it was two to five minutes - enough that I was quite surprised when it popped up and had no idea why I had originally hit it.
-
@scottalanmiller said:
Mine doesn't. Often takes up to 30 seconds for it to react and if I do anything I'll end up off of the screen that I was on. Sometimes I forget about it and it pops up for me when I'm doing something completely different. So yours is really fast? Mine varies a lot, but is never exactly instant but probably two seconds when fast, thirty on average and has certainly had times where it was two to five minutes - enough that I was quite surprised when it popped up and had no idea why I had originally hit it.
What version are you on? I had issues like that a few versions ago.
Currently on this version
-
1.2.6 Build 12. I just installed it recently when we were discussing it. It was the latest at the time, I believe.
-
Updated now. 1.2.7 B2 now. So far it pops up instantly. I'll let you know if it turns slow again.
-
@sc
Still getting this. I do not on the nodeBB forum. so I assume it is a setting someplace that may need updated?
Also having an issue getting the names to pop correctly. Going to try and kill my browser in a minute.
I hit @ then s and I see this.
When I hit the c it goes away.
-
I assume that it is this plugin: https://github.com/psychobunny/nodebb-plugin-desktop-notifications
Without it, we don't get desktop notifications, though, which a lot of us rely on. Not sure how to balance that.
-
You could add the concern onto that plugin page directly or make a new thread here only for that issue and I'll link it over to their forum and the plugin's GitHub issue tracker.
-
@scottalanmiller said:
You could add the concern onto that plugin page directly or make a new thread here only for that issue and I'll link it over to their forum and the plugin's GitHub issue tracker.
Thanks for the link. Added an issue to the github for it.
-
Also tagging @psychobunny here so that he can see it.
-
@JaredBusch said:
Also having an issue getting the names to pop correctly. Going to try and kill my browser in a minute.
completely rebooted my machine and still having issues with name auto completion when I need to type one manually.
Edit:
@scottalanmillerIt seem to come and go. that one just worked.
