Administrative and Maintenance Tools - Template Modification System

Template Modification System
Description
This modification allows easy management of template modifications.
Hack authors can define the necessary template modifications for their products.
When exporting a product, all template modifications assigned to this product
in MASTER style will be embedded into the product XML and imported on the
end-user vBulletin installation automatically if TMS is available.
Alternatively, it is also possible to create separate XML files for template modifications.
This way, 3rd parties can provide Template-Modification XML files for existing hacks.
Hack authors can also export standard template modification instructions as
textfiles to package them with their hacks, which allows users that do not
have TMS to also install them

In case the author defined modifications do not work (eg. the user uses a custom style),
the users can easily customize the modifications for their style(s).

TMS modified templates transparently, e.g. all Templates can still be modified
manually in style manager - they will appear unchanged there.


System Requirements
This Modification requires MySQL 4.1 or higher - it does not work with MySQL 4.0!
If you use MySQL 4.1 series, MySQL 4.1.10 or higher is required
If you use MySQL 5.0 series, MySQL 5.0.3 or higher is required
TMS 1.2.0 Beta 1 or higher requires vBulletin 4.1.5 or higher

vBulletin Compatibility
Versions up to and including 1.1.5 are compatible with vBulletin 3.6.X, 3.7.X and 3.8.X
Version 1.1.5 is partly compatible with vBulletin 4.0.X and 4.1.X
Version 1.2.0 Beta 1 or higher is compatible with vBulletin 4.1.5 or higher
vBulletin 4.1.11 or higher is currently not fully supported by TMS. If you use this version please apply the following patch: tms_patch120b4.zip

Branding:
Please note that TMS puts a small branding/copyright notice in footer - see readme.txt for further details.

Version History
1.2.0 Beta 4

• Bugfix: Database error when trying to add a template modification (this bug was introduced in TMS 1.2.0 Beta 3)

1.2.0 Beta 3

• Changed: Converted hardcoded text to phrases
• New Feature: Added doubleclick for editing style variables
• Bugfix: Database error when trying to add a template modification with an existing varname to a different style
• Changed: Fixed formatting of templateedits.php
• Bugfix: Fixed erors when manually modifying a template with template modifications

1.2.0 Beta 2

• Bugfix: Fixed errors in style variable editing code

1.2.0 Beta 1

• Changed: Ported to vBulletin 4.1
• New Feature: If an error occurs while trying to compile a template this error is now being disaplayed when trying to save the template modification
• New Feature: Styles variables used in templates can be edited via AJAX from the modify template screen

1.1.5

• Fixed Bug: Fixed incorrect variable type
• New Feature: Box 'Template-Modifications' (shown on editing a template) can now be collapsed/expanded

1.1.4

• Fixed Bug: Fixed HTML error/XSS in Template Modifications Manager

1.1.3

• Fixed Bug: Added missing phrase on ACP home

1.1.1

• Fixed Bug: Fixed Error with conflicting Template Modifications when importing a product
• Fixed Bug: Removed Pre-Selection of processing mode when adding new modifications
• Fixed Bug: Fixed Bug with zlib.output_compression AND vBulletin internal gzip being both turned on
• Fixed Bug: Display search results correctly
• Fixed Bug: Added missing phrase 'varname_x_already_exists'
• New Feature: Automatically rebuild template modifications after vBulletin Upgrade

1.0.0

• Changed: Several files renamed
• Fixed Bug: Fixed incorrect handling of product ids that contain only numbers
• New Feature: Search text can be search in template when editing a Template-Modification in Style Manager
• Changed: Multiple Template-Modifications can be loaded via AJAX
• First Release on vBulletin.org

1.0.0 RC 1

• Fixed Bug: All Bugs reported for Beta 4 have been fixed
• Changed: Display of modified Templates with HTML comments has been modified
• Changed: Debug-Mode is no longer required
• New Feature: It is now possible to export/import style-specific Template-Modifications

1.0.0 Beta 4

