This product is different from anything you have seen before, it raises the bar for forums. It will make your forums much more interactive, and also reduce server load.
Technical Details:
If a thread has been posted in X seconds then its now Live, if other users are viewing the Live topic and are on the last page they will experience a clean ajax experience while talking to other members. Once the thread is older than X seconds its no longer Live and it will now act like a normal thread. Also if a user edits one of their posts that's inside of the thread, it will be updated too so there is no longer a reason to ever have to refresh.
There is also logic for the viewer, the viewer of the thread has to be in an active state to see responses. An active user state is determined upon the users actions, if no actions were made in X seconds then the user is marked as inactive.
Also you may wonder why this could save your server bandwidth and CPU. If a user is refreshing to talk to another members the queries on a normal thread load are way more intense than the ajax call that this modification makes. So if you have 5 people talking to each other none of them have to refresh the page, all they are doing is simple page requests and one intense request when there has actual change.
You can test Live Topic with two users, you will see how amaizing this is... And probably spontaneously combust.
It looks like you have some extra divs in there. Probably a customized template is causing the issue. Create a new style with no parent:
Styles & Templates > Style Manager > Add New Style
Parent Style: No Parent Style
Title: Default vBulletin
Allow User Selection: Yes
Save
Now post in a thread where livetopic is active - do you still have the same problem?
Hey Lynne,
No it appears to be working perfect in default vBulletin aswell as one other custom template. So it must be a DIV thing could you point me to the template to look into finding this extra divs?
Thanks so much for the reply.
I made a post on vBulletin.com just then before reading your post so I will go delete that now
I'd take a look at both the postbit_legacy template and the postbit_wrapper template and that is going to also point to the space_open and space_close templates.
I'd take a look at both the postbit_legacy template and the postbit_wrapper template and that is going to also point to the space_open and space_close templates.
Hmm I just went through and compared all the divs to the default template and they all appear in the identical place. Same number of divs in the same location all closed at the end correctly, any other ideas?
Hmm I just went through and compared all the divs to the default template and they all appear in the identical place. Same number of divs in the same location all closed at the end correctly, any other ideas?
the only other thing I can think of is to use something like firebug to take a look at the code and see what is going on.
the only other thing I can think of is to use something like firebug to take a look at the code and see what is going on.
Hmm strange thing happens when I set the style to be 100% width wise the gab shrinks to about 1cm on each side...Does that give you any other clues Lynne?
Hmm strange thing happens when I set the style to be 100% width wise the gab shrinks to about 1cm on each side...Does that give you any other clues Lynne?
Nope. Like I said, you need to look at the page source and I would suggest using firebug to do so since it puts it in an easy to read format.
Live Topic Details »»
About Developer
Visit Web Site
DB Changes 
Is in Beta Stage 
01-29-2011, 02:41 PM
