![]() |
Quote:
DESCRIBE warnings Rgds |
Quote:
HTML Code:
<if condition="$bbuserinfo[usergroupid]==6"> HTML Code:
<if condition="$bbuserinfo[usergroupid]==6 OR $bbuserinfo[usergroupid]==13"> |
Quote:
Code:
Host: localhost |
Quote:
That does not make sense. Your table has the right columns, the SQL statement is trying to insert the right number of values, what on earth is this? Here is my warnings table description: HTML Code:
wid int(15) PRI auto_increment Do me a favor, try to add a non-post related warning from a user's public profile. See if that produces the same error. Rgds |
OK here it is.
Code:
Database error in vBulletin 3.0.5: OK I just tried a warning from a thread and got this Code:
Database error in vBulletin 3.0.5: |
Quote:
PHP Code:
PHP Code:
Rgds |
Quote:
Well, it took a little trial and error, but I got it to work. If you're interested, the code I used follows... Again, Admin is 6 & 13, Super Mods are 5 & 21, and Mods are 7 & 20: HTML Code:
<if condition="$hierarchical=='Yes'"> |
Quote:
One thing I would suggest, is to avoid using the Hierarchical Schema, and declare those additional user groups, as protected user groups, so that they can't be warned. I know that not using the hierarchical schema reduces the functionality, in the sense that a super mod cannot warn a moderator, but it also simplifies things, which in your case is something you would like. Correction: This solves your Warn sign issue. But it does not solve the hack's operation issues. There are more places where you have to do the same changes, like for example, when the "Warn XYZ" and "View XYZ's Warnings". The code there also uses the group information to decide if the links should be visible or not. Also, in the place where the warning points and the number of bans is shown. It's none of my business of course, but why are you using two groups for each role? Rgds Rgds |
Quote:
Just throwing the few cents I got about this out there :) |
Quote:
I was going to say I noticed that the Warnings by Warners Statistic doesn't list anyone in the other three usergroups. If you get a chance, and have the time, I'd appreciate it if you could note where else I will need to make changes. I first tried adding an "OR" to each one, followed by it's counterpart, but that made it possible for all the staff to warn in every forum, and allowed the members to see the links. The way it is now, every staff member can see the WARN image, and the view links, but only the super mod, admin, and the specific mod for that forum can see and use the warn links. It may not be right, but so far, I absolutely love it. It took me a couple hours to install it, but I haven't received a single error message yet, and for me, that's an accomplishment worth celebrating. :) The two Admin usergroups are for webmaster and admin, which have slightly different abilities, but are still both admin. The rest of the usergroups were doubled a couple years ago when we decided to create a second usergroup for sponsoring members, sponsoring moderators, and sponsoring super mods, and everything has just been built around that ever since. I'm sure there was/is an easier method, but I'm a mechanic, not a coder, and this stuff is as foreign to me as cooking. lol. |
All times are GMT. The time now is 08:21 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|