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

[MalluParadise]

work with vb 4.1.7 ?

[Andreas]

Originally Posted by Phaedrus

Quick question, Andreas...

If I donated to have the unbranded version long ago, will upgrading rebrand me?

No. Branding-free licenses for TMS are perpetual, eg. valid for any version.

Originally Posted by fly

Well he was a vB dev at one point...

Yes - I was, but that was several years ago (at 3.5/3.6)

It's still beta so no support will be given yet.

Even if it comes out of beta (which I expect to happen soon as there have not been new bug reports for quite some time) it will still be unsupported as I simply do not have the time to give support.
Apart from that TMS 1.2.0 Beta 4 should work just fine with 4.1.7, 4.1.8, 4.1.9 ... basically any version > 4.1.5

[thecore762]

Thanks for the update Andreas, everything working great!

[addamroy]

Can someone verify if this will work with vb 4.0.7??

I want to use this addon so this one, https://vborg.vbsupport.ru/showthrea...hlight=sprites will be easier to install.

Also, where do I get the branding free version, I absolutely will not place a sitewide footer link to websites irrelevant to my forum, that's absurd.

I already sent an email to the email in the readme but didn't get a response back.

I'd love to use this just to make the installation of other products easier like the one I linked to above. However, in the description it says 'partly compatible with 4.0.x', what exactly do you mean by partly?

Is the sitewide footer link really necessary? It's not like anybody on my forum or many other forums would have any interest in the link back anyways since it's completely irrelevant and certainly won't add any value to the community.

[dartho]

Yes, it works with 4.0.7

Having a footer link or branding is like an author having his name on the front cover of a book. Fortunately for you, the author has been generous enough to provide a means for having it removed.

Send the author a $100 donation using the "Support Developer" link in the first post and you will be able to remove branding.

[B16MCC]

Hi , great mod. Installed and working fine. Just one thing I'd like to ask please ...

Could this be expanded to include the creation of custom templates ?
In my forum I use several additional templates, if I install a new style I have to recreate all my custom styles in that new style.

I just wondered if this could be used to add existing templates to new styles, unless there's a simple way of doing it ?

[Andreas]

Originally Posted by addamroy

I already sent an email to the email in the readme but didn't get a response back.

Maybe I missed it but I don't rembmber any email from you?

However, in the description it says 'partly compatible with 4.0.x', what exactly do you mean by partly?

Partly means that it does work, but that it is not fully compatible
Eg. expect problems in some usae cases (like editing a template that has template modifications, modifying a .css-template with TMS, saving a template-modification that contains one half of a conditional, etc.).
Apart from that it does work (eg. importing Add-ons that contain TMS data and having that applied).

Is the sitewide footer link really necessary?

Yes
Developing software costs a lot of time - the link compensates that.
If you do not want to have a link you can purcahse a branding-free license for 15 €.

Could this be expanded to include the creation of custom templates ?

TMS is not care if templates are "custom" or not.
For you usecase I'd sugest to create your own Add-on, create your custom templates for that Add-on in MASTER style - then they will automatically appear in all styles.
But that has nothing to do with TMS

[tpearl5]

With the latest beta i'm getting a "No Template-Modifications could be found for this product." after trying to export some custom template modifications that I entered. (templateedits.php?do=files) I'm 100% sure that I'm choosing the correct product. Any ideas?

Update - It's probably because I didn't choose the correct style

[Maxii]

error

Database error in vBulletin 4.1.9:

Invalid SQL:

SELECT templateid, searchstrregex, replacestr
FROM templateedit AS templateedit
INNER JOIN templateeditlocation AS templateeditlocation ON (templateeditlocation.varname=templateedit.varname )
INNER JOIN template AS template ON (template.title=templateeditlocation.template)
LEFT JOIN style AS style ON (style.styleid=template.styleid AND FIND_IN_SET(templateedit.templateeditid, style.templateeditlist))
LEFT JOIN product AS product ON (product.productid=templateeditlocation.product)
WHERE (NOT ISNULL(style.styleid) OR (templateedit.styleid=-1 AND template.styleid=-1))
AND (product.active=1 OR templateeditlocation.product='vbulletin')
AND templateedit.active = 1
AND template.title IN ('footer')

ORDER BY searchorder ASC;

MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '='
Error Number : 1267

edit - fixed my problem

[franks]

Could you share how did you fix it? I'm facing the same problem.

Thanks.