Version: 3.6.9(C), by Delphiprogrammi
Developer Last Online: Aug 2015
Category: Administrative and Maintenance Tools -
Version: 3.6.8
Rating:
Released: 08-19-2006
Last Update: 10-02-2007
Installs: 211
DB Changes Uses Plugins Template Edits
Code Changes Additional Files Is in Beta Stage
No support by the author.
Advaned Warning System
This is a port of aws and i release this with permission...(yes i did ask the original author)
This version of the warning includes
1 vbulletin 3.6.x product file (XML)
1 admincp navigation XML
1 functions file(functions_warning.php)
3 images
3 cronjobs
1 modcp file to allow moderators to view warnings information without having to give admincp access(mod_warn.php)
1 admincp file to manage the system options(admin_warn.php)
1 XML to control permissions(bitfield_aws.xml)
For a completer list of the system features you can refer to this
This version will also require vbulletin 3.6.x to run.If you run 3.5.x or any other release then 3.6.x you will see a message.
This system is tested for a long time and i believe it's stable enough for a public release HOWEVER since this is a major hack and i'm just human please consider this first public run still as "beta"
instructions ow howto install can be found in the docs directory within the zip
statistics
25 plugins
27 templates
5 new MySQL tables
3 standard vbulletin tables alterd (user,post,and usergroup)
827 phrases
47 settings
updates
A problem has been found where no link is provided to view your own warnings(normal users) in the member profile only i fixed this.To get the fix you will need to reedit your "MEMBERINFO" template and reimport product-aws.xml (set allow overwrite to yes)
a product depency whas added the system will no longer install on PHP 5 (in response to continued error reports on that PHP version)
to report a possible bug
please go the system bugtracker here you can use the folowwing account
username:bugreporter
password:awsbug
no need to register yourself
30-11-2006
People on PHP 5 can follow this instructions to avoid the PHP version related error message BUT remember you are on your own if you do this.I won't upgrade my PHP until PHP 5 is there main stable release (www.php.net)
1-1-2007
A bug has been reported in the system.This bug whas causing vbulletin to throw an error when you try to use admincp => users=> add a new user
Quote:
Fatal error: Call to a member function clean_gpc() on a non-object in class_dm_user.php(2385) : eval()'d code on line 35
Solution
Edit plugin "AWS:warn link in usermanager" and replace all code with this
This release includes a fix for the problem "call to member function on a non object class_dm_user.php)" when you try to add a new user manaually (after submitting the form)
The members can not see the details of the warnings, they can see how many warning points other members have and how many warnings, but not the details.
The cron job will either render the warnings "Inactive" or it will remove them all together. It depends on your settings in the AdminCP. If you are using the Historical option, warnings are never deleted completely. They always remain in the members accounts, so that (a) they act as reminders for the members and (b) they show the members past history to the admin team. If you want the warnings to be completely deleted, you may select not to maintain historical data.
Quote:
I tried not maintaining the historical data. The warnings drop of when they mature (which is what I want) But now the bans drop off when the ban ends. Not when they mature.
package has been updated when you import product-aws.xml now it will automatically add a link to Warn.php?do=ViewMyWarnings in your navbars quick links menu (this done through a template hook) and this is new in use to me maybe in th future i can make it more automatic and kill a few more template edits as this hack requirers allot of them
I have a test account on my board, and gave it a warning and everything ok, but when I loged in with that account I can't see the warning, and get nopermission error page (sefault template of vBulletin).
and that happen everytime I tried to press on view my warnnings link !!
I put (Can view warnings) option in usergroup to yes, and did the same with other secondary groups that user has.
anyway in showthread page user can see warnings and warnings level of other members !! Is it work as designed??
I have a test account on my board, and gave it a warning and everything ok, but when I loged in with that account I can't see the warning, and get nopermission error page (sefault template of vBulletin).
and that happen everytime I tried to press on view my warnnings link !!
I put (Can view warnings) option in usergroup to yes, and did the same with other secondary groups that user has.
anyway in showthread page user can see warnings and warnings level of other members !! Is it work as designed??
Depends on your settings if you set setting "who can view the warnings points and bans" to all people can see that if you set that to Mgm only mods and up will see it
Depends on your settings if you set setting "who can view the warnings points and bans" to all people can see that if you set that to Mgm only mods and up will see it
my setting is Mgm, and still user can't see his warning page and get the default no permissions page.
and in the thread that he began and get his warning, he can see the warnings for other users under thier names only in that page, but can't see it in the second page of the same thread !!!!
anyeway the most imprtant point for me now is letting users to see there warnings, so what I can do?
Fatal error:
النص الذي أدخلته كبير جداً ($postlength حروف). الرجاء تقليله إلى $vboptions[postmaxchars] حروف .
$user[username] قام بإلغاء خاصية إستقبال رسائل خاصة . أو أنه غير مسموح لك بإرسال رسائل خاصة .
Unable to proceed with save while $errors array is not empty in class vb_datamanager_pm in /includes/class_dm.php on line 765
the arabic letters said your text is too long.
or you can't send pm maybe the user disabled recieving pms.
after deleting a warning I redirected to eeror page (The page cannot be found)
I get the reason of this error, because the link have a capital letters and in redirection we get the link in small case warn.php?&do=viewwarnings&id=xxx