Known issues with Qt Forum

SGaist

It seems that the "latest answer to a post" in the "unread" section is still wrong.

AndyS

Yeah that I am aware is the case, I am planning to schedule time this week to look at it. I need to understand the code to see why it might be wrong and see if its the server or something else tripping it.

Chris Kawa

@AndyS said in Known issues with Qt Forum:

Ok, I think this is fixed now. I have to wait until tomorrow to know for sure, but I am certain I got it right this time :)

The icon was back for me for few hours but now it's gone again?

Another thing - I know this was reported already but it started to happen to me too now so I though I'd mention it - the upvote counter does not show correct number for some posts. It's ok for others:
upvote

JKSH

@Chris-Kawa said in Known issues with Qt Forum:

the upvote counter does not show correct number for some posts. It's ok for others

This might be a cache issue. I've found that refreshing (or closing + reopening) the page can fix the counter.

JonB

For the record (Chrome): I'm no-favicon, and still with incorrect counters, despite any refreshes/re-opens, just as per the last few weeks. But not unappreciative of @AndyS efforts :)

AndyS

Ok, the fav-icon I can understand why it goes away, the problem is due to how our server works so the change I made doesn't get saved, therefore I need to do it a different way to make it stick. I'll try and sort that out today, though I am not sure why it stopped working initially because it has nothing to do with the upgrades.

koahnig

The number of posts in a thread are not always correct in the overview.

Quite often I am opening a thread showing only 1 post, but it may have already 1 or more answers. Sometimes those answers were a couple of hours old. However, it is not an update issue, because typically I am loading the list of unread threads each time.

When opening it showed

and 2 responses

koahnig

This one just showed up after I had cleared list

However, it is 8 hours old. When opening it had already a response which just added by SGaist

Chris Kawa

I have another kinda following the same theme - the number by the notifications bell icon does not go away but there's no new notifications inside. I thought maybe they are just not highlighted like they used to so I clicked through all of them one by one but the number stays. Curiously when opened in another browser the number is cleared, so I think it's some sort of yet another caching issue.
notifications bell
All those problems seem weirdly similar. Like something gets cached that shouldn't or something doesn't when it should. Maybe there's one root cause?

Chris Kawa

Also I just noticed that clicking on these notifications moves me to a random post way above the one actually mentioned in the notification. For example clicking on the first notification in the picture above should bring me to https://forum.qt.io/topic/106297/known-issues-with-qt-forum/35 (I think), but it actually goes to https://forum.qt.io/topic/106297/known-issues-with-qt-forum/22, which makes no sense since it's before my own post and there's more than 6 people below it so I'm not sure what it actually counts.

AndyS

I do believe all the problems are related to one cause but the problem is I haven't been able to figure out what that cause is yet. They do have similarities and I think it is more to how our server is than NodeBB itself, but I need to understand how NodeBB is doing it to figure out what might be wrong. It might be a DB problem too, but its hard to say when I can only really reproduce it on the main server and I don't want to tinker about that for obvious reasons :)

kshegunov

@Chris-Kawa said in Known issues with Qt Forum:

I have another kinda following the same theme - the number by the notifications bell icon does not go away but there's no new notifications inside.

I would bet this isn't upgrade related, because I've experienced it pre-upgrade. Rather rarely but it has happened. Clicking "Mark all read" removes the red indicator (obviously), but I have never been able to trigger it intentionally nor do I have any clue why it happens.

AndyS

After a bit of investigation, I think that the problem lies in the DB or potentially in the version of MongoDB being used, which might explain things. I have at least figured out where it gets this data from (at least I think I have) so I will continue to move forward with trying to see if the data compares as a result and work from that. I do want to get this fixed as it is very annoying :)

JonB

@AndyS
I suppose a whole bunch of must-have, new features we are getting from new forum updates is making this all worthwhile?? Because otherwise it was just fine as it was until a month or so ago... :)

AndyS

@JonB There are some features that I have noticed, but the main thing is down to security fixes too. We were so far behind that it was a risk in that respect and as a result it is better to be up to date to avoid anything known being exploited. Better to be safe than sorry after all :)

koahnig

@Chris-Kawa said in Known issues with Qt Forum:

I have another kinda following the same theme - the number by the notifications bell icon does not go away but there's no new notifications inside. I thought maybe they are just not highlighted like they used to so I clicked through all of them one by one but the number stays. Curiously when opened in another browser the number is cleared, so I think it's some sort of yet another caching issue.

All those problems seem weirdly similar. Like something gets cached that shouldn't or something doesn't when it should. Maybe there's one root cause?

This is possibly not introduced with update. I have seen in the past the number of notifications did not match the number of highlighten entries. Those entries have been highlightened with a new opening of box. Typically this occured when the number of notifications was "high" around 6 or more.
PS: Guess not everybody considers these as high numbers ;)

JonB

@AndyS said in Known issues with Qt Forum:

@JonB There are some features that I have noticed, but the main thing is down to security fixes too. We were so far behind that it was a risk in that respect and as a result it is better to be up to date to avoid anything known being exploited. Better to be safe than sorry after all :)

Here's a new one, which I thought I had noticed, but wasn't sure. You wrote @JonB in your reply, but I did not get any "Notification" of your post (I have checked the list of Notifications to make sure I did not miss). This seems to have happened a few times lately, whereas in the past I don't think it did.

Is this a new "feature", or is it to do with the way you posted the response and it has always been like that for the way you wrote it? :)

AndyS

@JonB It should have worked and it did come up before but that was supposedly resolved. So it seems that it has come back again but I also feel that this is all related to the same cause so I just need to figure out what that is. I was hoping to do that today but something more pressing came up so I had to deal with that first. But hopefully I will be able to move forward with this soon. Although it works for me, it bugs the hell out of me too :)

AndyS

To update. I have been spending some time trying to understand why the unread posts looks wrong, I am still going round in circles but at least it seems that the the database is correct so the forum is not doing the logic correctly. I am still trying to get my head around that part of the code but I have not connected all the dots yet, but progress is being made!

AndyS

After further investigation with the unread posts issue (which is connected to the wrong vote count and so on) it has been placed in the hands of IT now. After checking the database and NodeBB, the problem does not seem to stem from there but potentially due to how our forum is generally hosted it would seem. I was able to see two different set of unread lists from the same IP but on two different computers. Indicating that it is not consistently incorrect but something else seems to be getting in the way here. We hope to have it resolved soon, and I will focus on the other known issues while that goes on.