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

[derrene]

1.1.5 works on 4.0.2

after modification or adding new

click "rebuild all template modifications"
below under the table

[fly]

Originally Posted by derrene

1.1.5 works on 4.0.2

after modification or adding new

click "rebuild all template modifications"
below under the table

It doesn't work on CSS templates.

[demonfatal]

When I want uninstall it I get this sql error:
----------------------------------------------------------
Database error in vBulletin 3.8.4:

Invalid SQL:

SELECT templateid
FROM template
WHERE
edited=1;

MySQL Error : Unknown column 'edited' in 'where clause'
Error Number : 1054
Request Date : Monday, March 8th 2010 @ 08:14:10 AM
Error Date : Monday, March 8th 2010 @ 08:14:11 AM
Script : http://www.XXXXXXXXXX/forums/admincp...do=productkill
Referrer : http://www.XXXXXXXXX/forums/admincp/...oductid=tms&s=
IP Address : XXXXXXXXXXXXX
Username : XYX
Classname : vB_Database
MySQL Version : 5.0.90
---------------------------------------------------

Any help will be appreciated.

[Black Tiger]

I can't get this working on v4.02.

When importing 1.1.5 eng then the following error occurs:

Warning: require_once([path]/includes/adminfunctions_templateedits.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/adminfunctions_plugin.php(450) : eval()'d code on line 24

Fatal error: require_once() [function.require]: Failed opening required '/home/username/domains/mysite.org/public_html/includes/adminfunctions_templateedits.php' (include_path= '.:/usr/local/lib/php') in /home/username/domains/mysite.org/public_html/includes/adminfunctions_plugin.php(450) : eval()'d code on line 24

That's odd because the adminfunctions_templateedits.php is present in the /includes directory.
Any idea?
(I added a space here on the forums after include_path) so the text width fits better.

Additional info: Seems I also cant view version_tms.php with the browser get a 404 while the file is present. The normale vbulletin files will give me a blank screen but no error notice, so those work as they should be.
Very strange.

[lgnd]

Upgraded my forum from 4.0.1 to 4.0.2 PL1 yesterday and TMS is working with css files as well.

[Black Tiger]

Problem of mine is gone with the wind. The main admin imported the mod without any problems.
But I keep wondering why I got the error.

[lgnd]

I got the following error during working with TMS

Warning: Invalid argument supplied for foreach() in [path]/includes/adminfunctions_template.php on line 913

Found the solution with searching the vb forum:

Store CSS Stylesheets as Files? = No

TMS is working with CSS without any issues with 4.0.2.PL1 at my forum.

[Black Tiger]

Tank you Ingd. But I only got the message during installation. When the other admin imported it, he did not change anything, just imported it the same way I did and it worked without problems.
But maybe your answer can help others with a kind like problem, thank you.

[|Jordan|]

Something wierd is happening. All my template edits for postbit_legacy dont work but everything else is fine and my site is set up to use the legacy postbit. I haven't edited the style, TMS says that the template modification works - but yet it doesnt show up on my site. I tried rebuilding templates and rebuilding template modifications and it doesnt fix it.

EDIT: Nevermind, i found it. There was a missind </if> tag in one of my template edits.

[HydraulicJack]

I'm interested in the 4.x version of this product so I hope you'll let me know when it's available. Thanks!
HJ