You haven't add the 'reason' column in the userban table.

The query is in the install_warn.php file, so I do not understand why it didn't get created.

Run this query manually:

ALTER TABLE `".TABLE_PREFIX."userban` add `reason` mediumtext

One more thing, after you run the upgrade_warn.php script, did you do all the mods that are described?

Rgds

Thanks for spotting this, you are right.

Strange, it looks as if the zipper screwed something up. In my directory structure, the mod_warn.php is in the modcp directory. Functions_warn.php is in the includes etc. I also have the kill_bans.php file in the includes/cron directory and I noticed it does not exist in the zip I uploaded.

I uploaded a new zip file, which should be OK, please let me know if it is.

Rgds

There is a picture in the thumbnails, the last one I think, which shows my warning types. You can start there, and move along.

Rgds

On Wednesday December 29th, at GMT 12:15, I just uploaded a new zip file, with the updated upgrade_warn.php, the file used to upgrade from Zero Tolerance's ver. 1.5 hack to the latest version of AWS.

It should upgrade ZT's hack directly to the specs of AWS V.3.0.

Let me know if you have any problems.

Ok I managed to fix a few things, but it seems that not all phrases were installed and not all tables were added to database.

I tried uninstall and using install_warn.php and upgrade_warn.php
but both give me errors like:

Does not excist
Duplicate
etc

Which means I am unable to install the phrases. So what i'd like to know is what i should manually remove from the database. So I can actually finish the scripts.

Once that ahs been done I run install_warn ? or upgrade_warn? Or both...

Thanks !

Run uninstaller.php from the latest zip file (download it again). Then run install_warn.php, that should do everything for you.

Rgds

Ok managed to fix it. I removed the wrong table. Readded it and now all seems to work fine!

Thanks for all your help and now I can finally enjoy this AMAZING hack.

Thanks again.

I was checking the install script just in case I 've screwed something up, and I just came back to answer. Glad you made it.

Rgds

Any idea why I'm getting my error?

Are you using a table prefix? If not, try running the query without the ".TABLE_PREFIX." part.

Hi

My only problem, is that the variable $_POST[comment] is not working. Both email and PM, are sent wiht a empty space for the moderator commentslike this:

The admin/moderator who warned you, entered this comment:

=======================================
(nothing here)
=======================================
May you help?

Yes, the zip seems to have maintained its dir structure. Thanks, I can get to work on installing now.

Installed very smoothly indeed. Now, I'm going to sit back and watch the bans flood in :) Thankyou for a great add-on.

Ooops, good one Acido, thanks for catching that. I forgot to copy an <if> thingy.

Please download the zip again, and upload the Warn.php file and the include/functions_warning.php file to your server.

Apologies for any inconvenience.

One word of caution please, if you allow me.

If you do use the automatic warning functions of this hack, make sure that you set up everything properly. For example, use your common sense when setting up your censorship options. Words have to be selected very carefully, or else expect complains from your users who get warned for calling another member by his name (like the short name for Richard).

Also, if you use the Automatic Warning for PMs, please understand that each PM which is caught containing censored words, is kept in a log, which you can see. This may be in violation of your user's privacy, since a PM is a private message from one member to another. You may receive complains about it.

Don't shoot the pianist for the above!

Rgds

Hi Sv1cec,

I updated to v. 3.0.1 but two functions are not working for me now:
- automatically issued warnings for posts which contain censored words
- automatically issued warnings for private messages which contain censored words

I entered censored words but If I use them in a post I will never get warned.
I created a normal 'registered user' testaccount to test this.

Can you give a helping hand?

I sure can.

First of all, from which version did you upgrade to 3.0.1? Have you installed V.3.0 first? Did the automatic warning worked with that version?

The automatic warning was first implemented in version 2.0. If you have installed that version, and followed all the upgrades, you shouldn't have a problem.

Make sure that you have the proper code changed in the files newreply.php, newthread.php and private.php. Also, please make sure you have done the appropriate changes in includes/functions_newpost.php.

Let me have that info, and we'll make it work for you.

