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)

sv1cec 01-04-2005 03:12 PM

Quote:

Originally Posted by T3MEDIA
Does beyond compare work?

Well, it depends on what you want from it. Yes it does, I checked all the new files vs the old ones and did the upgrades (changes which are done by the various hacks) in less than 2 hours.

Rgds

T3MEDIA 01-04-2005 04:17 PM

abit off topic but how much more modified is the new version?

sv1cec 01-04-2005 05:45 PM

Quote:

Originally Posted by T3MEDIA
abit off topic but how much more modified is the new version?

The new version (I assume version 3.0.3) compared to what?

If you are refering to the Zero Tolerance's hack, quite a bit more. Read the features list, and you'll understand.

If you want to find out what's the difference between the current release and some previous one, there is a file here, called Versions.txt. Read that file to see what's been added in each release.

Rgds

Guy G 01-04-2005 05:46 PM

uninstalled... sorry, i experienced a lot of database errors and such.
ill wait for an update if there gonna be one.
thx

sv1cec 01-04-2005 05:49 PM

Quote:

Originally Posted by Zorobz
uninstalled... sorry, i experienced a lot of database errors and such.
ill wait for an update if there gonna be one.
thx

No problem, but you do not tell me what the errors were, so I can't be either of help to you or release an update. The issue is that the install script has been tested yesterday on a clear vB 3.0.4 installation, and it worked like a charm.

As for the program, there has been only one or two bugs refered to me, and they've been corrected the same day. Can't be of more help without input from you.

Rgds

Rhoads 01-04-2005 06:28 PM

Thnx sv1cec

Installed on vb3.0.4 en there is no problem.
Thnx for the great Hack :up:

Delphiprogrammi 01-04-2005 06:54 PM

yes same here works fine with vb3.04

Rhoads 01-04-2005 07:11 PM

Oke, I have a little problem when I do the 3.0.2 to 3.0.3 update :

When I run the query:
UPDATE `".TABLE_PREFIX."warning_options` SET version='3.0.3' WHERE oid=1

It's say's :
fault
SQL-query :
UPDATE `".TABLE_PREFIX."warning_options` SETversion = '3.0.3' WHERE oid = 1
MySQL retourneerde:
Incorrect table name '".TABLE_PREFIX."warning_options'

Delphiprogrammi 01-04-2005 09:21 PM

hi,

drop the TABLE_PREFIX part and replace it with your "real" table name so if you have a database table name "vb_" the querry becomes

Code:

UPDATE vb_warning_options SET version='3.0.3' WHERE oid=1
seem you have a dutch MySQL ?

laat dat TABLE_PREFIX gedeelte weg en vervang het door je "tabel" naam dan gaat het werken

T3MEDIA 01-04-2005 10:03 PM

I have been getting error from the database but I assumed it was something else. What exactly was your errors? Please let me know

Rhoads 01-05-2005 12:39 AM

Quote:

Originally Posted by Delphiprogrammi
hi,

drop the TABLE_PREFIX part and replace it with your "real" table name so if you have a database table name "vb_" the querry becomes

Code:

UPDATE vb_warning_options SET version='3.0.3' WHERE oid=1
seem you have a dutch MySQL ?

laat dat TABLE_PREFIX gedeelte weg en vervang het door je "tabel" naam dan gaat het werken

Thnx Delphiprogrammi, that was the problem, and now it's updated ;)

Torqued 01-05-2005 01:40 AM

John,

Getting an error after upgrading from 3.0 to 3.0.3

Quote:

Database error in vBulletin 3.0.3:

