Version: 1.00, by amykhar
Developer Last Online: Nov 2013
Version: 3.0.7
Rating:
Released: 02-21-2005
Last Update: 07-08-2005
Installs: 12
DB Changes
Is in Beta Stage
No support by the author.
I have seen some rules hacks that require users to agree to the rules before allowing them to post, but they have been board wide from what I have seen.
This one allows you to set up separate contracts on a per-forum basis. You can have a special contract for a debate forum and a different one for your sex forum. It's up to you.
THIS IS A BETA HACK. IT MAY HAVE BUGS. USE AT YOUR OWN RISK.
Planned features:
a - an install script to handle the queries, template and phrases. I want to work the kinks out of the code first.
b. - a ticket system by which you can temporarily or permanantly ban members from posting in individual forums if they violate the contract.
I have no plans of integrating this hack with any other ticket systems. I don't use any of the others because we really only have problems in one forum.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I installed it, but it is buggy. I am turing it off until it gets fixed, but I like the execution. This is the error I get, if it helps:
Quote:
Database error in vBulletin 3.0.7:
Invalid SQL:
UPDATE user
SET contracts = ,21
WHERE userid = 1
mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '21
WHERE userid = 1' at line 2
You will get a MySQL query syntax error number 1064 when you incorrectly use a reserved word in your query such as "when" or "order".
edit: but THIS POST suggests that the error may have been server-side due to low disk space! arrgh.. very confusing. Ya gotta love vague error messages.
I installed it, but it is buggy. I am turing it off until it gets fixed, but I like the execution. This is the error I get, if it helps:I surfed up some info on error 1064, and it said:edit: but THIS POST suggests that the error may have been server-side due to low disk space! arrgh.. very confusing. Ya gotta love vague error messages.
For some reason, it thinks something is in your contracts column of your user database.
For some reason, it thinks something is in your contracts column of your user database.
What is in that column for userid 1?
In PHPMyAdmin it says "2" under the contracts column, and I had previously clicked on a contract in Forum ID 2 before I got the error. Another user also has 2 in that column, and another user has 7 (and I had another contract in forum ID 7). I am not sure if this is how it works, but I will wait until later and will turn it back on. It may be a disk full error at my server, or something like that, since this worked well before. What would a database entry for that field with multiple contracts look like? Maybe it was erroring out because something was already there?
In PHPMyAdmin it says "2" under the contracts column, and I had previously clicked on a contract in Forum ID 2 before I got the error. Another user also has 2 in that column, and another user has 7 (and I had another contract in forum ID 7). I am not sure if this is how it works, but I will wait until later and will turn it back on. It may be a disk full error at my server, or something like that, since this worked well before. What would a database entry for that field with multiple contracts look like? Maybe it was erroring out because something was already there?
That may have fixed that bug, but I am still getting an error. This time it looks like this:
Quote:
Database error in vBulletin 3.0.7:
Invalid SQL:
UPDATE user
SET contracts = 2,21
WHERE userid = 1
mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '21
WHERE userid = 1' at line 2
Sorry to be a pain, but it just doesn't want to add a 2nd forum ID to that field for some reason.
EDIT: I went in to PHPMyAdmin and deleted that value ("2") from the contracts field, and was able to sign a different contract, but errored out again when adding a 2nd contract to the table.