Rgds

I upgraded from version 3.0 and no the automatic warning if a user uses a censored word was never working for me.


I'll recheck the changed in newreply.php, newthread.php, private.php and includes/functions_newpost.php and will then come back to you.

Hey, sv1cec
thanks for the solution on the colour for warning levels. I'll update the system and try your scripts this weekend. I'll let you know how it went!
Have a good end of the year and see you all next year!!!!

if i go into admincp > warning logs > complete removal
i get this:
The requested URL /forums/admincp/admin_warn.php was not found on this server.
my admincp directory is not named admincp
it's named something else.

how can i fix this?
btw this is a lovely mod.
thank you so much

another...

when i go into admincp > view banned users
and click on the "No users are banned from MyForum.com Forums - To ban a user, click here
i get a blank white page.
but if i were to go to admincp > users > ban users
it will come up just fine.
any idea?
thanks

I am looking for some one to install this for me Please PM so we can make arangements.

I guess I should fix it, by using the appropriate parameter, I'll try to find it tomorrow. In the mean time, you can always go into the admin_warn.php file and find the following line:

Replace the admincp in the path with whatever your admincp directory is.

As for the link, at the No users were banned etc., there shouldn't be a link there. Please find this code in admincp/admin_warn.php:

replace it with:

The reason I do not want that link there, is because in AWS, you are not suppose to ban users. Banning inside AWS is the result of warnings accumulated in a users account. AWS manages the warnings and the ban comes as a by-product, associated with the warnings. If you want to ban a user outside AWS, use the other link you suggested.

Rgds

The problem you had with the Complete Removal should be now resolved, in the admin_warn.php file included in the 3.0.2 zip file. Please let me know if it works.

Rgds

was i only suppose to simply upgrade to 3.0.2 and not do what you said in your second to last post?
i upgraded to 3.0.2 and uploaded the new admin_warn.php and now i got this when i try the complete removal error:

The requested URL /forums/admincontrolpanelnamehere/admincontrolpanelnamehere/admin_warn.php was not found on this server.

it displays the admincp twice

Either you upgrade the admin_warn.php included in the 3.0.2 release or you do the change I wrote to you before. Not both.

Rgds

i didn't do both at all.
i upgrade.
i got that double admincp directory thng i posted prior to this.

What does it shows you if you click on the link which has the warned user name? Does it come up with the proper page for that user?

when i clicked on the "View Warned Users " link, that page comes up just fine.

OK, open your admin_warn.php file and find the two lines which start with :

$x="<a href='

and

$cy="<a href='

Copy these lines from your file, here so that I can see what's going on. The two should be pointing to the same directory, only the first one has the forums URL in the front, which is redundant.

Waiting

Darn if I understand why this happens, but here is your solution:

Change those two lines with the lines below:

and

If there is no / in front of $admincpdir or no bburl, it uses the admincp directory twice!!! Go figure!

Sorry for that, I'll change it in the install file.

i'm getting this now:

Not Found

The requested URL /admincontrolpanelnamehere/admin_warn.php was not found on this server.

funny thing is that admin_warn.php does exist in that that directory :ermm:

That is crazy!!!

OK, convert both lines to:

and

Let's see if that works.

i'm smiling so you know what that means! ;)

Glad you made it. I would be happier if I knew why it was not working in the other two ways, but anyway.

Happy New Year and Happy Warnings

when i tried going running the 3.0.2 on my REAL LIVE forum i got this error when running the install_warn.php

Database error in vBulletin 3.0.3:

Invalid SQL: ALTER TABLE `vb3_userban`
add `reason` mediumtext;
mysql error: Duplicate column name 'reason'

mysql error number: 1060

How would I go about that if the user doesn't have any warning points, it'd appear as "0" for the value because a div in my postbit is being unused when their not warned and it looks bad.

something is wrong with your 3.0.2 install_warn.php file.
it won't do what it's suppose to do.
instead i've reloaded my db and used the install_warn.php from 2.3.5 and it altered what it was suppose to alter in the db.