Forums upgraded to NodeBB v1.9.0

[leocg]

leocg Moderator Volunteer @Guest last edited by

@joshl It's the page you see when you access the forums main address.

[sgunhouse]

sgunhouse Moderator Volunteer @amatczak last edited by

@amatczak Sorry, not showing here, First icon is Unread.

[amatczak]

amatczak Opera @sgunhouse last edited by

@sgunhouse desktop or mobile? I am on mobile now and indeed first icon is Unread.

[sgunhouse]

sgunhouse Moderator Volunteer @amatczak last edited by

@amatczak Desktop - well, a rather large laptop. 1600x900 though Opera is not fullscreen - call it 1400 wide.

[amatczak]

amatczak Opera last edited by

I think I may have an idea what's going on here...
Don't think that's related to screen size at all.
Can you check if you see it now?

[sgunhouse]

sgunhouse Moderator Volunteer last edited by

I was at work then, but I do see it now.

[amatczak]

amatczak Opera last edited by

OK, there was a bug introduced into NodeBB that we've released with the last upgrade.
Go to https://community.nodebb.org/topic/12323/widget-persists-and-does-not-respond-to-any-updates/6 if you're curious about the reason for this weird behaviour.

[A Former User]

A Former User last edited by

Yesterday, or perhaps the other day too, not sure, I had trouble connecting and posting here on the forums. Was there any trouble on the server end?
"Reply" didn't work a couple of times, pages kept loading for a while, and I dropped it. It seems that yesterday my comment came through, though I didn't see it appear at the time...

[leocg]

leocg Moderator Volunteer @Guest last edited by

@joshl Forums have been working fine here.

[A Former User]

A Former User last edited by

It seems to happen that the user list displays single member names twice:

While I was afraid at first glance that a unique member name could be assigned more than once during the registration process, I do think now that it is just a representation error in the user list, because both shown member profiles are linked to the same address.

I mention that because I don't know which event could trigger the occurence of that display bug.