• Fixed Bug: All Bugs reported for Beta 3 have been fixed
• Changed: Sorting in Template Modifications Manager has been changed
• New Feature: When adding or editing a Template-Modification, the Template can now be displayed and searched via AJAX
• Changed: When exporting as Text, the original instructions (eg. insert below/above) are retained
• New Feature: It is now possible to test each Template-Modification
• New Feature: Testing improved. It is now being display if a Template is OK after applying a Template Modification
• New Feature: When editing a Template, it is possible to activate/deactvate multiple Template-Modifications
• New Feature: Template-Modifications can now also be exported and tested from withing Product Manager
• New Feature: Function to display a template with all Modifications applied.
  This function can also display embedded comments to make it easier to identify changed parts

1.0.0 Beta 3

• Fixed Bug: All Bugs reported for Beta 2 have been fixed
• New Feature: Simplified adding Template-Modifications by allowing to select how to handle replacement text (eg. replace or insert above/below)
• New Feature: Each Template-Modification can now be disabled
• Changed: Testing Template-Modifications has been reworked:
  Column ordering can now be set through vBulletin Options; column headers are clickable to sort results
  Output has been separated by styles
  It is now possible to test only selcted products
• New Feature: TMS now integrates with 'Style Manager' and 'Product Manager'
• New Feature: The language can be selected when exporting Template-Modifications
• New Feature: Weh TMS gets deactivated, all Template-Modifications will be deactivated too
• New Feature: Display of Template-Modifications while editing a Template in Style Manager has been improved:
  It is now being display if a Template-Modification could be applied
  Template-Modifications can be edited via AJAX

1.0.0 Beta 2
First public Beta

[Andreas]

This is TMS for vBulelltin 3.7; unforfunetely I can only set 1 compatible version.

You can't 'install' tms_debrand.xml as the installation process will never complete - it's just to remove the branding.

The bugfixes have been implemented, but there is no ETA for a new version yet.

[Icy]

Thanks but this one still not implemented. Should I import the tms-plugin-outputbuffer.xml plugin?

[Andreas]

Please re-read my last post again ...

I said it's implemented, but there is no ETA for a new version yet.

[Icy]

Sorry. I thought these three bugfixes have been implemented in current version. Thanks for the reply.

[alexgeek]

Installed, thanks

[KURTZ]

i dont understand: is compatible or not with 3.7.0 B3?

[Icy]

Originally Posted by KURTZ

i dont understand: is compatible or not with 3.7.0 B3?

I'm using it on my vB 3.7.0 B3 live forum

[Hawaiian-TV]

I hate to be the rotten apple in your basket but I just installed the TMS, clicked View Template, made some manual modifications to a template on the MASTER style, then clicked Save. Voila' ... the modifications were done on all templates. I was impressed!

I noticed though that the template I modified (which was for another mod) didn't work properly so I uninstalled it via the Product Manager. The templates were all the same of course because I hadn't modified them. Then I went back to the TMS, selected that same template to "Revert" the templates back, and hit the Revert button.

Unfortunately the templates did not revert. Worse yet, I noticed for the first time a notice in German at the bottom of every page on the website that the template had been modified by the TMS system. (it almost brought back memories of Nazi Germany, seeing the site having been defaced by the product). Thank God I did of course save a backup SQL file to undo any damage your product may have caused. Maybe one or more other template mods I installed is conflicting with TMS? All I know is if others are having this same problem I suggest this product be moved temporarily to the Product Graveyard until it is fixed.

By the way, we are using VBulletin version 3.6.8 Patch 2.

Computerman

[Andreas]

Originally Posted by Hawaiian-TV

made some manual modifications to a template on the MASTER style, then clicked Save.

You should never ever modify templates in MASTER style (unless they are templates of a product you are deveoping).
Voila' ... the modifications were done on all templates. I was impressed!

I noticed though that the template I modified (which was for another mod) didn't work properly so I uninstalled it via the Product Manager.

You can't 'uninstall' templates vir product manager, only producst?

Unfortunately the templates did not revert.

If you manually modified a template in MASTER style, TMS won't ever revert those changed - as it has nothing to do with the modifications anyway.

Worse yet, I noticed for the first time a notice in German at the bottom of every page on the website that the template had been modified by the TMS system.

It is clearly stated in the readme.txt that TMS puts a branding in the footer.

All I know is if others are having this same problem I suggest this product be moved temporarily to the Product Graveyard until it is fixed.

There is no reason for such action; TMS runs fine on dozens of production sites.

[Lionel]

Originally Posted by Andreas

There is no reason for such action; TMS runs fine on dozens of production sites.

You are being modest, Andreas, not dozens, HUNDREDS