vb.org Archive
Page 47 of 57 « First 374546 47 4849 Last »
Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.0 Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=33)
-   -   Warning Hack V1.5 (https://vborg.vbsupport.ru/showthread.php?t=65336)

sv1cec 11-08-2004 08:05 AM
Quote:
Originally Posted by Blam Forumz
Is it possible to make it so I can set out a system like this :

5 - Warnings = 3 day ban.

After those 3 days are up, then another 5 warnings = 10day ban



Thanks

/Blam
Well, not exactly, but you can make it so that

5 - Warnings = 3 day ban.
5 more Warnings = 6 day ban.

I could make the multiplication factor a parameter in warning_options, but it will have to be a multiple of the original ban days parameter.

etc.

sv1cec 11-08-2004 08:08 AM
Quote:
Originally Posted by Blam Forumz
How can I stop my Super Mods warning my Admins?
Use the protected groups field. I assume that your admins/mods/supermods should all be there, so that they can't warn each other. As I said before, I do not use Super Mods, so the full hierarchical scale is not implemented.

Rgds

beano33 11-08-2004 03:35 PM
Here's a tip for those who use Super Moderators. The conditionals in the hack are written for Moderators as the primary usergroup. If you don't want to edit that, you can make everything work fine by changing usergroup settings.

For Super Moderators use the settings:
Primary Usergroup: Moderators
Display Usergroup: Super Moderators
Additional Usergroups: Super Moderators

As long as the primarary usergroup is moderators, everything in the hack works fine. Your Super Moderators will still be displayed as Super Moderators and have Super Moderator permissions doing it this way.

sv1cec 11-08-2004 03:43 PM
Quote:
Originally Posted by beano33
Here's a tip for those who use Super Moderators. The conditionals in the hack are written for Moderators as the primary usergroup. If you don't want to edit that, you can make everything work fine by changing usergroup settings.

For Super Moderators use the settings:
Primary Usergroup: Moderators
Display Usergroup: Super Moderators
Additional Usergroups: Super Moderators

As long as the primarary usergroup is moderators, everything in the hack works fine. Your Super Moderators will still be displayed as Super Moderators and have Super Moderator permissions doing it this way.
Yeah, that's a good idea. But would they be able to warn moderators and not be warned by them? I guess not, since the protected groups are all treated the same.

Oh well, if I find the time, some day, perhaps. But I guess if this is added, then I'll have to spend some time coming up with proper documentation of changes, compared to the standard release, and maybe release the whole thing as a new hack, with thanks to the original author, Zero Tolerance, of course.

Rgds
-----------
John

beano33 11-08-2004 04:34 PM
Quote:
Originally Posted by sv1cec
Yeah, that's a good idea. But would they be able to warn moderators and not be warned by them? I guess not, since the protected groups are all treated the same.
I tested that out. It works fine this way regarding protected usergroups. The problem I was having was that only mods and admins could view warnings anywhere, and I really didn't feel like going through the whole thing again to fix the conditionals for supermods. Since I only have a handful of supermods, this was an easy way to handle it.

Quote:
Oh well, if I find the time, some day, perhaps. But I guess if this is added, then I'll have to spend some time coming up with proper documentation of changes, compared to the standard release, and maybe release the whole thing as a new hack, with thanks to the original author, Zero Tolerance, of course.
You might want to inquire about vBulletin's plans to release their next version so you don't end up doing a lot of work that may have to be modified. For all we know the next version may include a warning system. :D

sv1cec 11-08-2004 04:46 PM
Quote:
Originally Posted by beano33
I tested that out. It works fine this way regarding protected usergroups. The problem I was having was that only mods and admins could view warnings anywhere, and I really didn't feel like going through the whole thing again to fix the conditionals for supermods. Since I only have a handful of supermods, this was an easy way to handle it.



You might want to inquire about vBulletin's plans to release their next version so you don't end up doing a lot of work that may have to be modified. For all we know the next version may include a warning system. :D
This whole issue of updates is really making me nervous. I am still at release 3.01, because I have made so many mods to my files/templates etc. that I do not dare to upgrade, I would hate to go through the same process again. Is there a list of files which shows which have changed between 3.01 and 3.03? Just thinking that this can occur every six months, when vB is releasing a new release, makes me crazy. I think I'll stick with 3.01, until something major is done.

As for your suggestion for the supermods, it is indeed very nice.

Rgds

beano33 11-08-2004 06:08 PM
Quote:
Originally Posted by sv1cec
This whole issue of updates is really making me nervous. I am still at release 3.01, because I have made so many mods to my files/templates etc. that I do not dare to upgrade, I would hate to go through the same process again. Is there a list of files which shows which have changed between 3.01 and 3.03? Just thinking that this can occur every six months, when vB is releasing a new release, makes me crazy. I think I'll stick with 3.01, until something major is done.

I asked one of the vB people this in mid-September before I upgraded from 3.0.1 to 3.0.3 and was told it would be at least a few months before the next version and that I should update then unless I have a lot of custom programming in PHP. There's a list of file changes in the announcements forum at vbulletin.com. I was able to upgrade with only one major problem due to a search hack that we installed that modified search.php. vB changed it's search so if you have any search hacks installed, it's liable to conflict, so it's best to remove it before you start. The other issues just involved redoing the templates we had modified (postibit legacy, navbar, and a few I can't remember). It was simply a matter of saving the templates we had modded as text files and pasting them back in. They all worked fine with the upgrade. Custom templates and custom php files weren't affected.

rex_b 11-08-2004 11:05 PM
Quote:
Originally Posted by sv1cec
As I said before, I liked the idea of a covered warner, so I did some changes in the database and the files/templates to make it a "consistent" feature of the hack. A text file is attached here, with the required modifications.

I hope you enjoy it.

While doing this, I also discovered a strange behaviour, in the Warning Options section of AdminCP. So, I changed the code a bit to correct it. The changes you should do, are described in the second attached file. All those who have implemented my "Allow multiple warnings for the same post?" option and the "Send PM to the warned member?" option, should do these changes, or else these features will not function properly.

Sorry for any inconvenience.

Finally, since the Warning Options part of AdminCP is getting a bit large as it is (it shows both the warning options, the defined offenses and allows you to add a new offence), I decided to separate them a bit, in order to make things more manageable. A third file is attached, which explains how to separate the Warning Options from the Warning Types.

I hope you enjoy.

Rgds
-----------
John

my templates look nothing like you ones you posted :(

sv1cec 11-09-2004 04:00 AM
Quote:
Originally Posted by rex_b
my templates look nothing like you ones you posted :(
What version are you running? This whole thing is based on 3.01, but should work on later releases.

Rgds

rex_b 11-09-2004 01:52 PM
Quote:
Originally Posted by sv1cec
What version are you running? This whole thing is based on 3.01, but should work on later releases.

Rgds

I'm using zero tolerances version and I didn't know there was another version within this thread. that's the problem I have.


All times are GMT. The time now is 09:35 PM.
Page 47 of 57 « First 374546 47 4849 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01604 seconds
  • Memory Usage 1,757KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (10)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 
Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 
Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete