No, I am no coder hehe.
I wondered myself it was possible to do.
Thnx anyway

If you do not mind the fact that the button will not say "Warn John" but "Warn User" (without the user name), I can do it for you

Rgds

Can someone send me that part of the private.php file, I asked for, a couple of posts back?

Rgds

Yes why not, when you press on the button you can see the user who you warned , ;)

Hello, I've just installed AWS "by the book", version 3.1.2
I get the following errors in admincp:
When clicking Statistics - Bans per User:

/admincp/admin_warn.php

Database error in vBulletin 3.0.6:

Invalid SQL: select b.*, u.*, a.username AS warner, w.*, wt.* from ban_dates as b
LEFT JOIN user AS u ON(u.userid = b.banned_user)
LEFT JOIN user AS a ON(a.userid = b.banned_by)
LEFT JOIN warnings AS w ON(w.wid = b.banned_warning)
LEFT JOIN warning_types AS wt ON(wt.tid = w.warned_warning_id)
ORDER BY b.banned_user, b.banned_ban LIMIT 0,
mysql error: You have an error in your SQL syntax.

When clicking Statistics - Warnings per User

/admincp/admin_warn.php

Invalid SQL: select * from
user u where warnings>0 ORDER BY userid ASC LIMIT 0,
mysql error: You have an error in your SQL syntax.

Looks like the $perpage variable isn't set for some reason, see LIMIT 0,
A bug?
What should I check for?
Thanks for any info :)

no that can't be a bug why ? because it works in here probably you have a typo somewhere also if you have bans already already you must run the included update_bandates.php script

Already run /admincp/update_ban_dates.php before.

This is weird, if I add this row, just before the code you specified above:
$perpage = 10;

it works!!!

so the $perpage does indeed loose its value somewhere...maybe a typo, I don't know.

$perpage=$warn_opts['warnings_per_page'];
echo "warnings_per_page=".$warn_opts['warnings_per_page']."<br>";

Told me that $warn_opts['warnings_per_page'] is empty. Where is this variable declared, assigned?

Any other ideas?

I do not think it is a bug, and I do not think it is a typo, the reason is that admin_warn.php is not a file the user edits, it is in the zip file. And it can't by a bug, because, as Delphi says, it works elsewhere.

Check your warning_options table in your database to see what value it has in that column. If it has nothing, set it from the AWS Options and check again.

BUT: I would strongly advise that you download and install the latest version. Use the uninstaller to uninstall the previous one, and then run the install_warn.php file again, from the newest version (I'll be uploading version 3.1.3 in a few minutes).

Hmm...wtf?!? :)
My warning_options table is empty...how could that be...gaaaah!!!

I'll try reinstalling it.

EDIT: thanks for the help :)

Allrighty...now it works...must have missed some part in the installation.
But the installationprocedure was no picknick, a lot of messing around in the code :) , and I'm no newbie...it would be great to have a more simple installation. Anyway, thanks for the help.