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

[vgevolution]

Is anyone else able to create modifications for the footer template? Mine aren't taking affect at all. Seems to work when I use either Show modified Template or Show commented modified Template from within the Style Manager, but then the changes aren't apply in production. All template mods are active. I'm using vb3.6.8p2, and this is the first time I've tried to modify the footer, so I don't know how long the problem has been occurring. All I'm trying to do is add target="_new" code to the admincp and modcp links.

[vgevolution]

Is the English version of this mod supposed to have the plugin names and footer credits in German?

[Andreas]

Yes, they are supposed to be in german.

Modifying the footer should work just fine.

Can you attach the XML that does not work?

Also, this Mod should work just fine with 3.7 as well.

[vgevolution]

Strange, it seems to be working now. Could template caching be delaying the changes?

[Andreas]

Depends on how you are 'caching templates' ...

[TCE Killa]

great mod thanks.

[Nacho Love]

Hello everyone,

I am currently trying to follow the instructions laid out in the following thread:

http://vbdrupal.org/forum/showthread.php?t=1011

In order to basically make my site look similar to the vbdrupal.org website. My goal is to eventually have my left navigation, header and footer drupal blocks displayed on my forums - giving the appearance that the forum loads within my drupal website.

I have installed the template-modifications manager but have been unsuccessful in getting my changes to take effect. However I am very certain that I am doing something wrong that is likely straightforward for most of you, so can anyone help with my remedial questions?

First I get to this screen - which option do I want?



I've been using the MASTER STYLE one - fyi

Once in there, I grasp the basic concepts here of loading up a template (such as header), however, I don't believe my changes are taking effect. On the following screen ,what exactly do I need to do to make the code changes? I've been making the code appear by clicking 'view template', but from here I'm unsure of what to do to make my code changes take effect. What about naming - does it matter at all? Can anyone please provide step by step instructions on what to do?



Assuming I make the correct code changes, what are my next steps to apply these changes to my website? (pretend you're talking to an idiot )

Thanks for the help, and sorry for being such a noob :erm:

[goddess_dix]

Originally Posted by Nacho Love

Assuming I make the correct code changes, what are my next steps to apply these changes to my website? (pretend you're talking to an idiot )

Thanks for the help, and sorry for being such a noob :erm:

after you set up and save your template changes (and have marked them active in your template setup), you must select the "rebuild all template modifications" option to have your site reflect the changes.

the fact it's for a vbdrupal site doesn't impact how tms works...all tms does is store you template edits in a central location, sort of like a parent style, so you can enable or disable them for different skins. basically it's a search/replace hack for your templates....you can also try making the changes directly in the templates to see how it looks and make sure you're getting the edits you want.

i'd put some random text in your edit so when you rebuild the template modifications, you can see easily whether it's taken or not, because if your simply judging by whether or not your vbdrupal content is showing, you might have another issue to resolve not related to tms.

[Andreas]

You don't have to rebuild all template modifications - rebuildung is being done automatically when necessary.

'Rebuild All Templates' is just for odd cases where automatic rebuilding failed.

[Icy]

Andreas, can I install this on vB 3.7.0 beta 3? If not then any ETA on releasing TMS for vB 3.7.0? One more question about the tms_debrand, can I run the query rather than installing the product? Or can I install the product then uninstall it? Also is this, this & this bugfixes implemented already? Or I have to do this myself?