The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
![]()
there may be people who like hacking more than editing templates
![]() also if he made some scriptspecific things in phpinclude it doesn't look that well |
#12
|
||||
|
||||
![]()
Heh heh,
Well, another reason it's so long is I LOVE whitespace and making the code both nice to look at as well as functioning. Many of the lines are simply { because I leave those to themselves. I also have a LOT of commentary text so that if anyone comes in after me they can see what it does. As an example, here's the first section... PHP Code:
The second item more cleanly allows the move thread presets. It's actually the 2nd version of a hack I've released and if you make a lot of thread moves it comes highly recommended. The rest of the script does these things (just copying the commentary text...) PHP Code:
|
#13
|
||||
|
||||
![]()
Looks intriguing.
![]() ![]() |
#14
|
||||
|
||||
![]() Quote:
|
#15
|
||||
|
||||
![]()
The Jelsoft support concern is definitely a valid one, but we have modified the code to allow forum banners. The changes are minor and can be undone in an hour or so if need be, but they are there.
I suppose I could require it in global.php, but I'm constantly upgrading the thing and as I said I don't have FTP access to the server, which I sorta would need to put it in an include file. |
#16
|
|||
|
|||
![]()
I never touch my include template. Everything is file modded for me. ^^
|
#17
|
||||
|
||||
![]()
i think the combination is best
phpinclude can be a strong way to make some changes, but there are things which shouldn't be in that template ![]() |
#18
|
||||
|
||||
![]()
perhaps we should make a list of when phpinclude is especially useful and when definitely not
![]() |
#19
|
|||
|
|||
![]()
Phpinclude should not be used for calling templates imho, seeing how you have to hack the files to get the new template in the cache list anyway. Query's are fine in phpinclude, it just boils down to what the query dose as with hacking.
We really need to do some testing with phpinclude to see how much of an impact it has on resources over placing code directly into the files. |
#20
|
|||
|
|||
![]()
Ok I re-applied some stock vB code for de-buging to the phpinclude_start template, try this little hacket out and see how much time/memory your phpinclude_start template is eating up.
In /forumroot/global.php find: PHP Code:
PHP Code:
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|