Invalid SQL: update vb3warning_options set
hierarchical='Yes',
automatic='No',
automaticpm='No',
autocomments='Yes',
warner='0',
automatic_warner='0',
collector='1',
banned_limit='3',
points_before_banned='10',
banned_usergroup_id='8',
troll_usergroup_id='8',
protected_usergroups='6|6',
aprotected_usergroups='6',
restore_groupid='0',
incr_ban_days='No',
max_no_bans='3',
bans_mature='0',
viewoption='All',
multiple_per_post='Yes',
send_pm_warning='Yes',
send_em_warning='No',
email_on_ban='Yes',
historical='Yes',
allowoffpost='Yes',
warnings_per_page='15'
where oid='1'
mysql error: Unknown column 'collector' in 'field list'
Here is what is in my warning_options table:
Code:

          oid          int(15)                    No                      auto_increment
        version          varchar(10)                  Yes          NULL                   
        hierarchical          char(3)                  Yes          NULL                   
        automatic          char(3)                  Yes          NULL                   
        automaticpm          char(3)                  Yes          NULL                   
        autocomments          char(3)                  Yes          NULL                   
        automatic_warner          int(10)        UNSIGNED        Yes         
        warner          int(10)        UNSIGNED        Yes          NULL         
        collector          int(10)        UNSIGNED        Yes          NULL         
        banned_limit          int(15)                  No          0                   
        points_before_banned          int(15)                  No          0         
        banned_usergroup_id          int(15)                  Yes          0         
        protected_usergroups          varchar(50)                  Yes          NULL         
        aprotected_usergroups          varchar(50)                  Yes         
        troll_usergroup_id          varchar(10)                  Yes          NULL         
        restore_groupid          smallint(5)        UNSIGNED        Yes         
        incr_ban_days          char(3)                  Yes          NULL         
        max_no_bans          int(5)                  Yes          NULL                    Change
        bans_mature          int(10)                  Yes          NULL                   
        viewoption          char(3)                  Yes          NULL                   
        multiple_per_post          char(3)                  Yes          NULL         
        send_pm_warning          char(3)                  Yes          NULL         
        send_em_warning          char(3)                  Yes          NULL         
        email_on_ban          char(3)                  Yes          NULL                   
        historical          char(3)                  Yes          NULL                   
        allowoffpost          char(3)                  Yes          NULL                   
        warnings_per_page          int(3)                  Yes          NULL

I don't understand why it's saying the "collector" field isn't there..

sv1cec 01-05-2005 05:53 AM

Quote:

Originally Posted by Torqued
John,

Getting an error after upgrading from 3.0 to 3.0.3



Here is what is in my warning_options table:
Code:

          oid          int(15)                    No                      auto_increment
        version          varchar(10)                  Yes          NULL                   
        hierarchical          char(3)                  Yes          NULL                   
        automatic          char(3)                  Yes          NULL                   
        automaticpm          char(3)                  Yes          NULL                   
        autocomments          char(3)                  Yes          NULL                   
        automatic_warner          int(10)        UNSIGNED        Yes         
        warner          int(10)        UNSIGNED        Yes          NULL         
        collector          int(10)        UNSIGNED        Yes          NULL         
        banned_limit          int(15)                  No          0                   
        points_before_banned          int(15)                  No          0         
        banned_usergroup_id          int(15)                  Yes          0         
        protected_usergroups          varchar(50)                  Yes          NULL         
        aprotected_usergroups          varchar(50)                  Yes         
        troll_usergroup_id          varchar(10)                  Yes          NULL         
        restore_groupid          smallint(5)        UNSIGNED        Yes         
        incr_ban_days          char(3)                  Yes          NULL         
        max_no_bans          int(5)                  Yes          NULL                    Change
        bans_mature          int(10)                  Yes          NULL                   
        viewoption          char(3)                  Yes          NULL                   
        multiple_per_post          char(3)                  Yes          NULL         
        send_pm_warning          char(3)                  Yes          NULL         
        send_em_warning          char(3)                  Yes          NULL         
        email_on_ban          char(3)                  Yes          NULL                   
        historical          char(3)                  Yes          NULL                   
        allowoffpost          char(3)                  Yes          NULL                   
        warnings_per_page          int(3)                  Yes          NULL

I don't understand why it's saying the "collector" field isn't there..

That's strange. Where did you get the list of the columns? Did you do a "describe warning_options" or did you copy it from the hack instructions?

Rgds

sv1cec 01-05-2005 05:56 AM

Quote:

Originally Posted by T3MEDIA
I have been getting error from the database but I assumed it was something else. What exactly was your errors? Please let me know

