The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Advanced Warning System (Beta Version) Details »» | |||||||||||||||||||||||||
Advanced Warning System
IF YOU ARE RUNNING vB 3.6, THERE IS A NEW THREAD FOR THIS HACK UNDER THAT VERSION. vB 3.6 USERS GO HERE: https://vborg.vbsupport.ru/showthread.php?t=124477 This is a direct port of the Advanced Warning System, as it was implemented in vB 3.0.x. This port has all the features of AWS version 3.4.16, except the Notes. For a complete description of AWS capabilities, please refer to the following thread: https://vborg.vbsupport.ru/showthread.php?p=574374 The vB 3.5 compliant version of AWS includes: 1 Product XML (17 Plugins, 107 Phrases, 26 Templates, 43 Settings) 1 ACP Navigation XML 1 PHP Functions File 3 Images 2 PHP Frontend Files 1 PHP Admin CP File 1 PHP Mod CP File 3 PHP Cronjob Files This port would not be possible, without the help of KirbyDE, to whom I am greatful. KirbyDE will also be responsible for supporting you here, with questions related to this particular release. Also, this port would not have been possible, without the help of Juan P hernandez, who offered me a free test system, in which the porting was performed. The hack has been tested and it is believed to be bug-free, however since this is a major hack, I release it today (September 9th 2005) as beta. I hope you all enjoy it. History (Productversion) 3.5.b Initial Version 3.5.b1 Fixed a typo that caused Errors in User Datamanager. Fixed a wrong object reference in functions_warning.php 3.5.b2 Fixed a Bug that caused PHP Error Messages. Fixed a Typo in the Install Code that causes mySQL Errors. Updated the Template Edit instructions to be (hopefully) compatible with RC3 3.5.b3 Fixed User not showing up in automatic warning PMs Fixed 2 missing Phrases Fixed Hidden Warner being Used for Automatic Warnings Fixed "View x's Warnings" Button in Usermanager not working 3.5.b4 Removed one unsued Phrase, added one missing Phrase Fixed a Typo that caused PHP Errors when sending PMs Fixed a Typo that caused PHP Errors upon Installation Changed Product ID for Admin CP Navigation XML from vbulletin to aws, so it won't show up any longer if AWS is uninstalled/disabled. A bug was found which didn't allow you to delete an entered Warning Type. Bug fixed in the current distribution file. If you found a Bug, please report it at http://bugs.kirbydemos.ath.cx This helps to keep issues organized, which can't be guaranteed if it's only posted in the Thread. Thank you. P.S.1: After you install the hack per the instructions, please update your installation with the separate files listed. They are newer files not included in the zip. P.S.2: If you want to use the Notes feature, as it existed in AWS 3.4.16, please install AWS per the instructions in the zip file, and THEN follow the instructions included in the warn_notes_update_instructions.txt. IMPORTANT NOTE: Please keep in mind that this hack is not supported. What this means is that I have no obligation to support it. The reason for that, is because I have no access to a vB 3.5 system any more, so I can't work on this hack any more. Andreas (or KirbyDE) who undertook the support of this version of the AWS hack in the beginning, is obviously too busy to support it. So you are on your own, at least as far as the interaction with vB is concerned. If you have an issue with the hack files themselves, I'll do my best to solve it, but without a test environment, it is not easy. So users of vB 3.5 beware! P.S. May 31st 2006: The zip file uploaded today, should contain all the debugging done by Delphi, so it should be fine as it is. You do not need the other files listed at the right, only the zip. Download it and follow the instructions in it, for installing the hack. I leave the other files there, just in case some one needs them, they will be deleted later. SV1CEC Supporters / CoAuthors Show Your Support
|
Comments |
#132
|
|||
|
|||
Disregard, the user hit the ban threshold and I didn't realize he was banned.
Sorry..... |
#133
|
||||
|
||||
Quote:
|
#134
|
|||
|
|||
How long does the PM cut-off last for?? I am guessing it follows the warn maturity??
If so, can it be set to increment like bans?? I have my maturity set to 30 days and bans to increment starting at 1 day. It looks like PM cut-off will last longer than the ban. |
#135
|
|||
|
|||
Quote:
|
#136
|
|||
|
|||
Quote:
|
#137
|
||||
|
||||
When you had this for 3.0, we modded it so that it didnt have two segments 1. post related 2. profile related. We combined it so the system would just run off one set of programmed warnings and if it was post related it took the info, if it was not post related, then it didnt show any thead info. It seems more logical to have the system this way.
Reason is, what if you have a rule that could be either post related or not post related. Seems silly to have to program that same law twice in the system. Cant you just combine it? Drop the post related/non post related feature and just make it one set where the system pulls the thread link if the warn comes from the post or not if from profile? I just dont remember how to merge it from a year ago and really dont want to go through that again. |
#138
|
||||
|
||||
Seems to be more logical to me to have separate warning types.
Don't know hiw sv1cec thinks about it, but I think it should not be changed. |
#139
|
||||
|
||||
Why have two seperate. What Im saying is the way we modded this mod a year ago was the system determined if it was post or nonpost related in itself.
I have 10 laws which have different criterias and could be both, so that means I have to create 20 warnings in the system, 10 for each and when you look at the summary page showing all the warnings you could get it looks horrible with 10 dupes. |
#140
|
|||
|
|||
It could be modified to work as WNxWakko, but what's the reason? I fail to see the reason to spend some hours recoding that, just to save up some copying and pasting. I certainly do not have the time to do it.
|
#141
|
|||
|
|||
Ok well I have several problems. Here we go:
1)First problem comes up when using the AWS menu in ACP. I can use the managing warning options but when I click Manage Warning Types I see the bar that sayd Current Warning Types but I get a DB error above it: PHP Code:
PHP Code:
PHP Code:
I also had some problems with my postbit_legacy template, but I assume thats what I get for doing template mods at near 4AM. Any ideas? |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|