Miscellaneous Hacks - Live Topic

. . . . . . . . Brought to you by scriptasy.com

. . . http://www.Scriptasy.com

Live Demo:

Live Topic 1.07b Demo (you must be logged in, and the topic must be "live")

Videos: 1.00b 1.06b

watch the damn videos... ^_^

Description:

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.

Found a bug? Want to request a feature?

Live Topic - Project Manager

Installation:

This is take less than 3 minutes to install, takes longer to notice its amazing feature. (you need multiple people to be active in the same topic)

Upgrade:

[1.01b to 1.XXb] Uninstall the product, then reinstall it. Overwrite all old files with new files and you should be fine.

[1.02b to 1.03b] Overwrite files, upgrade product (dont install product)

[1.03b to 1.04b] Uninstall the product, then reinstall it. Overwrite all old files with new files and you should be fine.

[1.04b to 1.05b, 1.05b to 1.06b,1.06b to 1.07b] Upgrade the product. Overwrite all old files with new files and you should be fine.

Works With (FF2, FF3, IE6, IE7, IE8, SF2, SF3, CHROME):

vBulletin [3.8.X]

get the vBulletin [3.7.X] version here

INCOMPATIBLE HACKS:

• USC
• PassiveVid (1.x)
• gXboxLive
• Topic (incl. Blog) of the Week
• Marquee Text

Versions:

1.01b
1.02b

fixes

safari 2 support
safari 3 support
google chrome support
added live topic icon on new posts page
fixed security issue, strongly suggest upgrading!

changes

added live edit (to avoid a performance hit i had to add two rows to two tables in the database)
added external style sheet

1.03b

fixes

fix double post
phrase notification
fixed an edit bug for people with table prefixes

changes

ability to change interval in ACP

1.04b

fixes

javascript error for guests
fixed live topic activation (first poster to raise a dead topic)

changes

auto quick reply focus after post

1.05b

fixes

css flaw
js error for unsupported browsers (random)
fixed chrome issue

changes

edit notification - thanks to nso
rebuilding some of the original logic to hopefully prevent product conflicts

1.06b

fixes

fixed a little javascript issue that had to do with displaying posts
uses GPC cleaner now

changes

limit the number of ajax posts on the live topic (example 40) and fade them away.
changed the way the hooks are used
tightened up everything a bit

1.07b

fixes

fixed a bug where the live topic notification always making an ajax call

changes

support user ignore list
changed the way the javascript logic worked (hopefully there are less compatibly issues) added support for IE6 and IE8

1.10

hmm

{Mark As Installed}

