Warning count in welcome area of header

I'd like to have the user's warning count in the welcome area of the header. Something like:

Welcome, user.
You last visited: Today at 13:46
Private Messages: 0 Unread, Total 9
Warnings: 3

But only if the user has warnings, of course.

How would I go about this?

Jim

[sv1cec]

Nice idea, I'll add it in the next version.

Go to your navbar template and find:

<if condition="$show['pmstats']"><br /><phrase 1="$vbphrase[unread_x_nav_compiled]" 2="$vbphrase[total_x_nav_compiled]" 3="$session[sessionurl]">$vbphrase[private_messages_nav]</phrase></if>

Right below that add:

<if condition="$bbuserinfo['warnings']>0"><br />Warnings: $bbuserinfo[warnings]</if><if condition="$bbuserinfo['warning_level']>0"> - Warn.Points: $bbuserinfo[warning_level]</if><if condition="$bbuserinfo['warning_bans']>0"> - Bans: $bbuserinfo[warning_bans]</if>

If you want that to appear in red letters, just add a

<font color='red'>

before the new code, and a

</font>

after it.

It should work fine.

Rgds

[Tom1234]

John,

Could you please start separating the "necessary" code/template modifications from "optional" mods like this? I think many of us prefer to change as little code as possible even if it means missing little features like this, but it is not easy to see which mods are essential in the installation instructions.

[sv1cec]

Usually, I try to remember to write in the instructions "This is optional" but I do not always manage it! LoL. The thing is, what is optional and what is necessary? I am sure the are sites out there, which do not use even half of what AWS is capable of doing. Still, the instructions are there, because I have no idea when the admin will decide to turn that functionality on or off. Imagine that someone does not do the changes in the private.php or in editpost.php and newreply.php because he (at the installation time) does not want to use the Automatic Warnings feature. Then at a later time, he goes to his Warning Options, and turn that feature on. The feature will obviously not work and the user doesn't know why.

It's better to alter the code as instructed even if you do not plan to use it, than not. I understand your point, but you have to also understand that when you decide to start altering your vB code, you are taking risks. Especially when installing such a complicated hack, you'd better know what you are doing.

Rgds