T3Media, what errors are you getting?

sv1cec 01-05-2005 06:09 AM

Version 3.0.4 has been released. It allows you to warn a user directly from your AdminCP, or to be more precise, from the User Manager section of AdminCP. Obviously, only non-post-related warnings can be issued from there.

I hope you enjoy.

Vixion 01-05-2005 08:54 AM

I have version 2.3.5 but I don't understand how to update it from version 2.3.5 tot 3.0.4.

Do I need to update from 2.3.5 tot 3.0 and then 3.0 tot 3.0.4?

sv1cec 01-05-2005 09:42 AM

Quote:

Originally Posted by Vixion
I have version 2.3.5 but I don't understand how to update it from version 2.3.5 tot 3.0.4.

Do I need to update from 2.3.5 tot 3.0 and then 3.0 tot 3.0.4?

You have to update from 2.3.5 to the next release. Then from that one to the next etc.

Torqued 01-05-2005 11:54 AM

Quote:

Originally Posted by sv1cec
That's strange. Where did you get the list of the columns? Did you do a "describe warning_options" or did you copy it from the hack instructions?

Rgds

I copied it from PHPMyAdmin. I had uninstalled a v 1.x (including removing the tables) and then successfully ran the 3.0 installer before this upgrade.

sv1cec 01-05-2005 12:34 PM

Quote:

Originally Posted by Torqued
I copied it from PHPMyAdmin. I had uninstalled a v 1.x (including removing the tables) and then successfully ran the 3.0 installer before this upgrade.

And what are you trying to do when you get that error message? Update the Warning Options? That's strange. I am not sure what to say. I assume you applied all changes from 3.0 to 3.0.1, to 3.0.2, to 3.0.3, right?

If this is a new installation, and you do not have any warnings you want to preserve, try running the uninstaller and then reinstall from scratch. It just does not make sense.

JayJay 01-05-2005 12:35 PM

Code:

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/-/public_html/forum/includes/init.php on line 522



 
Unable to add cookies, header already sent.
File: /home/-/public_html/forum/includes/init.php
Line: 522


Any idea what would be causing that error when loading 'mod_warn.php' in the modCP?

Torqued 01-05-2005 12:53 PM

Quote:

Originally Posted by sv1cec
And what are you trying to do when you get that error message? Update the Warning Options? That's strange. I am not sure what to say. I assume you applied all changes from 3.0 to 3.0.1, to 3.0.2, to 3.0.3, right?

If this is a new installation, and you do not have any warnings you want to preserve, try running the uninstaller and then reinstall from scratch. It just does not make sense.

Yes. I applied all the changes for 3.0 -> 3.0.3. I was trying to update the Warning Options. I'll try running the uninstaller and reinstall again.

edited to add:

Uninstalled and reinstalled.. updating options seems to work fine now. :ermm:

Since I had made the file edits up to 3.0.3, I just applied the file edits for 3.0.3 -> 3.0.4 and am seeing a couple of issues when trying to warn from the Admin CP:

1: When entering a specific userID to warn, it just takes me to the user list.

2: When selecting Warn User from their profile page, it just takes me to a blank screen.

sv1cec 01-05-2005 01:05 PM

Quote:

Originally Posted by Torqued
Yes. I applied all the changes for 3.0 -> 3.0.3. I was trying to update the Warning Options. I'll try running the uninstaller and reinstall again.

edited to add:

Uninstalled and reinstalled.. seems to be working fine now. :ermm:

OK, because if it didn't, I would have to crash my mind. It wasn't logical, was it?!!

Rgds

Torqued 01-05-2005 01:07 PM

Quote:

Originally Posted by sv1cec
OK, because if it didn't, I would have to crash my mind. It wasn't logical, was it?!!

Rgds

Looks like we were cross-posting. :)

Uninstalled and reinstalled.. updating options seems to work fine now.

Since I had made the file edits up to 3.0.3, I just applied the file edits for 3.0.3 -> 3.0.4 and am seeing a couple of issues when trying to warn from the Admin CP:

