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

[Marv]

Hi all,
hi Andreas.

I am running TMS since a few years and hadn?t touched it in the last year. End of february I?ve tried to do a little template change and noticed the same day here on vb.org, that TMS has an update and a patch available, so I?ve installed them first.

Since this moment TMS wasn?t working proper anymore, means: I couldn?t do new changes. Even though the changes I?ve made before the update seemd to work as before.

Today I had to learn it the hard way, to never change a running system: I had a look at my AdSense-Account and I was shocked about the loss of clicks and revenue. Costs for site and server are barely covered by the revenue and the loss of 70% clicks was some kind of wake-up call.

It took a while to notice, that 2 custom ad-placements I have created years ago were gone. They are still in the TMS and TMS tells me, they are working - but they don?t. The error message is saying:

A curly bracket wasn?t closed. Do you have inserted a curly bracket without content between ( {} )? If so, enclose the complete code with <vb:literal>Your code</vb:literal>.

Has anyone an idea, what I can do now?

I?m now in a situation, that I can?t do changes to the showthread template. Wether through TMS nor through direct template edits. It always displays this error message as shown above. Even when trying to save the original non-altered showthread template.

-- Edit--

Problem solved.
This error occured because of this mod: https://vborg.vbsupport.ru/showthread.php?t=308620 . It?s now in the graveyard for a good reason (the idea sounds promising though, but the code has to be rewritten). For the other 3 who have that addon installed - after you have uninstalled this addon you HAVE TO revert your SHOWTHREAD template or you will have the risk of code fragments still sitting in the SHOWTHREAD template. The uninstall routine hadn?t worked properly in my installation and left changes in the template that caused that error. May be one of the mods could attach this info to the Addon in the graveyard.

[BirdOPrey5]

Originally Posted by Marv

Problem solved.
This error occured because of this mod: https://vborg.vbsupport.ru/showthread.php?t=308620 . It?s now in the graveyard for a good reason (the idea sounds promising though, but the code has to be rewritten). For the other 3 who have that addon installed - after you have uninstalled this addon you HAVE TO revert your SHOWTHREAD template or you will have the risk of code fragments still sitting in the SHOWTHREAD template. The uninstall routine hadn?t worked properly in my installation and left changes in the template that caused that error. May be one of the mods could attach this info to the Addon in the graveyard.

I'm glad revering the template helped you but I don't think the problem came from the Panda mod.

[RavenDust]

Originally Posted by Phaedrus

On Version 4.2.2

I rem'd out line 20 in the forums/admincp/templateedits.php file and it now works again.

Right as rain...

This:

// double output buffering does some weird things, so turn it off
define('CVS_REVISION', '$RCSfile$ - $Revision: 146 $');
define('NOZIP', 1);
$vbulletin->nozip = true;

Became this:

// double output buffering does some weird things, so turn it off
define('CVS_REVISION', '$RCSfile$ - $Revision: 146 $');
define('NOZIP', 1);
//$vbulletin->nozip = true;

You could alway do the (kind of) right thing and do something like

// double output buffering does some weird things, so turn it off
define('CVS_REVISION', '$RCSfile$ - $Revision: 146 $');
define('NOZIP', 1);
$vbulletin = new stdClass();
$vbulletin->nozip = true;

That way you retain the original function of the code, but disable the warning. At least for php 5.4. I mean, this worked fine on my server. No guarantees^^

[Phaedrus]

Originally Posted by RavenDust

You could alway do the (kind of) right thing and do something like

// double output buffering does some weird things, so turn it off
define('CVS_REVISION', '$RCSfile$ - $Revision: 146 $');
define('NOZIP', 1);
$vbulletin = new stdClass();
$vbulletin->nozip = true;

That way you retain the original function of the code, but disable the warning. At least for php 5.4. I mean, this worked fine on my server. No guarantees^^

This worked better than my cutthroat method/quick fix. Some day I'll have time to dig into this. I just don't know when someday is on the calendar.

[Alan_SP]

Does this extremely useful mod still works on vB4.2.2 and 4.2.3b? I see that there needs some lines of code to be modified.

How it works for you? I'm thinking about upgrading to 4.2.2 and this is important mod for my site.

[Toorak Times]

Originally Posted by Alan_SP

Does this extremely useful mod still works on vB4.2.2 and 4.2.3b? I see that there needs some lines of code to be modified.

How it works for you? I'm thinking about upgrading to 4.2.2 and this is important mod for my site.

I'd like to know too Alan. How does it affect template changes made before installation?

[Black Tiger]

I'm wondering about this too. Best mod made ever which makes admin live lots easyer, especially when upgrading after a lot of changes.
It should have been bought by vB and implemented by default.

[Alan_SP]

Or some other developer start developing similar mod with same functionality and using same data format, for example DBTech. If only Andreas would keep supporting his great mods.

[ndahiya]

Originally Posted by Alan_SP

Does this extremely useful mod still works on vB4.2.2 and 4.2.3b? I see that there needs some lines of code to be modified.

How it works for you? I'm thinking about upgrading to 4.2.2 and this is important mod for my site.

This still works great as of 4.2.3 b4.
Install the mod, install the patch (opening post), and then the one small change below.

ndahiya

Originally Posted by RavenDust

You could alway do the (kind of) right thing and do something like

// double output buffering does some weird things, so turn it off
define('CVS_REVISION', '$RCSfile$ - $Revision: 146 $');
define('NOZIP', 1);
$vbulletin = new stdClass();
$vbulletin->nozip = true;

That way you retain the original function of the code, but disable the warning. At least for php 5.4. I mean, this worked fine on my server. No guarantees^^

[Alan_SP]

Thank you very much for your info. :up: