vb.org Archive
Page 10 of 11 « First 89 10 11
Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)
-   -   vBulletin Project Tools - vBulletin Project Tools Open Source 2.2.2 (https://vborg.vbsupport.ru/showthread.php?t=270346)

rbc 06-02-2017 02:10 PM
Quote:
Originally Posted by Dave (Post 2587182)
I'm pretty sure this project/plugin is dead and no longer developed/supported.
Dave

That's how it looks :(

best regards

Paul M 06-02-2017 05:38 PM
Quote:
Originally Posted by Dave (Post 2587182)
I'm pretty sure this project/plugin is dead and no longer developed/supported.
Actually, i noticed Yves did some work in svn the other day.

In Omnibus 06-02-2017 10:21 PM
Quote:
Originally Posted by rbc (Post 2587176)
Tried to install this version of Project Tools on vBulletin 4.2.5.
Installation not possible - no way.

Attachment 156442

No error message ....... just the progressbar for ever :confused:

Someone an idea?
I have this up and running on a 4.2.5 installation. There must be some other issue.

rbc 06-03-2017 08:05 AM
Quote:
Originally Posted by In Omnibus (Post 2587221)
I have this up and running on a 4.2.5 installation. There must be some other issue.
@In Omnibus

i have a fresh (clean) install of vB 4.2.5 (testboard)
When i try to install PT v. 2.2.2 nothing happens. Just progress bar as pointed above.

my live board works very well with vB4.2.4 and PT 2.2.2 and i am sure i can
update my board to vB4.2.5 and it would still work.

hope you know what i mean. (english -> not my language) ;)

best regards

In Omnibus 06-03-2017 11:18 AM
Quote:
Originally Posted by rbc (Post 2587233)
@In Omnibus

i have a fresh (clean) install of vB 4.2.5 (testboard)
When i try to install PT v. 2.2.2 nothing happens. Just progress bar as pointed above.

my live board works very well with vB4.2.4 and PT 2.2.2 and i am sure i can
update my board to vB4.2.5 and it would still work.

hope you know what i mean. (english -> not my language) ;)

best regards
Without much information I suspect it may be a PHP issue.

Which PHP version is your 4.2.5 installation using?

rbc 06-03-2017 01:09 PM
Quote:
Originally Posted by In Omnibus (Post 2587237)
Without much information I suspect it may be a PHP issue.
Which PHP version is your 4.2.5 installation using?
@In Omnibus

I use PHP Version 5.6.24-pl0-gentoo, exactly the same as on my live board.
-----

What i did today ! :
I did a fresh installation of vBulletin 4.2.4
Then the installation of vB Project Tools v. 2.2.2 works just fine.

Then i did an upgrade to vBulletin 4.2.5 - PT still there and visible.

try to add a new issue, results in a white page.

i did a new import of the product PT xml.

still the same -> white page.

(Its no problem to me, because this is only on a test site)
PT 2-2-2 works just fine on my live Board with vBulletin 4.2.4!

best regards

In Omnibus 06-03-2017 01:19 PM
Quote:
Originally Posted by rbc (Post 2587240)
@In Omnibus

I use PHP Version 5.6.24-pl0-gentoo, exactly the same as on my live board.
-----

What i did today ! :
I did a fresh installation of vBulletin 4.2.4
Then the installation of vB Project Tools v. 2.2.2 works just fine.

Then i did an upgrade to vBulletin 4.2.5 - PT still there and visible.

try to add a new issue, results in a white page.

i did a new import of the product PT xml.

still the same -> white page.

(Its no problem to me, because this is only on a test site)
PT 2-2-2 works just fine on my live Board with vBulletin 4.2.4!

best regards
Odd. That's the same PHP version I'm using on my test site. I'm trying to think of what else might be causing the issue but my knowledge of the changes between 4.2.4 and 4.2.5 as it relates to project tools specifically is limited to say the least. If I get some free time later I'll test this in debug mode on a clean installation.

Dave 06-03-2017 01:30 PM
Are there any errors in the error logs of Apache/PHP?

rbc 06-03-2017 09:41 PM
Quote:
Originally Posted by Dave (Post 2587242)
Are there any errors in the error logs of Apache/PHP?
@Dave

[04-Jun-2017 00:33:57 Europe/Zurich] PHP Fatal error: Call to undefined method vB_DataManager::vB_DataManager() in /home/xxxx/xxxx/vbtest/includes/class_dm_pt_project.php on line 89

PHP Code:
87       function vB_DataManager_Pt_Project(&$registry, $errtype = ERRTYPE_STANDARD)
88     {
89        parent::vB_DataManager($registry, $errtype); 
[04-Jun-2017 00:42:37 Europe/Zurich] PHP Fatal error: Call to undefined method vB_DataManager::vB_DataManager() in /home/xxxx/xxxx/vbtest/includes/class_dm_pt_projectgroup.php on line 77

PHP Code:
75    function vB_DataManager_Pt_ProjectGroup(&$registry, $errtype = ERRTYPE_STANDARD)
76    {
77        parent::vB_DataManager($registry, $errtype); 


best regards

Dave 06-03-2017 10:03 PM
Yea, it seems that it will not work properly with the latest vBulletin version that supports PHP 7.
It should work if you change all instances of
PHP Code:
parent::vB_DataManager($registry, $errtype); 
to
PHP Code:
parent::__construct($registry, $errtype); 
And the function which contains that call should be changed to __construct since a class can not have a function that has the same name as the class. (For example change function vB_DataManager_Pt_Project to function __construct

I took a quick look and it seems that a bunch of files do this so you might have to apply these changes to multiple files.

rbc 06-04-2017 07:57 AM
Quote:
Originally Posted by Dave (Post 2587256)
Yea, it seems that it will not work properly with the latest vBulletin version that supports PHP 7.
It should work if you change all instances of
PHP Code:
parent::vB_DataManager($registry, $errtype); 
to
PHP Code:
parent::__construct($registry, $errtype); 
And the function which contains that call should be changed to __construct since a class can not have a function that has the same name as the class. (For example change function vB_DataManager_Pt_Project to function __construct

I took a quick look and it seems that a bunch of files do this so you might have to apply these changes to multiple files.
@Dave ;)

Thank you for pointing this out. :up:
I will try to change these functions - and then try a new installation.

I took a look too and compared some new files from vB 4-2-5 with 4-2-4 and it`s
exactly how you wrote.

best regards

rbc 06-04-2017 12:16 PM
Some good and some bad news ...........

After updating this files :

class_dm_attachment.php (Z. 82)
class_dm_pt_issue.php (Z. 138)
class_dm_pt_issueassign.php (Z. 77)
class_dm_pt_issuechange.php (Z. 83)
class_dm_pt_issuenote.php (Z. 91/708/824/911)
class_dm_pt_issuepetition.php (Z. 79)
class_dm_pt_issuereport.php (Z. 85)
class_dm_pt_issuestatus.php (Z. 84)
class_dm_pt_issuesubscribe.php (Z. 75)
class_dm_pt_issuetype.php (Z. 104)
class_dm_pt_issuevote.php (Z. 78)
class_dm_pt_magicselect.php (Z. 71/232)
class_dm_pt_milestone.php (Z. 94)
class_dm_pt_project.php (Z. 87)
class_dm_pt_projectgroup.php (Z. 75/820)

the install script works perfect :)

All database entries, the sample project group and an example project Is created.
Everything is as good as it should be ..... but

If you want to make a new issue click on submit, a white page appears. You go back to project main page and the just created issue is listed in timeline and wherever. When you click on them -> white page.

Php.log:
[04-Jun-2017 15:14:16 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_projecttools.php on line 428
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1403
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1409
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Declaration of vB_DataManager_Pt_IssueNote::verify_ipaddress() should be compatible with vB_DataManager::verify_ipaddress($ipaddress) in /home/xxxx/vbtest/includes/class_dm_pt_issuenote.php on line 0
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1572
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1403
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1409
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_DataManager_Pt_IssueNote::verify_ipaddress() should be compatible with vB_DataManager::verify_ipaddress($ipaddress) in /home/xxxx/vbtest/includes/class_dm_pt_issuenote.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1572
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Fatal error: Unhandled BB Code Call : vB_BbCodeParser in /home/xxxx/vbtest/includes/class_bbcode.php on line 221

A coder will quickly recognize where the problem lies. I'm not a coder :confused:

best regards ...

Dave 06-04-2017 01:18 PM
Every
PHP Code:
=& datamanager_init 
has to be changed to
PHP Code:
= datamanager_init 
in all files.

--

In /includes/class_dm_pt_issuenote.php
PHP Code:
function verify_ipaddress(&$ipaddress) 
Remove the ampersand.

--

In /packages/vbproejcttools/attach/issue.php
PHP Code:
public function pre_delete($list) 
to
PHP Code:
public function pre_delete($list, $checkperms = true) 
--

I'm not sure about the fatal error though, it's not clear to me where it's called from.

rbc 06-04-2017 01:32 PM
Thank you @Dave :)

I will check and fix this - I come back with feedback!

best regards

rbc 06-04-2017 03:42 PM
@ Dave

I changed the files:
/vbhome/
projectajax.php (c 100/202/363/374)
projectpost.php (c 406/704/757/1407/1414/1578/2697/2714/3103/3296/3353/3438/3973/4554)
projectsearch.php (c 791/928/961/)
/vbhome/includes/
adminfunctions_projecttools.php (c 428/459/
class_dm_pt_issue.php (c 570/587/645/670/680/907/995/1408)
class_dm_pt_issueassign.php (c 139/183/)
class_dm_pt_issuechange.php (c 167/247)
class_dm_pt_issuenote.php (c 389/403/503/517/568/582/619/696)
class_dm_pt_issuepetition.php (c 158/187)
class_dm_pt_issuemagicselect.php (c 299)
--
/vbhome/includes/class_dm_pt_issuenote.php (117)
/vbhome/packages/vbprojecttools/attach/issue.php (520)
--

I uninstalled vb PT. AdminCP remove plugins.
Installed it new - > no problems.
install script :up:
create issue -> :down: white page. :mad:

Of course i uploaded all the altered files ....

php.log:

[04-Jun-2017 18:16:25 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:16:45 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:38:44 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:39:01 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue::pre_delete( ) should be compatible with vB_Attachment_Dm::pre_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:52:45 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/projectcounters.php on line 153
[04-Jun-2017 18:53:04 Europe/Zurich] PHP Strict Standards: mktime(): You should be using the time() function instead in /home_p2/c/o/compusoft.li/htdocs/includes/class_core.php(4735) : eval()'d code on line 2
[04-Jun-2017 18:53:15 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 18:53:15 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507

[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 568

[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 633
[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 683

[04-Jun-2017 19:14:30 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/project.php on line 957
[04-Jun-2017 19:14:52 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/project.php on line 647
[04-Jun-2017 19:17:08 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 19:17:08 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507

@Dave
feel free to abort your kind advice at any time ... :)

best regards

rbc 06-04-2017 06:19 PM
@ Dave

GOT IT !! :)

In class_bbcode_pt.php i changed :
PHP Code:
parent::vB_BbCodeParser($registry, $tag_list, $append_custom_tags); 
to : (it is crazy i know, but it works ...)
PHP Code:
parent::__construct($registry, $tag_list, $append_custom_tags); 
and now eveything works perfect. Without your valuable tips I would never have done that.

Thank you very much again and have a nice evening.

best regards ;)

Dave 06-04-2017 06:58 PM
Ah that explains, I thought you already fixed that. Glad it's working now. :)

rbc 06-05-2017 11:48 AM
Quote:
And the function which contains that call should be changed to __construct
It should work if you change "all" instances of ......
@ Dave

At first i thought only this function must be exchanged "vB_DataManager".
I was wrong.

best regards :)

Hostboard 07-03-2017 12:05 PM
Quote:
Originally Posted by Paul M (Post 2587211)
Actually, i noticed Yves did some work in svn the other day.

Is there anyway to access the SVN? I have tried from http://svn.vbulletin.org/svn/project_tools as noted on
https://www.vb-os.com/ but all I ever get is a white blank page...


Anyone interested in uploading the changed files and save me some work form having to edit all of them :p

Dave 07-03-2017 12:09 PM
Quote:
Originally Posted by Hostboard (Post 2588090)
Is there anyway to access the SVN? I have tried from http://svn.vbulletin.org/svn/project_tools as noted on
https://www.vb-os.com/ but all I ever get is a white blank page...


Anyone interested in uploading the changed files and save me some work form having to edit all of them :p
Yes, use a SVN client. :) If you look at the source code of the SVN pages you will see XML which a SVN client can parse properly.

Hostboard 07-03-2017 01:16 PM
Thank you. Never played with SVN or knew I needed a client.


For those interested, installed Tortoise SVN from here: https://tortoisesvn.net/
Then in their browser used URL: http://svn.vbulletin.org/svn/project_tools


Current build is 2.3.1

Phillip 08-20-2017 05:21 PM
Still can't get this to work with 4.2.5 at all. When going to installing the xml to the admincp...it just comes up blink.

Hostboard 08-21-2017 01:21 PM
Quote:
Originally Posted by Phillip (Post 2589485)
Still can't get this to work with 4.2.5 at all. When going to installing the xml to the admincp...it just comes up blink.




Which version of PT are you attempting to use?

Phillip 08-21-2017 08:35 PM
The Minified one...which already tried the other one before that and still nothing after trying minified.

Hostboard 08-21-2017 10:17 PM
Quote:
Originally Posted by Phillip (Post 2589508)
The Minified one...which already tried the other one before that and still nothing after trying minified.

You should download/install Project Tools Version 2.3.1 from the repository. I have it running of VB 4.2.5 with no issues.

Phillip 08-27-2017 07:35 PM
Quote:
Originally Posted by Hostboard (Post 2589511)
You should download/install Project Tools Version 2.3.1 from the repository. I have it running of VB 4.2.5 with no issues.
Where is the repository?

Hostboard 08-27-2017 08:52 PM
Quote:
Originally Posted by Phillip (Post 2589608)
Where is the repository?
https://www.vb-os.com/content/123-Download??

Phillip 08-27-2017 09:49 PM
Still nothing on that...same thing. :(

Hostboard 08-28-2017 12:03 AM
Did you you instal Tortoise SVN from here: https://tortoisesvn.net/ as I noted in post #381

Phillip 08-28-2017 12:19 AM
Yes, still the same result.

rbc 08-28-2017 12:47 PM
Quote:
Originally Posted by Phillip (Post 2589613)
Yes, still the same result.
I would rename all the old files of the PT on the server.
Upload the complete package again - Be sure it is the latest version 2.3.1

Try again the installation / update

Phillip 09-04-2017 04:10 PM
Finally got it to work after imported it on my server instead of the "EITHER upload the XML file from your computer".

rbc 09-04-2017 06:08 PM
Quote:
Originally Posted by Phillip (Post 2589738)
Finally got it to work after imported it on my server instead of the "EITHER upload the XML file from your computer".
Thats Great !! :up:

Best regards!

barnsi 09-29-2017 10:03 AM
Hello friends!
We have ProjectTools2.3.1 running well on vB4.5 with PHP7.1.9 and MariaDB10.1.26 installed.

But there are two fatal problems:

1. when trying to import a thread (Example: projectpost.php?do=importcontent&p=12392&type=post ) an error occurs:
PHP Code:
(PHP Warning): array_keys() expects parameter 1 to be array, null given in ....\projectpost.php (Zeile 4989) 
2. when clicking on a projecttype (Example: issuelist.php?projectid=1&issuetypeid=SFMInfo) an error occurs:


PHP Code:
[] operator not supported for strings on line 448 in ..\issuelist.php
#0 {main}
(Fatal User Error): [] operator not supported for strings on line 448 in ....\issuelist.php in ....\vb\vb.php (Zeile 286)
Trace Data:
#1 : vbstop() called in ....\includes\class_core.php on line 6090
#2 : vbulletin_error_handler() called in  on line 
#3 : trigger_error() called in ....\vb\vb.php on line 286
#4 : vB::handleException() called in  on line 

Var Type:
[ NULL ]

Var Data:
null 
I have seen that it works very well here: https://www.vb-os.com/project/2-Project-Tools with vB4.5Beta3.
Is there a way to fix this?

PitchouneN64ngc 09-29-2017 02:47 PM
Those errors are related to PHP 7, vb-os.com is still running on PHP 5.6.

Fixes will come quickly :)

PitchouneN64ngc 09-29-2017 02:54 PM
As another note, Im not sure why 2.3.1 was defined in development code, reverted to 2.3.0. You can edit the installed product file to change it from 2.3.1 to 2.3.0 or updating it won't execute added code for 2.3.0 & 2.3.1 in the future.

PitchouneN64ngc 09-29-2017 04:21 PM
After further research, those errors are not related to PHP 7. They are fixed locally, will commit them :)

WindVoice 09-29-2017 07:09 PM
Can't find the latest version 2.3.1 at https://www.vb-os.com/content/123-Download

Where to get it from?

Thanks!

PitchouneN64ngc 09-30-2017 12:09 PM
1/ It's not 2.3.1 but 2.3.0, there were an error versioning.
2/ Follow instructions on the page, it's on development.

barnsi 10-04-2017 02:05 AM
1 Attachment(s)
Hey! :)
...yes, installed it from SVN (29.09.2017 at Revision #904)


All times are GMT. The time now is 10:34 PM.
Page 10 of 11 « First 89 10 11
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.02098 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
  • (15)bbcode_php_printable
  • (18)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (3)pagenav_pagelink
  • (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