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

[Black Tiger]

Thanks for your quick answers Icy!

1.) Oke I was afraid of that.
2.) I just implemented some new edits, the test is not done automatically, you have to use the test function after implenting indeed, but that works nice.
3.) There must be a way because it get's implemented some way. Branding free is for removing the notice. I don't want it removed I only want it displayed in English.

Thanks again for your quick support.

[Icy]

Originally Posted by Black Tiger

Thanks for your quick answers Icy!.

You're most welcome

Originally Posted by Black Tiger

2.) I just implemented some new edits, the test is not done automatically, you have to use the test function after implenting indeed, but that works nice.

When you upgrade your vBulletin the TMS will automatically test all the modifications & show the status on your admin control panel index like the vBulletin's updated template function does.

Originally Posted by Black Tiger

3.) There must be a way because it get's implemented some way. Branding free is for removing the notice. I don't want it removed I only want it displayed in English.

As far as I'm concern somewhere in this thread Andreas mentioned the copyright will stay in German language. However you can wait for Andreas's confirmation.

[Black Tiger]

Oke, otherwise I could pm Andrea.

Now I've got another problem. I just logged in to my ACP and see a notice that wasn't there before it has this headline:

Help !!! Out-of-date Template-Modifications found !!!

And this is the content of the notice:

There are 1 Template-Modifications that were not desinged for the currently installed vBulletin version. To make sure that vBulletin and your installed Products are working correctly, you must check and maybe modify those Template-Modifications.

Test Template-Modifications

But when I use the test function (it's clickable in this notice) all 3 template edit i made so far has a "v" in the circle, meaning they are ok.

So now I don't know what the problem is. Nore why it's giving this notice.

I could try and disable them one by one to see which one is giving the problem, but I wonder why this notice was not given yesterday after I implemented them.

Or could this notice appear because I'm using vb 3.7.0 beta 5 and TMS is not recognizing things?

[Icy]

Try another fix

[Black Tiger]

Oh LoL, I should start using the search function in this mod I see.
Happened because I'm used to it at vb.org that if fixes are made, they are included in the distribution package by the coder.
Thanks again Icy!

[Lionel]

Hello, are there any known issues with the go button not working on a Mac G5 with Safari?

[dancue]

Can you believe I just asked for this same exact type of mod in general discussions?!?!

Great mod!!

Edit.....

I have the same problem with the go button on safari. I'm using a macbook pro.

[dancue]

I downloaded FF and it worked on that. I guess I will just have to use that.

[dancue]

Okay, Okay...

This IS the greatest mod ever!! It SHOULD come standard on vBulletin!!!

My only suggestion would be to put together some instructions, maybe examples of how to use the product. I must admit, even after reading the faq, and the instructions I was still a bit intimidated, and then scared to "mess things up" after reading the 17 pages here.

A video tutorial would be nice. This Mod is worth the time to make one...I just don't know how.

If someone could do that it would save Andreas time so he may continue working on his wonderful mods!!

*clicked install
*nominated for MOTM

[dancue]

Also, a quick question....

I added a template-modification to the master style, which worked great for me because it added it to all the other styles automatically. ( I do not have child styles)

Now, if I add a new style, will it automatically add the template-modifications to that style?