Description: In previous versions of UBBThreads there has been a notification of staff when a user was banned or unbanned. In the 6.5 this feature disappeared. This mod ads this feature back. In addition to this the mod adds the ability to specify the ban duration. If the user tries to login before the ban time is over, he is shown the time that still remains until he is going to be unbanned. After the time is over, the user is automatically unbanned when he tries to login. The banned user receives an email about his ban, the ban reason and the ban duration. He also receives an email if he is manually unbanned.
Disclaimer: Please backup every file that you intend to modify. If the modification modifies the database, it's a good idea to backup your database before doing so.
Note: If you modify your UBB.Threads code, you may be giving up your right for "official" support from Infopop.If you need official support, you'll need to restore unmodified files.
//if the status changed insert the ban duration an reason, else not $ubanover = ""; $ubanreason = ""; if ($check != $isbanned) { /* status changed */ $ubanover = ",U_BanOver = '$banover'"; $ubanreason = ",U_BanReason = '$banreason'"; }
When writing in ban time and ban comment, but forgetting to uncheck the Member has Access Rights? it still sends PM's to admins and mods, would it not be smart to have a check for that field beeing unchecked, or automaticly uncheck when ban reason and/or time have been entered?
I have no clue on what I am talking about, but I did not get it to work in 6.5 without some changes.
Since $isbanned always was 1 in my test, i was banning another moderator as test... this is when it always sent an banned PM (maybe mail) even if the $hasaccess checkbox was not changed... is this check if status moderator to avoid banning of mods? I never tried banning a normal user btw. but are experimenting there maybe now... if i have time.
I changed like this, and now it works for me, thought i dont really know what I have done
Then later when one used showuser.php to look for the ban status it always said permanently banned... so i had to change the list(x,x,x,x,x) thing to fetch variables $banover and $banreason from the query...
I'm getting the following error when trying to edit a user as an admin:
PHP Parse error: parse error, unexpected $ in /admin/showuser.php on line 714, referer: showprofile.php?Cat=0&User=1981&Board=mkmf&what=ubbthreads&page=0
Since showuser.php doesn't have 714 lines, I'm guessing there's something wrong with showuser.tmpl?
Any ideas (i've tryed adding the mod from scratch two times now)?
well...the easiest would be to give him permission to edit users. Then he will be able to access this function(but also other functions that deal with user settings)
When I wrote any number in ban timer is always display that is pernament ban Reason of ban doesn't see in PM, but in code, in changeuser.php are lines:
I noticed with the new instuctions it is missing one thing.
At the end of the editing of the admin/showuser.php file it shows this --------------- }else{ $banreason_display = <<<END <textarea name="banreason" rows="5" cols="30" id="banreason"></textarea> END; $banduration_display = <<<END <input type="text" name="banduration" size="5" id="banduration" /> END; --------------------------
After the last END; there should be a }
It should look like this: ------------------------- }else{ $banreason_display = <<<END <textarea name="banreason" rows="5" cols="30" id="banreason"></textarea> END; $banduration_display = <<<END <input type="text" name="banduration" size="5" id="banduration" /> END;
} -------------------------------- With out that bracket, I ended up getting a Parse Error.
Just thought I would mention it. I was using the Time Ban and Notification 1.03 txt file when I ran into the problem.
[]UnixSpot said: I noticed with the new instuctions it is missing one thing.
At the end of the editing of the admin/showuser.php file it shows this --------------- }else{ $banreason_display = <<<END <textarea name="banreason" rows="5" cols="30" id="banreason"></textarea> END; $banduration_display = <<<END <input type="text" name="banduration" size="5" id="banduration" /> END; --------------------------
After the last END; there should be a }
It should look like this: ------------------------- }else{ $banreason_display = <<<END <textarea name="banreason" rows="5" cols="30" id="banreason"></textarea> END; $banduration_display = <<<END <input type="text" name="banduration" size="5" id="banduration" /> END;
} -------------------------------- With out that bracket, I ended up getting a Parse Error.
Just thought I would mention it. I was using the Time Ban and Notification 1.03 txt file when I ran into the problem. [/]
I found it, but here was my bug When I made copy&pase operations, I had
Donate to UBBDev today to help aid in Operational, Server and Script Maintenance, and Development costs.
Please also see our parent organization VNC Web Services if you're in the need of a new UBB.threads Install or Upgrade, Site/Server Migrations, or Security and Coding Services.