you're wonderful Brad, thank you so much!

there is no setting that I know of to control which staff members can edit the sb. Any staff member that can see the edit options by clicking on the word Shoutbox at the top of the sb can edit. As far as editing ALL shouts.. only the ones that you give the /prune command to can delete all sb posts at one time

Is this what you were asking?

*Clicks install*

A nice upgrade for my forums. Thanx ZT!! Btw RE4 iz teh best game Ev3r!!:rambo:

Can you share it with us?

And another useful modification for this hack would be "/prune [options]" command. My board have 100 pages of shouts, and I wanted to prune the old shouts. But the only option I can do is to prune all of them. I wish I could prune messages from number x to number y or from date x to date y. :rambo:

the problem is i give mod spots to people who mod they own section for their hip hop groups, however they are not on my staff....i need a function to determine who can edit the shoutbox, possible update on the shoutbox?

Thanks a lot Brad. Working just fine now. ^_^

Thanks a lot Brad. Working just fine now. ^_^

EDIT: Oops.. sorry about the triple post.. vbulletin.org was acting up for me. :(

Thanks a lot Brad. Working just fine now. ^_^

EDIT: Oops.. sorry about the triple post.. vbulletin.org was acting up for me. :(

Thanks a lot Brad. Working just fine now. ^_^

please, someone can code a word wrap function??

Yay thanks for the update!

Littleman, my installation said "Loading" too. I didn't have the vbshout.php in the forum directory. Copy that file there and it should start working [assuming permissions are correct].

Maybe this question has been answered before, but I couldn't find it in this thread. I'm runnin' 3.5.4 and special charactors like quotation marks and greater than/less than symbols show up as HTML code in the shout box unless I turn the vBcode and smiley option off in the ACP.

Sooo, now my users can't use smileys because of this glitch. Any fix for this??

I was still having problems with quotations etc, until i removed the who's shouting addon.Problem was fixed right away..

I don't have that addon, and I'm having the same problem.

A possible quick solution to limit access to the archive and archive functions by user group :

There is a template called forumhome_vbshout that has as part of its contents a line with the following info: <a href='vbshout.php?{$session['sessionurl_q']}do=archive'>Shoutbox</a>

Perhaps one could possibly change that line so that it reads:

<if condition="can_moderate()">
<a href='vbshout.php?{$session['sessionurl_q']}do=archive'>Shoutbox</a>
<else />
Shoutbox
</if>

While that will not prevent a user from manually typing in the name of the link. It will prevent those without the knowledge of the links parameters from going further.

If one is a bit more interested in digging deeper one could, possibly, open the vbshout.php file and find:

if ($_GET['do'] == 'archive')
{

located around line 356/357

Then one could, possibly, insert below the line with the "{" and above the line "$navbits = array("vbshout.php?" . $vbulletin->session->vars['sessionurl'] . "do=archive" => 'Archive');"

something like:

//use for an individual access
//if ($vbulletin->userinfo['userid'] != X)
//use for usergroup access
if (!(in_array($vbulletin->userinfo['usergroupid'], array(6,7))))
{ print_no_permission();
exit();
}

Where 5=super moderators, 6=admin, 7=moderators, and (optional) X1= what ever other usergroup one wants to include (if one was not to use X1 then do remember to remove the "," as well).

Then it should be highly possible that one would, possibly, be able to highly limit the access to the Shoutbox, a most wonderful product!, archive functions.

Of course one would be on their in doing such things.:surprised:

i still need a wordwrap function because i have the shoutbox in the left frame of vbadvanced. long words crashing the tables.

I've just noticed after installing vbShout (although it may have been happening before) that, when I log in from the forum home (where the shout is) I get the Thank You and am redirected back to the forum home but it doesn't recognize that I'm logged in until I go to a second page. Any ideas?

Yeh same situation, I aint got any other plugins for it. And the quotes and any other special characters dont work. Is there any fix or work around??

Whenever I enter a message with a quote in it and go to edit it, the message is truncated after the quote. Are others seeing this problem and is there a solution? Thanks!

Awesome, I'll upgrade my shoutbox right away. Good job on the update!

If I type "" i get &quot;&quot;

I have just downloaded and installed the latest. or do i need to apply the patch that he put in this thread.

Is there a way to display the shoutbox collapsed by default?

Hello, i`m trying to prevent the guest from seeing the shoutbox, But when I ban the guest id from viewing the shoutbox. I get an error message.
can anyone help me with this?

I entered the correct id for the guest which is "1" but it is not working.
thanks:banana:

can you code a word wrap for too long words in the shoutbox when i have it on the left panel of my forum plz? it's a greate update for all peopele that have the shoutbox in a sidepanel from the vbadvanced portal.

Ok, I am getting frustrated with this "viewing the shoutbox" issue. I have read all the posts about it but it's still not doing what I ask for. CMPS is installed so index.php is the CMPS page and forum.php is my forum index page. I have another plugin that does custom WOL locations and forum.php is set to it.

This problem never happend until I moved to a new host which seems to be on a different version of apache. This is a bug in the program and need to be fixed. I look at the WOL page very often to see where people are on the site and having this bug is very annoying. So instead of telling me to read the previous posts about this issue does anyone know of any other solutions? I shouldn't even have to do anything because it should just work like it did before.

I know this may not be a direct shoutbox support thing, but does anyone have any idea how to fix this?

I also get that word error after symbols in the shoutbox too, most notably the & symbol, when typed in shows as &amp; in the shoutbox message, no add ons.

to fix the 'no gap' problem edit the forumhome_vbshout template and add <br /> at the top,

to fix the symbols problem, installing the latest version should fix that,


CP1

To get date & time in shoutbox You have to add one line in forumhome_vbshout_shout template.
under
add:
This line some how is missing... :)

How can i set the $pagenav in to the shoutbox ?

Someone here who can help me out..

Have not checked the rest of the script you attached, but what is the purpose of the last bit?

I thought the latest version is supposed to filter out html tags to avoid java script inject. Your code seems on the surface to bypass the fix?

A better way to handle html inject will be:


$vbulletin->options['allowhtml']

Defaults to off when bbcode is used. That is why everyone is getting the &gt; etc. using the latest version.

Basically if one uses bbcode in the shouter. That is no need to worry about html inject because bbcode parser will handle special html tags by default.

There appears to be a bug with speech marks. " is replaced with &quot;

Tested on vB 3.5.4
Using the vBShout fixed v3 zip.

Hi,

How many shouts will be stored in database?

I'm using it over a few months. Is all the shouts so far'll be in the DB or it'll be cleared?

They're all saved until you prune them.

Can please help me somebody with a function that cut long words??
look @ attachment

Any way to get the ignore list to work with this?

Still hoping on figuring out why it doesn't show the last shout when reloading the page :( just jumps to the middle.

Was anone successful in getting it to appear in a specific forum either?

I'm just getting 'loading' at the bottom of the board's main page. :-(

http://www.twolvescentral.com

As an update to my other post about the WOL showing everyone on the forum index as "viewing the shoutbox" I believe it is not because of a newer apache but because of PHP 5 that I now have on my new hosting. My old hosting had PHP 3. So if you could please make this extention PHP 5 comptable to fix that bug I would appreciate it. Thank you.