Bug Screen jumps while attempting a quick reply

[Antec]

Myself and many of my users seem to be running into the same problem with this mod (my users know it as Live Topic). The problem is mainly focused in one section where threads can get spammed with posts durning certain sporting events. I have copied a detailed complaint from one of my Staffers to give you a prime example of what is happening.

As I said before, I use Chrome, almost exclusively, so I'm not sure if these happen across several browser, and how prevalent they may be.

I have 2 issues basically when using Live Topic, both revolving around the action of posting a quick Reply.

The first of the two is simply that quite often times when I click the button to reply I wait 10-15+ seconds before it responds is anyway. I know this is a Live Topic specific issue because it happens A LOT in GDTs, and once every couple months outside of Live Topic threads. So, I'll chock up the infrequent ones to just something slow at that exact moment. The GDT occurences are too many in too short a time span to be coincidence.

The other issue is that, often times when I click Quick Reply, and it works; the entry box appears (or even if I just started typing in the Quick Reply at the bottom of the page), when new posts are made it doesn't maintain my scroll position. I end up jumping all over the screen (vertically) as new posts pop in, while I try to type my message. It's impossible to keep it stable in a busy thread.

Thanks for looking into these,
Kevin

GTD's are referring to the section of the forum where we use Ajax Threads.

There only seems to be the issue when a lot of users are posting rapidly. I have also noticed a LARGE increase in server load caused by PHP processes traced back to the Ajax Thread mod, also including large MySQL server use. It is a fairly large forum, but it only seems to occur when a Thread using Ajax Threads is very busy, any other time the load is within normal limits for a board this large. I have asked other users to report in detail on their issues with Ajax Threads, so if I receive any other reports I will let you know.

But is there any solution to the page jumping as described, because I have had this happen to me many times in the GDT threads, and it is Quiet annoying.

 

[Fillip H.]

I have uploaded a hotfix to v1.1.1 of AJAX Threads - please re-download the zip file and re-upload only this file: /dbtech/ajaxthreads/clientscript/ajaxthreads.js

This will ensure that no further AJAX requests are made until previous requests have been completed.

To see the change, you may need to perform a Hard Refresh (CTRL+F5). This does not work on Google Chrome and you will not see the change until you either manually purge your browser's cache or Chrome decides to remove the file itself.

This change should eliminate some of the congestion that may occur in busy threads if you have set your refresh rate too low (less than 5 seconds is generally not recommended).


PS / Edit: The actual topic (screen "jumping") is impossible to fix, so I focused on the issue I may have already been able to fix

 

[Antec]

So you are saying that, while attempting to write a quick reply, the screen will still loose it's position? If that is the case, what exactly does this fix do? Also, what about the excessive load?

 

[Fillip H.]

So you are saying that, while attempting to write a quick reply, the screen will still loose it's position?

Whether the screen loses its position is up to each individual browser, it is not something I am able to control.

If that is the case, what exactly does this fix do?

Addresses this:

what about the excessive load?

like I said:

This change should eliminate some of the congestion that may occur in busy threads if you have set your refresh rate too low (less than 5 seconds is generally not recommended).

 

[Antec]

Refresh rate is default on 5 seconds.

 

[Fillip H.]

If your server get hammered due to heavy traffic it can still occur, so it's still worth grabbing that change

 

[Antec]

If your server get hammered due to heavy traffic it can still occur, so it's still worth grabbing that change

I have installed that change, but the load is still spiking. The refresh rate is set to default.

 

[Fillip H.]

It wasn't designed to fix any load spikes, just prevent AJAX Threads from adding unnecessary load