Quote:
Originally Posted by Delphiprogrammi
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
PHP Code:
$get_bans=$DB_site->query("select b.*, u.*, a.username AS warner, w.*, wt.* from ".TABLE_PREFIX."ban_dates as b
LEFT JOIN " . TABLE_PREFIX . "user AS u ON(u.userid = b.banned_user)
LEFT JOIN " . TABLE_PREFIX . "user AS a ON(a.userid = b.banned_by)
LEFT JOIN " . TABLE_PREFIX . "warnings AS w ON(w.wid = b.banned_warning)
LEFT JOIN " . TABLE_PREFIX . "warning_types AS wt ON(wt.tid = w.warned_warning_id)
ORDER BY $orderby LIMIT $startat, $perpage");
|
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).