Upgrade templates on a hacked board

[Jawelin]

When upgrading an hacked vbulletin using upgradeXX.php, only default templates are updated, but not modified ones.
Well; how could I manage by hand the new templates and apply all the differences just I could do with the php code ?
Tried to use for example TBS Hack (see here), but my customized templates aren't touched at all; so I haven't a FULL UPGRADE of the board, loosing some little fix or new feature, this way.

Thank you for any help.
:tired:

[FWC]

You can compare the default templates and the modified ones with a file compare utility just like the PHP files. That's the easiest way to do it if there are extensive changes.

[Jawelin]

Yeh. Of course.
The problem is : how could I upgrade the default templates if they are 'marked' as modified ?

All those templates listed as :
[edit] [revert to original] [view original] aren't upgraded at all...
Let's say: I'm on v2.2.2, now. How could I see 'how they should have been' in an UNhacked v2.2.4 board ?
How could I backup the original UPGRADED templates (parallel branch than mine hacked...) with TBS, for instance ?

Thanks

[pogo]

I don't know if the TBS hack is able to save the master templates as well. But you need them to compare them.

This is how I do template upgrades:

• I save the original old master templates to text files
• I save the original new master templates to text files
• I use a file compare utility to compare the old and new template files
• I insert the changes I find into my modified templates

I never used the TBS hack so it is possible that it can save the master templates.

I use this script: Save template to textfile

[Admin]

My hack does save master templates.

[Jawelin]

Originally posted by FireFly
I'm thinking about writing a piece of code that can:
a) Write all templates to text files (kinda like this)
and more important
b) Can read all templates from text files and update database accordingly.

Why?
This would be great for upgrading. You can make two folders, one of the new templates (let's say the original v2.2.0 template), and another one for your customized template (let's say your own v2.0.3 template).
Now you can use something like Araxis or Beyond Compare to compare the files, update, and save everything to the database with ease!

Great, Chen!
As asked here, how could I with TBS:
- backup all master and modified templates
- upgrade all original templates with upgradeXX.php
- re-backup all master upgraded templates
- compare them each other (this is easier to me... )

????

Thanks

[Admin]

Open up tbs.php, and backup all templates to /before. Then upgrade vBulletin, and again backup all templates to /after. Now use Araxis Merge or Beyond Compare to compare these two folders, and save changes to the text files. After that, go to tbs.php again and this time import all templates from the /after folder.

[Jawelin]

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.

[Jawelin]

This is what I mean (it comes from vb.com announcements )

Originally posted by John
Changed Templates

Note: Upgrading will not overwrite any of your custom templates. If you have customized any template that is listed as 'modified' below, we seriously recommend using the 'revert' option to return them to the default template, then re-applying your customizations.

Actually, SHOULD I
- backup (tbs) all my templates
- find all changed ones on db and revert them to the original
- run upgrade16 and upgrade17 (2.2.2->2.2.4)
- backup (tbs) all original upgraded templates
- find (Araxis Merge) and reapply all differences
???

I definetively think a compare between the two or three .style file should be more efficient....

:ermm: :ermm: :ermm:

[Jawelin]

Originally posted by Jawelin
I definetively think a compare between the two or three .style file should be more efficient....

:speechless:
NO! Too expensive !!
Too many differences... sob!

Let's try with template table on db... What's the exact meaning of templatesetid field and all the allowed (special) values ???

Well. I'm in the right middle of the 2.2.2 -> 2.2.4 upgrade procedure (successfully updated all the code and all the un-customized templates) ...
But loose as said all upgrades to my hacked templates... Please don't let me alone... now !!!!


Ahhh! Forgot to add this simple query to find all the customized templates (better, the version counter) directly into db:

SELECT title, count(*) as moltep 
FROM `template` 
WHERE 1=1 
GROUP BY title 
ORDER BY moltep DESC, title ASC

Thnx