Advanced Warning System (Beta Version)

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

[Andreas]

Originally Posted by Milchi

Problems are solved. First of all, to all 3.5 Customers, use the attached functions_warnings.php, this should solve all problems

What my Effects where:

- If i activate the Load Functions File Plugin, noone Could login or logout.
- I was unable to issue post OR non-post-related warnings (if i am already logged in)
- there where some errors in displaying old warnings correctly

What where the problems?

KirbyDE didn't get it managed to convert all Scripts to 3.5. I assume that i did it, but don't know it really (it's going to be testet on tuesday, we update our 12 000 customers board ;-)).

I don't know on which file you based your modification, but definitly not on the file from the ZIP (which works fine except that global $vbulletin; has to be removed) as you got some some code in totally different locations, as well as completely wrong code like

PHP Code:

    $to=$db->query_read("select * from ".TABLE_PREFIX."user where userid='{$to}'");  // Grab Member Its Going TO
    $from=$db->query_read("select * from ".TABLE_PREFIX."user where userid='{$from}'"); // Grab Member Its Coming FROM 


[sv1cec]

Don't blame it to KirbyDE, it might be me who have made that mistake. Although it works on my board, but my board has the first vB 3.5 version of AWS I send to KirbyDE, when he jumped in on this.

In any case, good you have it solved.

[jluerken]

Complete Removal of Warnings is not working.
Wrong Link.

Please KirbyDE (Andreas) take a look at this hack again.
Its a quite useful hack which should be vB standard but actually it is not working correctly for 3.5.1

[Milchi]

I took the version which is for download here, downloaded at 13:00 Saturday morning 5. of november, GMT+1 German Time, based on this code, it is NOT functional and i made it to function ..

Complete Removal is working, you must click on the "inline mod" function of complete removal. don't know why the normal link is not working, didn't figured it out after 6 hours rewriting of code ...

@KerbyDE:
The Locations are different cause i restructered the file ;-)

This is the code from the ORIGINAL ZIP File, look (just downloaded it again this seconds)

PHP Code:

    $to=$db->query_first("select * from ".TABLE_PREFIX."user where userid='{$to}'");  // Grab Member Its Going TO
    $from=$db->query_first("select * from ".TABLE_PREFIX."user where userid='{$from}'"); // Grab Member Its Coming FROM 


[sv1cec]

Andreas is KirbyDE????

Hey partner, why don't you tell me so?

[jluerken]

Originally Posted by sv1cec

Andreas is KirbyDE????

Hey partner, why don't you tell me so?

Didn't you read the announcement that KirbyDE became an official supporter here and that he changed his loginname to Andreas?
Hopefully I find a time slot to phone with Andreas today.

It would be good to have a list with all open points so that I can check with him if he has time and is willed to

[Milchi]

Originally Posted by jluerken

Didn't you read the announcement that KirbyDE became an official supporter here and that he changed his loginname to Andreas?
Hopefully I find a time slot to phone with Andreas today.

It would be good to have a list with all open points so that I can check with him if he has time and is willed to

If so, pls give report (it's always funny if german people are talking english against each other *g*).

[jluerken]

Originally Posted by Milchi

If so, pls give report (it's always funny if german people are talking english against each other *g*).

Its a question of respect I think.
All others want also to know what we're talking about

Aaeeh ok, I am sure sometimes Andreas don't want to know cause in most cases this means work for him

[Andreas]

For the "Invalid User Input"-error:

admin_warn.php, replace all instances of

PHP Code:

do_finduserwarnings&userid=$vbulletin->GPC[temp_uid]"; 


with

PHP Code:

do_finduserwarnings&{$userid=$vbulletin->GPC[temp_uid]}"; 


This is an utterely ugly Hack, but should work until the backend is fully revised.
(Currently working on the frontend, which is 85% phrased by now)

I am sorry that I can't fully work on this, but time is a major problem.

[Andreas]

Originally Posted by Milchi

This is the code from the ORIGINAL ZIP File, look (just downloaded it again this seconds)

PHP Code:

    $to=$db->query_first("select * from ".TABLE_PREFIX."user where userid='{$to}'");  // Grab Member Its Going TO
    $from=$db->query_first("select * from ".TABLE_PREFIX."user where userid='{$from}'"); // Grab Member Its Coming FROM 


This code is correct, yours isn't (it's generating a mySQL result resource, while the needed data in $to and $from are arrays with the values ).