{Don't forget to vote for Modification of the Month}

[Smitty]

Originally Posted by DobieGillis?

only issue left is Firefox...works fine with IE7 and Opera. Firefox goes white and stops. This is only in quick reply.

Has anyone else verified the Firefox Quick Reply issue?

[DobieGillis?]

Originally Posted by Smitty

Has anyone else verified the Firefox Quick Reply issue?

no, just the users on my board. It works fine with every browser but that one, every one of them.

[inciarco]

On My Board (vB37x) FireFox and Google Chrome Work Fine with Quick Replies and Normal Replies. (I've Tested with 2 Users on my Computer with 2 Browsers Opened, FireFox and Google Chrome).

This Last Version has the Problem with Old Posts Hiding After X Posts, which I Described in one of my Posts on this Thread (or the vB37x Version).

I Think that Perhaps you're Describing One of the Following 2 Problems:

1. The Bug I Mentioned with the Hiding of Old Posts, because the Posts Aren't Shown on the User's Window but they Do on the Other User's Browsers; that After X Posts, as I Documented on one Post with some Tests I Made.

2. If you have the DoublePost Prevention, and You Haven't Applied the Solution Provided by Coders Shack to that Problem, it happens Exactly as You Described, because the Double Posts Merge but have the Conflict with this Mod in the Display of the Post Edit, which is Solved 100% with Coders Shack Solution and Displays Great the Post Edits.

If None of the Ones Before, perhaps could be a Conflict with Other Mod, you'll have to Disable them One By One until you Find the Conflicting Mod. Once You Find It Please Post the Conflict Here for All of Us to Know and If Possible Propose a Solution.

Also, Perhaps on the New Update that Coders Shack Mentioned for Version 1.07b, the Improvements on the Code would Solve the Problem You Mention, as Perhaps some of the Conflicts with other Mods will be Solved. We Have to Wait and Test the New Update.

My Best Regards.

[DobieGillis?]

Originally Posted by inciarco

On My Board (vB37x) FireFox and Google Chrome Work Fine with Quick Replies and Normal Replies. (I've Tested with 2 Users on my Computer with 2 Browsers Opened, FireFox and Google Chrome).

This Last Version has the Problem with Old Posts Hiding After X Posts, which I Described in one of my Posts on this Thread (or the vB37x Version).

I Think that Perhaps you're Describing One of the Following 2 Problems:

1. The Bug I Mentioned with the Hiding of Old Posts, because the Posts Aren't Shown on the User's Window but they Do on the Other User's Browsers; that After X Posts, as I Documented on one Post with some Tests I Made.

2. If you have the DoublePost Prevention, and You Haven't Applied the Solution Provided by Coders Shack to that Problem, it happens Exactly as You Described, because the Double Posts Merge but have the Conflict with this Mod in the Display of the Post Edit, which is Solved 100% with Coders Shack Solution and Displays Great the Post Edits.

If None of the Ones Before, perhaps could be a Conflict with Other Mod, you'll have to Disable them One By One until you Find the Conflicting Mod. Once You Find It Please Post the Conflict Here for All of Us to Know and If Possible Propose a Solution.

Also, Perhaps on the New Update that Coders Shack Mentioned for Version 1.07b, the Improvements on the Code would Solve the Problem You Mention, as Perhaps some of the Conflicts with other Mods will be Solved. We Have to Wait and Test the New Update.

My Best Regards.

I'm thinking your first solution might be it. I may go back to 1.05 and see if that helps. Thank you very much!

[inciarco]

Originally Posted by DobieGillis?

I'm thinking your first solution might be it. I may go back to 1.05 and see if that helps. Thank you very much!

You can Solve it just specifying a Big Number for Old Posts to Hide, like 100 or 200 Posts Per Page, or more, not the 30 Proposed; you can do that on the Mod's Options.

Try that Before Installing an Old Version, Coders Shack Optimized the Code on latest Update, so I guess it should Load Less the Server than Old Versions, and Also Added some Really Good Extra-Features.

My Best Regards.

[DobieGillis?]

Originally Posted by inciarco

You can Solve it just specifying a Big Number for Old Posts to Hide, like 100 or 200 Posts Per Page, or more, not the 30 Proposed; you can do that on the Mod's Options.

Try that Before Installing an Old Version, Coders Shack Optimized the Code on latest Update, so I guess it should Load Less the Server than Old Versions, and Also Added some Really Good Extra-Features.

My Best Regards.

so the higher the number the better? Little confused about that

[inciarco]

Originally Posted by DobieGillis?

so the higher the number the better? Little confised about that

You Should do That Until the Problem (Bug) is Solved to Solve Your Problem on the Live Quick Replies. (I Think and Hope that In The Next Update Coders Shack will Share with Us)

Once the Bug is Solved you should set it to the Maximum Number of Posts you'd like your Users to See on the Live Page, (the Default of 30 Posts is a Good Number); actually is a Really Cool Feature (Coders Shack is a Great Coder, I Hope this Mod Win the Mod Of The Month Contest), and seeing the Old Posts Get Hidden is Really Amazing.

My Best Regards.

[DobieGillis?]

Originally Posted by inciarco

You Should do That Until the Problem (Bug) is Solved to Solve Your Problem on the Live Quick Replies. (I Think and Hope that In The Next Update Coders Shack will Share with Us)

Once the Bug is Solved you should set it to the Maximum Number of Posts you'd like your Users to See on the Live Page, (the Default of 30 Posts is a Good Number); actually is a Really Cool Feature (Coders Shack is a Great Coder, I Hope this Mod Win the Mod Of The Month Contest), and seeing the Old Posts Get Hidden is Really Amazing.

My Best Regards.

agreed which is why I'm hanging in there with Live Topic, best Mod I've seen.

[MarkJW]

Originally Posted by DobieGillis?

I already have and noticed that when I uncheck javascript enabled in FF, it works fine except I don't see the posts flash with the other browsers. Conclusion, FF sucks!

No, FF does things the "correct" way. Either the code sucks or the browsers that work correctly with this code suck.

[DobieGillis?]

so 1.07 is out?