The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Template Modification System Details »» | |||||||||||||||||||||||||||||||||||||||||||
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
1.2.0 Beta 3
1.2.0 Beta 2
1.2.0 Beta 1
1.1.5
1.1.4
1.1.3
1.1.1
1.0.0
1.0.0 RC 1
1.0.0 Beta 4
1.0.0 Beta 3
1.0.0 Beta 2 First public Beta Download Now
Screenshots
Show Your Support
|
11 благодарности(ей) от: | ||
alhidaya, Hostboard, izenberg, misericorde, mohammadxxx, o0mohammed0o, Simon Lloyd, Skaut, SWSUSA, usHealthy |
Comments |
#672
|
||||
|
||||
I can't remember that. But this is what the readme says:
Quote:
|
#673
|
||||
|
||||
Update
TMS 1.2.0 Beta 3 is now available. This is the first version that is (well , should ) be fully compatible with vBulletin 4, at least vBulletin 4.1.5 is required. TMS 1.2.0 has one major new feature over the previous release: The possibility to modify style variables via AJAX right from the style manager while editing a template. If there are bugs please let me know. |
#674
|
||||
|
||||
Hi Andreas, i take it on vb3.8.x we'll not loose anything with just import with overwrite?
|
#675
|
||||
|
||||
No, you won't loose anything but it will not work at all anyway; TMS 1.2.0 Beta 1 or higher requires vB 4.1.5 or higher.
|
#676
|
||||
|
||||
Sorry, i just though it would as this is a vb3.8.x thread , ok no worries!
|
#677
|
|||
|
|||
Hi!
I get this when importing the product: Code:
Database error in vBulletin 4.1.5: Invalid SQL: SELECT templateid, searchstrregex, replacestr FROM cf_templateedit AS templateedit INNER JOIN cf_templateeditlocation AS templateeditlocation ON (templateeditlocation.varname=templateedit.varname) INNER JOIN cf_template AS template ON (template.title=templateeditlocation.template) LEFT JOIN cf_style AS style ON (style.styleid=template.styleid AND FIND_IN_SET(templateedit.templateeditid, style.templateeditlist)) LEFT JOIN cf_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_swedish_ci,IMPLICIT) and (latin1_german1_ci,IMPLICIT) for operation '=' Error Number : 1267 The product doesn't show in product manager, cannot uninstall... Thanks for any help :up: |
#678
|
||||
|
||||
Andreas thanks for the update, been waiting for a wile for this to get to 4.x.
Now I can make all my edits, and make this week even better then the last. |
#679
|
||||
|
||||
This Add-on is unsupported except for proven bugs.
However you will find dozens of threads if you search for that error message on vbulletin.com/vbulletin-germany.com. In a nutshell: Your database is inconsistent, fix it. |
#680
|
|||
|
|||
Ok, thank you, I'll have a look :up:
====================================== Edit: in case this could help those non-technical users like me getting that collation error and wishing to uninstall, just DROP tables 'templateedit' and 'templateditlocation' using Phpmyadmin, also delete fields: 'templateeditlist' from the 'style' table and 'edited' from the 'template' table Then delete the uploaded files. |
#681
|
|||
|
|||
Uptaded Thank you
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|