The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#1
|
|||
|
|||
![]()
Yes, easy....
![]() ... but: when I save /before templates, all custom and default templates would be saved; only ONE copy for each template, even those modified... I.e. I save only the last version of everyone, I guess. When I upgradeXX.php, only DEFAULT ORIGINAL templates are updated, not my customized version. So, when I write them to /after dir, again I'd have only the lastest version of everyone. Not modified by me would be upgraded to 2.2.4, those customized by me, NOT ! Is it true ? What should be the utility to compare already upgraded templates ? If it was right, I'm now searching a way to make all the original templates upgraded, then compare all of them with my customized one branch. Not found till now... unless I use Araxis Merge against vbulletin.style checking one by one all templates modified between 222->223->224 ... ![]() Thanks again, FF. |
![]() |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|