vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.0 Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=33)
-   -   Advanced Warning System (AWS) (https://vborg.vbsupport.ru/showthread.php?t=71992)

mcyates 12-12-2004 01:18 PM

where is ther updated file????

sv1cec 12-12-2004 01:32 PM

Quote:

Originally Posted by mcyates
where is ther updated file????

In the zip, you will find all updated files and instructions on how to update.

Rgds

mcyates 12-12-2004 01:37 PM

there is usually something there like a zup file but you only have

Download
Features.txt
Versions.txt

and no zip file

sv1cec 12-12-2004 01:43 PM

Quote:

Originally Posted by mcyates
there is usually something there like a zup file but you only have

Download
Features.txt
Versions.txt

and no zip file

OOOOOOOOOOOpppppppsssssssss, OK, here it is.

Shack Networks 12-12-2004 01:44 PM

OK I have been thinking and had another idea lol

Would it not be able to be adapted to detect duplicate posts and possibly add a warning point to the offending member ?

Just a little idea to keep you busy over xmas lol

Thanks a lot for this hack, I can not start to express my gratitude enough.

H

mcyates 12-12-2004 02:13 PM

sorry but got a warning:

SQL-query:

ALTER TABLE `warnings` ADD COLUMN `caused_ban` char( 1 ) AFTER warned_warning_id UPDATE `"warning_options` SET version = '2.3.1' WHERE oid =1
MySQL said:

#1064 - 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 'UPDATE `"warning_options` SET version='2.3.1' WHERE oid=1' at l

mcyates 12-12-2004 02:15 PM

ahh i left the " in oops sorry


The first quiery worked, the second didn't

Code:

SQL-query:

UPDATE `warning_options` SET version = '2.3.1' WHERE oid =1
MySQL said: 

#1054 - Unknown column 'version' in 'field list'


Delphiprogrammi 12-12-2004 02:52 PM

the query in the lated version upgrade instruction doesn't work for me

Code:

ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN `caused_ban` char(1) AFTER warned_warning_id
UPDATE `".TABLE_PREFIX."warning_options` SET version='2.3.1' WHERE oid=1

reply from the MySQL server

Code:

An error occurred while attempting to execute your query. The following information was returned.
error number: 1103
error desc: Incorrect table name '".TABLE_PREFIX."warnings'

sql querries aren't my strongest point ...

Bolas 12-12-2004 03:46 PM

Quote:

Originally Posted by sv1cec
It's not very difficult to do what you want, AWS is not very far from what you are asking, the main differences are:

- everybody can vote against everybody. This can be considered the same as everybody being capable of issuing warnings.
- in which case, obviously the warning points required for a ban should be much higher.

So, in reality, with some changes at who can vote (warn), some adjustements of the existing parameters and some additional parameters (like for example how many times a member can warn another member), a system like the one you describe is possible.

Or, you can add another level above the whole hack, where users are really voting for a particular warning which the admins have decided to issue against a particular member, and the results of these votes decide if the warning is issued or not. This is getting too "democratic" for my taste, and too much democracy easily leads to anarchy.

I am not sure if the above make sense, too late in the evening and too many things in my mind, so sorry if they sound like a drunk man's words (I swear, no drinks).

Rgds


The idea is the following: anybody can vote the ban proposal and once the quorum has been reached, the ban proposal is sent to the moderator of such forum. This way, the users of a forum can bring up the need for a change towards that person but only one of the moderators can approve it (or an administrator)

Is this true Democracy or a way to prevent unwanted people? :devious:

mcyates 12-12-2004 03:57 PM

Quote:

Originally Posted by Delphiprogrammi
the query in the lated version upgrade instruction doesn't work for me

Code:

ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN `caused_ban` char(1) AFTER warned_warning_id
UPDATE `".TABLE_PREFIX."warning_options` SET version='2.3.1' WHERE oid=1

reply from the MySQL server

Code:

An error occurred while attempting to execute your query. The following information was returned.
error number: 1103
error desc: Incorrect table name '".TABLE_PREFIX."warnings'

sql querries aren't my strongest point ...

I got the first quiery working:

Code:

ALTER TABLE `warnings` ADD COLUMN `caused_ban` char(1) AFTER warned_warning_id
by removing the botton query and removing the ".TABLE_PREFIX." which was infront og the warnings.


All times are GMT. The time now is 08:48 PM.

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.04847 seconds
  • Memory Usage 1,745KB
  • 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
  • (6)bbcode_code_printable
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (3)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