In my members warning section within there profile, the choose warning options is blank and none show up.

I have added warning to the system?

Any ideas?

Also.....

My postbit_legacy template is differant from the basic one, can someone help us put the correct code in this template please.

My Original Template:
Code Needed to be added:
Thanks.

Got me mixed up here. Warning Options in profile? Maybe you mean the links to warn xyz and to view xyz's warnings? Are you sure that you have set up your options properly? Are you and admin or a mod viewing the profile? If the answer is yes, check that you have made all the changes properly.

We cross-posted, please send me a larger part of your template, what you posted is not enough for me to help you.

Rgds


Rgds

Just installed this last night and I absolutely LOVE it!!! Instructions were excellent, and it installed without a single problem! Took me 2 hours to do it, lol, but it works perfect, I think...

The only issue I may have is that none of my moderators can see the WARN image. I can see it everytime I come across a post where the member was warned, but they can't see it at all, even posts they warned in their own forums.

Is this the way it's designed to work? If not, where should I look to correct this, and if it is designed that way, is there something I can do to enable the mods to see it?

Thanks!

*edit*
I'm running vB3.0.5, if it matters.

No, this is not the way it should work. Mods, supermods and admins should be able to see the Warn sign, that's the whole idea behind it. Actually, the management team has also the ability to click on the sign to see the warnings the post has received.

If the sign does not appear for your mods, while it appears for you (I assume you are the admin), check the postbit template (or postbit_legacy).

This is the code that you should have in postbit (assuming your mods, supermods and admins are usergroups 6,5 and 7):

Let me know if you got it.

Oh, next release the Warn Sign behaviour changes a bit. Again, the management team will be able to see the sign and click on it to see the warnings the post has received, but if the "Who can see the warning level and bans" is set to "All" then the rest of the gang can see the sign (i.e. they can tell the post was warned), but they can't view the warnings.

Rgds

I dont see any warn sign and Im admin?

Id this right?

Okay, that was my problem. Apparently it's not going to work properly because I have 6 usergroups between the mods, super mods, and admin. I'm guessing I should add the other three usergroups to each of the instances in postbit (actually legacy postbit) where that occurs?

Actually, now that I look at it, it may be a little more complicated than that. I've got everyone seeing the image now, but they don't all share the same abilities. My staff user groups are as follows: 6 & 13 are admins, 5 & 21 are super mods, and 7 & 20 are mods. With that in mind, what changes should I make to the legacy postbit?

*edit*
One more question; is this supposed to allow any moderator to issue a warning anywhere, or only in their own forums?

The whole hack is based on the standard usergroups of vB, that's 5, 6 and 7. Changing it to work with 6 usergroups instead of 3 is not going to be easy. Try to find instances where it refers to $bbuserinfo[usergoupid]==6 and add $bbuserinfo[usergoupid]==13, same thing for 5 and 21 and 7 and 20. I can't remember right now if that is all you have to edit though.

To answer your second question, the mods can warn only in the forums they can moderate.

That's pretty much what I figured, but my coding skills don't really exist, I'm an engine man. lol. What is the proper syntax for adding two user groups together like you are suggesting? I'm not asking for the whole code, but do I write "$bbuserinfo[usergoupid]==6, $bbuserinfo[usergoupid]==13" or "$bbuserinfo[usergoupid]==6 and $bbuserinfo[usergoupid]==13", etc. ? What's the proper way to write it out so that the browser recognizes those two go together?

Jeez, now I'm getting this when I try and warn someone from admincp

Database error in vBulletin 3.0.5:

Invalid SQL: insert into warnings values('','8449','1','1105418299','test','','1','N ','A','','')
mysql error: Column count doesn't match value count at row 1

mysql error number: 1136

Date: Monday 10th of January 2005 08:38:19 PM
Script: http://www.letsgokings.com/bbs/Warn.php
Referer: http://www.letsgokings.com/bbs/Warn....n=user&id=8449
Username: RinkRat
IP Address: 66.214.41.130

Strange, this error shows the proper columns OK. What is the description of your warnings table? Run this query and post your results here:

DESCRIBE warnings

Rgds

It depends on the statement. Most of the times, it should be OR, like :

should be converted to :

Rgds

Rinkrat,

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:

Exactly the same as yours. And at that part of the code, the hack is using Warn.php routines, which should be fine, since they work OK here, and I assume with others, because no one has complained about it.

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.



OK I just tried a warning from a thread and got this

I might have screwed up the edits (there were a lot) but I was really careful. Maybe I'll try it all over again.

OK, let's do this test. Open your includes/functions_warning.php file and find:

Replace that line with:

See if that works OK.

Rgds

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:

Just wish that this is the only place that you have to change the code for your situation. I just can't check where you need to make this change to make the hack safe for your condition.

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

That there looks like a missing addslashes()
Just throwing the few cents I got about this out there :)

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.

sv1cec,

i'm having a problem to upgrade to 3.0.8 with an SQL querry this sql querry

MySQL is giving me error 1064 and i tryed like 10 times (i do remove the TABLE_PREFIX part) but it doesn't help what the heck is this ?

regards