1: When entering a specific userID to warn, it just takes me to the user list.

2: When selecting Warn User from their profile page, it just takes me to a blank screen.

sv1cec 01-05-2005 01:08 PM

Quote:

Originally Posted by JayJ
Code:

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/-/public_html/forum/includes/init.php on line 522



 
Unable to add cookies, header already sent.
File: /home/-/public_html/forum/includes/init.php
Line: 522


Any idea what would be causing that error when loading 'mod_warn.php' in the modCP?

JayJ,

When does this happen? As soon as you log in the modcp? Or when you click on the link in the left frame, where it is supposed to say "View Issued Warnings"?

Also, which AWS version are you running?

Rgds

JayJay 01-05-2005 01:19 PM

When one clicks the 'View Issued Warnings' link in the left-hand panel. I downloaded my version of AWS around 3-4 hours ago, therefore it is fairly recent.

It's weird since I updated to 3.0.4 today, and that particular file has not been touched or edited.

JayJay 01-05-2005 01:26 PM

If it helps any, it refers to this section of the init.php file:

Code:

// add default special templates
                if (!CACHE_DATASTORE_FILE OR !defined('CACHE_DATASTORE_FILE'))
                {
                        $specialtemplates = array_merge(array(
                                'options',
                                'cron',
                                'forumcache',
                                'usergroupcache',
                                'stylecache'
                        ), $specialtemplates);
                }


sv1cec 01-05-2005 01:28 PM

Quote:

Originally Posted by JayJ
When one clicks the 'View Issued Warnings' link in the left-hand panel. I downloaded my version of AWS around 3-4 hours ago, therefore it is fairly recent.

It's weird since I updated to 3.0.4 today, and that particular file has not been touched or edited.

Does the report opens? If yes, does it have the sort buttons? Maybe it's an old version?

Give me a couple of minutes, I have found a small problem in that file, but it shouldn't be the one which is causing your problem.

I'll post here, when the new version is uploaded.

Rgds

Vixion 01-05-2005 01:28 PM

I am getting errors...

Code:

UPDATE `vb3_warning_options` SET version=\'3.0\' WHERE oid=1

MySQL retourneerde:

You have an error in your SQL syntax near '\'3.0\' WHERE oid=1' at line 1

and

Code:

CREATE TABLE `vb3_ban_dates` (
  `banned_serno` int(15) NOT NULL auto_increment,
  `banned_user` int(15) NOT NULL default \'0\',
  `banned_ban` int(2) default \'0\',
  `banned_warning` int(15) NOT NULL,
  `banned_by` int(15) NOT NULL default \'0\',
  `banned_dateline` int(15) NOT NULL default \'0\',
  `banned_status` char(1),
  `banned_reason` mediumtext,
  PRIMARY KEY  (`banned_serno`)
) TYPE=MyISAM

MySQL retourneerde:

You have an error in your SQL syntax near '\'0\',
  `banned_ban` int(2) default \'0\',
  `banned_warning` int(15) NOT NUL' at line 3

What can I do to solve this problem?

sv1cec 01-05-2005 02:12 PM

Quote:

Originally Posted by Vixion
I am getting errors...

Code:

UPDATE `vb3_warning_options` SET version=\'3.0\' WHERE oid=1

MySQL retourneerde:

You have an error in your SQL syntax near '\'3.0\' WHERE oid=1' at line 1

and

Code:

CREATE TABLE `vb3_ban_dates` (
  `banned_serno` int(15) NOT NULL auto_increment,
  `banned_user` int(15) NOT NULL default \'0\',
  `banned_ban` int(2) default \'0\',
  `banned_warning` int(15) NOT NULL,
  `banned_by` int(15) NOT NULL default \'0\',
  `banned_dateline` int(15) NOT NULL default \'0\',
  `banned_status` char(1),
  `banned_reason` mediumtext,
  PRIMARY KEY  (`banned_serno`)
) TYPE=MyISAM

MySQL retourneerde:

You have an error in your SQL syntax near '\'0\',
  `banned_ban` int(2) default \'0\',
  `banned_warning` int(15) NOT NUL' at line 3

