The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#1
|
||||
|
||||
![]() Quote:
PM's are a useful feature for occasional use. Using them for constant communication is not the best choice, that would be far better done via e-mail A mobile style would be nice, but you cannot just plug one in, many features here would break (we have 80+ customised templates). Upgrading is not just a case of uploading a few files and running the upgrader. Despite the fact we have also repeated this many times, I'll cover it again. Any upgrade is a huge effort - even going from just 3.6 to 3.8 is major work - as above, we have 80+ template edits to check or redo (or modify). Over 120 plugins to check, rewrite (or remove in some cases). Things like thread prefixes are a custom mod in 3.6, but a standard feture in 3.8. All our custom javascript would all need redoing (3.8 uses YUI, 3.6 did not). All out custom functions (contained in a number of custom files) would need to be checked. Its a lot of work, so its not going to be done until there is a very good reason to do so. Despite what most people think, the thing most likely to drive an eventual upgrade is the servers we run on. vBulletin 3.6 does not play well with php5.3, even less so php5.4. Eventually we are going to have to do something to move off the old Jelsoft servers we use onto newer servers, and they wont be running php 5.2. |
![]() |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|