Perhaps I'm not understanding this - are you saying that if I am using a style (let's call it 'My-Style') that is a child of the MASTER STYLE then TMS will not work on any of the 'My-Style' templates unless they are customised versions in My-Style (i.e. not inherited from MASTER) ?

This seems to be a bit of a big drawback as that's how most forums I've seen are set-up.

:confused: hmmmm i didnt get it?!!!
so what does it do exactly? it make the changes for certain style into another ? or what?!!

:p sorry if i sound stuiped

No. It means:
If your postbit template is not customized in style 'My Style' (which inherits from MASTER), you can't apply modifications to this template that are different from the modification applied to MASTER postbit template.
Technical background: Templates that are inherited only exist as references.

Basically: It allows you to modify templates without customizing them.
This means, that your modifications will still work after vBulletin updates - vBulletin will not 'complain' about outdated templates.
It means that you don't have to edit templates manually if the product support TMS - just install/uninstall/activate/deactivate, the template stuff will be done automatically.
All this is done without any overhead at frontend runtime.

@All
If you are using this modification and have added template-modifications for products released on vBulletin.org to your installation - feel free to export your XMLs and share them with others here.

Fantastic thing, good to see it is final 1.0.0 now :)

Thanks for this handy tool !

Kirby!!! Thanks for the release. Will look at this when time permits. :)

MOTM klicked :)

right!

It does not work in IE7 :

Line: 120
Char: 55
Error: Identifier expected
Code: 0
URL: http://....../templateedits.php

and it is not possible to go anywhere by Go.

Try the attached JS file.
I'll also update the package later.

Sorry,

Same error......