What can I do to solve this problem?

Why are you adding backslashes?

It would also help if I knew the error number that the database returned.

sv1cec 01-05-2005 02:14 PM

Quote:

Originally Posted by JayJ
If it helps any, it refers to this section of the init.php file:

Code:

// add default special templates
                if (!CACHE_DATASTORE_FILE OR !defined('CACHE_DATASTORE_FILE'))
                {
                        $specialtemplates = array_merge(array(
                                'options',
                                'cron',
                                'forumcache',
                                'usergroupcache',
                                'stylecache'
                        ), $specialtemplates);
                }


JayJ, I am not using these templates at all.

Please download version 3.0.5 I just uploaded and check out the new mod_warn.php file. It should work the way you are, without doing any other changes. Of course, do make the other changes after you verify that everything is OK with your problem.

Rgds

JayJay 01-05-2005 02:20 PM

Thanks - I'll give that a try now and then tell you how I get on :)

sv1cec 01-05-2005 02:26 PM

Quote:

Originally Posted by Torqued
Looks like we were cross-posting. :)

Uninstalled and reinstalled.. updating options seems to work fine now.

Since I had made the file edits up to 3.0.3, I just applied the file edits for 3.0.3 -> 3.0.4 and am seeing a couple of issues when trying to warn from the Admin CP:

1: When entering a specific userID to warn, it just takes me to the user list.

2: When selecting Warn User from their profile page, it just takes me to a blank screen.

For the first, it's strange because I took the code directly from vB's admincp entry page and it works fine in my system. Anyone else is having this problem? If you go into the User Manager and you select Warn User from the Quick User Links, do you get the warn screen?

As for the second, check your warn_addwarn_nopost template, that's the one that is called from that point.

I'll look more into these two issues later tonight, my hands are kind of full right now.

Rgds

Rhoads 01-05-2005 02:47 PM

Quote:

Originally Posted by sv1cec
For the first, it's strange because I took the code directly from vB's admincp entry page and it works fine in my system. Anyone else is having this problem? If you go into the User Manager and you select Warn User from the Quick User Links, do you get the warn screen?

As for the second, check your warn_addwarn_nopost template, that's the one that is called from that point.

I'll look more into these two issues later tonight, my hands are kind of full right now.

Rgds

I have the same problem :

1: When entering a specific userID to warn, it just takes me to the user list.
2: When selecting Warn User from their profile page, it just takes me to a blank screen with "Internal Server Error" "The server encountered an internal error or misconfiguration and was unable to complete your request."

It was good, but after the 3.0.4 and 3.0.5 update it's wrong.

Torqued 01-05-2005 02:59 PM

Quote:

Originally Posted by sv1cec
For the first, it's strange because I took the code directly from vB's admincp entry page and it works fine in my system. Anyone else is having this problem? If you go into the User Manager and you select Warn User from the Quick User Links, do you get the warn screen?

As for the second, check your warn_addwarn_nopost template, that's the one that is called from that point.

I'll look more into these two issues later tonight, my hands are kind of full right now.

Rgds

I think I may be onto something:

My default style was a child style of the Default VB Style.

I switched my default style back to the parent Default VB Style and reinstalled. Now I get a 404 error when selecting the Warn User from the dropdown in the user profile.

Still getting just the user list when entering a userID. Searching by username now seems to be working.

I changed the following in admincp/user.php:

Code:

"/Warn.php?$session[sessionurl]do=WarnUserNoPost&id=$userid"
to:

Code:

"../Warn.php?$session[sessionurl]do=WarnUserNoPost&id=$userid"
Once I did that, I no longer get the 404, but instead get this:

Code:

An Error Has Occured!
An error has occured, the following message has been left below:

You may not issue warnings which are not related to a post

Edited to add: Ignore that last part right there.. when I reinstalled, I forgot I had to go back and change my warning options again. lol. sorry for being a retard! :nervous:

Still am getting only the whole userlist when I enter in a numeric userid via Warn User in the AdminCP

