NodeBB 1.2 Released
-
@BRRABill said in NodeBB 1.2 Released:
@travisdh1 said
Sorry for the horrible picture, found that the other day. Need to put a battery in it and get it back up on the wall.
Did you take that during a massive earthquake?
It's what happens when I take a picture without my glasses on. That looked "normal" on my phone when I took it. Didn't think to take my glasses into the laundry room.
-
Here we go....
-
And we are back!
-
That was fast, everything work okay?
-
Yup, you beat even me. I wasn't watching the script closely enough. It just "comes up" when it finishes because I script it. It's back up, no errors. Looks good thus far.
-
We are now on 1.2.0 and all plugins are fully updated.
-
I'm now getting this every few seconds
-
What browser? Have you restarted the browser?
-
@scottalanmiller said in NodeBB 1.2 Released:
What browser? Have you restarted the browser?
Come on now.. really, you want me to kill my 30+ tabs?
FF - fine.. I'll restart
-
The private chat windows on mobile are huge!
-
My chat rooms are weird and yes, I restarted my browser. And am also getting those sound missing alerts.
-
I get this new error in mobile chats. Logged out of mobile, restarted browser.
-
@BBigford said in NodeBB 1.2 Released:
I get this new error in mobile chats. Logged out of mobile, restarted browser.
I do get the same error outside of mobile (Chromebook).
-
I also get the error @Dashrender mentioned. Computer died so I switched computers, same result.
-
The mango favicon on the tabs is gone.
-
Yes, that's the chat issue I am seeing.
Chat rooms, and some recent chat content seems to be missing.
And it is throwing up that sound error.
-
I feel like threads load much faster now. When I click to open a link, it is nearly instantaneous.
-
@nadnerB said in NodeBB 1.2 Released:
The mango favicon on the tabs is gone.
Yeah back to the nodebb default.
-
I am getting the sound error pop up even though I have sounds disabled.
I did select each sound and click play. they do work.
-
@JaredBusch notice those are mp3 files but the error is a wav. Try reloading the browser, maybe that will help? Or maybe I need to restart the server? I remove the .wav files that were in a different folder.
