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.
mod_security is a server thing, not a vbulletin thing. You will have to find out if your server is running it and if the rules being applied (again, you must look at the rules on your server) may be interferring with this mod.
I'm talking about the apache error_logs and that is a server thing that you must enable.
I get the same error repeating which I dont think is related to my problem?
Quote:
`client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
/web/cgi-bin/php5: Symbol `client_errors' has different size in shared object, consider re-linking
Sweet mod man, I have only had it installed for a half hour or so, but I noticed in IE a little red warning window pops up in the new post warning me to read the following posts. O haven't seen it pop up for FF3 yet?
so in 1.06b one thing you will notice in the ACP is that there is an option to set the max amount of posts that can be displayed in the thread. Default is 30, so once there are 31 posts the oldest post on the page will disappear. (this feature was added because the page simply gets too huge if theres a bunch of people talking for a long time)
How do I only allow certain usergroups to have this functionality? Are there edits I can make in your files, to accomplish this?
How do you resolve the incompatibility with the 'Prevent double posting' Hack? Is there a fix?
I installed your product on my test forum. Here's the error on import:
Code:
Importing Product, Please Wait...
[:]
Warning: file_get_contents() [function.file-get-contents]: URL file-access is disabled in the server configuration in [path]/admincp/plugin.php(1995) : eval()'d code(2) : eval()'d code on line 1
Warning: file_get_contents(http://track.scriptasy.com/livetopic/1.05b/www.mysite.com) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in [path]/admincp/plugin.php(1995) : eval()'d code(2) : eval()'d code on line 1
Message
Product livetopic Imported
this is in the pipeline , I want to make sure that all major issues have been fixed first.
removed eval for the tracking call, if you dont want me to track the install you can comment that line out on the xml (its harmless though, just a numbers thing ^_^)
Live Topic Details »»
About Developer
Visit Web Site
DB Changes 
Is in Beta Stage 
02-13-2009, 08:29 PM
, I want to make sure that all major issues have been fixed first.