Viol8or 01-05-2005 04:17 PM

Another suggestion sv1cec:

Situation: a certain person has already got a few warnings. He makes a new posts that needs a warning to. ModA comes by, spots the post and gives warning. Few hours later ModB passes by, spots post. If it's smart moderator, he will first check the logs or warnings to see if this post was warned before. A lot of mods however will skip this step, and it's rather time consuming on bigger boards as well. Therefor it would be nice if the post that got the warning was marked in any way, or has a prevention from further warnings.
We had situations we users got 2 or 3 warnings for the same post.
Can be handy?

sv1cec 01-05-2005 06:17 PM

Quote:

Originally Posted by Torqued
I think I may be onto something:

My default style was a child style of the Default VB Style.

I switched my default style back to the parent Default VB Style and reinstalled. Now I get a 404 error when selecting the Warn User from the dropdown in the user profile.

Still getting just the user list when entering a userID. Searching by username now seems to be working.

I changed the following in admincp/user.php:

Code:

"/Warn.php?$session[sessionurl]do=WarnUserNoPost&id=$userid"
to:

Code:

"../Warn.php?$session[sessionurl]do=WarnUserNoPost&id=$userid"
Once I did that, I no longer get the 404, but instead get this:

Code:

An Error Has Occured!
An error has occured, the following message has been left below:

You may not issue warnings which are not related to a post

Edited to add: Ignore that last part right there.. when I reinstalled, I forgot I had to go back and change my warning options again. lol. sorry for being a retard! :nervous:

Still am getting only the whole userlist when I enter in a numeric userid via Warn User in the AdminCP

Folks,

I think that at some time, I installed a hack which allowed you to search by the User ID. I swear to God, it works fine with the code as it is in my site. I am trying to find out what else need to be changed, but I can't. I think it was a mini-mod that did that, but I can't find it at the moment.

I'll look at that and let you know as soon as possible.

As for the post being marked, this is an excellent idea, and I think it can be done.

Umtil later.

SamirDarji 01-05-2005 07:34 PM

Quote:

Originally Posted by Viol8or
Another suggestion sv1cec:

Situation: a certain person has already got a few warnings. He makes a new posts that needs a warning to. ModA comes by, spots the post and gives warning. Few hours later ModB passes by, spots post. If it's smart moderator, he will first check the logs or warnings to see if this post was warned before. A lot of mods however will skip this step, and it's rather time consuming on bigger boards as well. Therefor it would be nice if the post that got the warning was marked in any way, or has a prevention from further warnings.
We had situations we users got 2 or 3 warnings for the same post.
Can be handy?

I wouldn't think preventing a warning would be a solution, but what about changing the color or font (or both) of the "warn user" link in the post when there is already a warning for that post? This way, a mod will know there is already a warning on that post, but still has the option to warn again if it is warranted.

mojo8850 01-05-2005 09:22 PM

Thanks sv1cec..

Nice One Guys For Replying Appreciate It..!

Viol8or 01-06-2005 05:08 AM

Quote:

Originally Posted by SamirDarji
I wouldn't think preventing a warning would be a solution, but what about changing the color or font (or both) of the "warn user" link in the post when there is already a warning for that post? This way, a mod will know there is already a warning on that post, but still has the option to warn again if it is warranted.

This would indeed be an acceptable solution.

sv1cec 01-06-2005 05:43 AM

Good morning Gang,

Here is the answer to your problem. I knew it was not something difficult:

In your includes/adminfunctions_user.php find:

PHP Code:

$condition .= iif($user['email'], " AND email LIKE '%" addslashes_like($user['email']) . "%'"); 

Right above that, add:

PHP Code:

$condition .= iif($user['userid'], " AND user.userid = '" addslashes_like($user['userid']) . "'"); 

That should solve your search with User ID problem.

Let me go and update the installation instructions and all.

Rgds


All times are GMT. The time now is 01:18 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.01953 seconds
  • Memory Usage 1,911KB
  • 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
  • (18)bbcode_code_printable
  • (2)bbcode_php_printable
  • (23)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (2)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (40)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