I understand that chat notification occur when the target user is not directly focused on the chat itself. I further understand that the notification will also be delayed by about a minute just in case more messages come in.
However, in the latest version, it seems that when chat is sent, the target user will not get notified within 1 minute (pending the above). Actually, action:notification.pushed is triggered after few minutes, if at all.
Anything I am doing wrong?
@PitaJ What kind of reverse proxy configuration issue may it be? I've tried to change some nginx configuration lines, but withou result.
Oh I forget, I have used certbot to install SSL for my NodeBB forum, it changes some configuration in the nginx file. I do it according to this: https://medium.com/@hariomvashisth/free-https-within-5-minutes-5b67479849fa
I notice that on the mobile safari browser, after click the 'go' button, the url seems to stop for 1 or 2 times, maybe caused by http/https transformation. But not very clear, any idea? Thanks!
solution - i hadn't removed my custom theme properly. you need to reset to the default theme, remove the link, and use npm rm to completely remove your theme so it doesn't check for it.
i'm not sure why my calendar plugin broke as well, or why the bootswatch theme i was using as a base has stopped working either. but the build itself is working.
There's some mention of this previously (at the bottom of: Re: Make uploaded files private...?.
Basically is there any way to make uploaded files only accessible to members of a specific group? At the moment any registered user can access any uploaded file if they have the correct link.
Using: NodeBB v1.11.0.
Thank you very much for your continued support and for the ever evolving NodeBB forum.
Warmest thoughts and best wishes for a wonderful holiday and a very happy new year. Wishing you the gifts of the season — Peace, Hope and Happiness.
My report isn't 100% correct.
When resizing the browser smaller, the top bar does become 2x taller, but the title and breadcrumb are rendered beneath properly.
So it's only a normal (not full screen) kind of browser window with a long site title that exhibits the problem.