Bug Bug with thread display Linear - Newest first

[Alan_SP]

Just installed and noticed that I don't see this:

As I'm watching threads in "reverse" mode, last posts are on first thread page, I checked last page (where first posts are) and there was it. Didn't checked other thread display modes and didn't had opportunity to check if it works in this mode at all, but just to let you know.

Thinking about it, you probably check if user is on last page and only if is, ajax threads kick its magic. You probably should also check users thread display mode and check if he's using reverse mode I prefer and in that case check for first page.

Also, just to note, after I installed it I had problem with server, server went to overload and qmail crashed. It may be coincidence, I don't know, but I'll check it farther and if it is connected I'll start new bug report.

And I just want to thank you for your great mods.

 

[Fillip H.]

Thinking about it, you probably check if user is on last page and only if is, ajax threads kick its magic.

That is what I'm doing, and is also the reason why you are having this issue.

I was not aware that they flipped the way pages work as well, I'll fix it in the next update.

 

[Alan_SP]

I was not aware that they flipped the way pages work as well, I'll fix it in the next update.

Just installed latest version 1.1.0 and bug is still here.

Please, can you fix this bug? I really like to look at threads in reverse order.

 

[Fillip H.]

I'll look into it again, I wasn't able to confirm it after applying the fix way back when but I'll have another go

 

[Alan_SP]

It's easy. Found thread with more than one page and select to view threads in Linear - Newest first mode.

You'll immediately see there's no notice about thread been active (live):

And of course, this means that mod isn't active, as you are actually looking at first, not last page. You just need to check what viewing mod is used, and if it is Linear - Newest first look for first, not last page to have thread active (live).

 

[Alan_SP]

Thanks, now it's fixed.