I am not sure, because this happened even when his text was just "test".

And the value of that variable is going through a function which is supposed to replace the '.

I am puzzled.

That's easy. Edit your admin_warn.php file and find:

Replace that with:

As for the other changes, what you should do, is make sure that wherever there is a reference to group 6, there is also a reference to the equivalent group. Typically, the two references should be OR-ed and even better put them in a parenthesis like ($bbuserinfo[usergroupidi]==6 OR $bbuserinfo[usergroupid]==13 ). Same with the rest.

Let me know how you are progressing.

Rgds

Remove the WHERE oid='1'. We are altering the table, not updating it.

Stupid me!!! I am going to correct that in the zip.

I couldn't find that exact line in a fresh upload of the file but found something very close and changed it. This is what I get now.

It appears as if all of the errors are listing the first value as being empty

values('','1742','1'

Is that right? I don't know php/mysql real well so I have no idea.

No, this is not your problem, this column is an auto-increment column, so you shouldn't enter a value.

Add the missing column by running this query:

ALTER TABLE `warning_options` ADD COLUMN `caused_ban` char(1) AFTER warned_warning_id

Then try again.

OK here I go.. It's weird because I ran the upgrade script adn even went back and ran the install script.

Here's the table:

Sorry, wrong input on my behalf. Here is the proper query:

ALTER TABLE `warnings` ADD COLUMN `caused_ban` char(1) AFTER warned_warning_id

Then use the modification I told you before in the functions_warning.php and try to issue a warning.

Hi,

I upgraded to 3.0.8 and have two questions.

1.

In the user section in the admincp I have now two different links with the same name and output. See attachment. Can I delete one or are they really different?

2.

I entered a lot of censored words but still the users don't get warned automatically when using them. sv1cec do you think you'll find time to take a look at this at my board next days?

Kind regards
jluerken

On issue 1, yes, the first line can be deleted. The code for the two buttons is the one I have in the UpgradeToLatestVersion.txt file.

On the second issue, in order for the automatic warnings to work you have to have defined:

- censored words
- set the automatic warnings for posts to 'yes'
- define an automatic warner
- define a warning type called 'ObsceneWords' and charaterize it as automatic

If one of them is not done, the warnings cannot be issued. If you have done all these and you still have problems, I can have a look at your site and try to figure out what's the problem.

Rgds

OK it looks like it worked!! Thanks so much for taking the time to see this through and for the prompt replies. This is part of what makes VB so cool is the great community. You rule!

Oh yeah, after I get the success message it gets forwarded to the wrong address

"The requested URL /admincp/user.php was not found on this server."

It's actually in /bbs/admincp/user.php Where can I fix this?

I did not had this in my installation.
I will add it an test this in the next days.

Thanks for the fast feedback.

One more question.

I have only one cron called: delete_old_warnings in my sheduled task folder but in the cron folder of 3.0.8 there are two files called kill_bans.php and kill.warns.php.

Do I have forgotten to add a second sheduled job?

Yes, the kill_bans is used to kill bans which expire, from the user account. See the related Option, on Bans Maturity. If you do not plan to use that, no need to install it.

First of all, I do not remember what you are trying to do. Please remind me. I mean after all these posts, I do not remember what you were doing when you got the error, so let me know.

Also, what is your $vboptions[bburl] ?

When I am in Admincp and issue a warning I get the success message "You have issued a warning" or whatever, then I'm forwarded to /admincp/user.php instead of /bbs/admincp/user.php (the correct location of bbs root is /bbs/).

John,

I found a small typo in the instructions for 3.0.7 -> 3.0.8:

For the code after // ########################## REQUIRE BACK-END :

in this code:

There is an extra space between ".TABLE_PREFIX." and warning_options

Instead of ".TABLE_PREFIX." warning_options

Should be ".TABLE_PREFIX."warning_options

I was getting an error when trying to access my AdminCP before I fixed this.

edited to add:

Also, it is not saving my options when I click on "Update Warning Options"

:(

I had initially installed up to 3.0.3, so I ran the uninstaller script, uploaded the 3.0.8 files, then the 3.0.8 installer script, and then did the file edits for 3.0.3 -> 3.0.8. I figured that would be quicker/easier than all of the manual table/template edits. :D

I'm also getting "Warning: Division by zero in /admincpanel/admin_warn.php on line 672" when trying to view "Statistics - Warnings per user" via the admincp.

and "Warning: Division by zero in /admincpanel/admin_warn.php on line 1889"
when trying to view "Statistics - Bans per User" via the admincp

Rinkrat

OK, edit your Warn.php file and search for :

Replace that with:

rgds

Torqued,

Space thingy, you are right, some stupid editor must have brought that in, sorry I'll correct that.

Saving the warning options? Does it come up with any message? It's wierd, 'cause it works fine in both my test site and in the production one. Try downloading the zip again and upload the admin_warn.php to your server's admincp directory.

The two division by zero errors you get, are because the warning_options are not saved and the program tries to divide by the number of lines per page, the last field in the warning_options, which is zero, since the value you entered didn't get saved.

Try what I suggested and come back to me.

Rgds