Helpful Information
 
 
Category: Advanced Warning System (AWS)
User cannot PM the automatic warner

When you set a user to be the automatic warner and have a collector of disputes, there's no way for other users to send a PM to the automatic warner. All the PMs would go to the collector of disputes.

I don't know if this is a bug, but I just like to point it out. :)

When you set a user to be the automatic warner and have a collector of disputes, there's no way for other users to send a PM to the automatic warner. All the PMs would go to the collector of disputes.

I don't know if this is a bug, but I just like to point it out. :)
No, it is not a bug, it is mentioned in the instructions. The automatic warner is not supposed to be a real account, it's just a "false account" which the warnings are issued from, if you do not want the real moderator to show. In that case, someone has to see the replies that might be send back, so a "Collector" is defined.

Rgds

I created a dummy account to handle it and set it up as the autowarner. The account has everything turned off in terms of PMs, email, etc. and it works flawlessly.

That's what you should do. Then setup either a particular moderator or an admin, to hanlde complains.

Rgds

That's what you should do. Then setup either a particular moderator or an admin, to hanlde complains.

Rgds
Ok. Thanks. But I have another problem, members are complaining that they got like 70 emails from me saying that they've been warned. I assume that's out of the ordinary?

What are these warnings? Check your Warnings Log. Why are those warnings issued? If you haven't issued those warnings, then it is the Automatic Warnings function that issues them. The Automatic Warnings function is based on your censorship options. If your members use words which are in your censored list, they will get warned. In the Warnings Log, you can see why they were warned, for which post they were warned etc. Check these out. If they are warned for no reason, then you have made a mistake somewhere when editing the files. Check your newthread.php, newreply.php, editpost.php, if the warnings are post-related.

Rgds

What are these warnings? Check your Warnings Log. Why are those warnings issued? If you haven't issued those warnings, then it is the Automatic Warnings function that issues them. The Automatic Warnings function is based on your censorship options. If your members use words which are in your censored list, they will get warned. In the Warnings Log, you can see why they were warned, for which post they were warned etc. Check these out. If they are warned for no reason, then you have made a mistake somewhere when editing the files. Check your newthread.php, newreply.php, editpost.php, if the warnings are post-related.

Rgds
The posts are non-post related, and they say that a warning has been removed. However, there IS no warning that is removed. Where its supposed to say which warning is removed, it's blank.

These are emailed to users who have had a warning removed. Also, the emails comes at random times.

The posts are non-post related, and they say that a warning has been removed. However, there IS no warning that is removed. Where its supposed to say which warning is removed, it's blank.

These are emailed to users who have had a warning removed. Also, the emails comes at random times.
EDIT: Somehow their maturity dates got messed up, and it said 12-31-1969! I don't know how that happened. Possibly with the update to 3.3.0.

The upgrade shouldn't touch the warning dates or the maturity dates. The code was not changed there.

Do you have any real warnings you want to keep? If not, just uninstall the hack and re-install the latest version. I can't understand what this is all about.

The upgrade shouldn't touch the warning dates or the maturity dates. The code was not changed there.

Do you have any real warnings you want to keep? If not, just uninstall the hack and re-install the latest version. I can't understand what this is all about.
There was only two warnings that had 1969 has its maturity date. I physically had them removed and everything should be fine now.

The 1969 date is shown when there is no real date entered in that column (or any date column).

Just something to keep in mind.










privacy (GDPR)