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 |
#512
|
||||
|
||||
When you search this mod for "illegal collations", what do you see? Obviously your post is at the top, but surely you must see mine below that?
I agonized over that problem for weeks. I'm still a little pissed about it I guess, sorry. Especially if people are going to keep posting the problem even after I posted a solution for it. |
#513
|
|||
|
|||
There is no reason to get angry. I saw your post. Your solution requires that I backup my 450MB database, run a "search and replace" and then re-upload the 450MB database. This is an impossible solution for me. There is just no way to do that on such a large, large, large database.
|
#514
|
|||
|
|||
Look here: http://www.phpwact.org/php/i18n/utf-8/mysql
|
#515
|
|||
|
|||
Thank you dartho. That was very helpful. I also found that I can change the overall characterset in phpMyAdmin using the "operations" tab.
|
#516
|
||||
|
||||
wtf... out of line a bit I might be but rest assured your sanity is safe with me...
Quote:
Quote:
Quote:
Now you can try changing the collation via phpmyadmin if you have that or another alternative. Backup your DB before doing anything in any editor etc. If it works fine then uninstall the currently disabled mod, leave any files if present but install it again via the product etc, then it should work. S-MAN |
#517
|
||||
|
||||
Quote:
But if that's the case, I also gave a link to a programmatic solution. However, that was taking forever for me as it would fail every few lines, and taking the time to make the corrections manually got onerous really fast. |
#518
|
||||
|
||||
Erm ... you don't have to dump the whole database just to fix a couple illegal collations.
just take a look at your DB, find out which collation is being used most often, adjust the new tables/fields that generate error accordingly and you're done. |
#519
|
||||
|
||||
Quote:
Fact is, in my case about 80 tables were different collations, and after sitting down one day and manually changing each one in PHPMyAdmin, I discovered that only changes the tables, not the fields within! A real PITA that hadn't bothered me at all until I tried to install this mod. |
#520
|
|||
|
|||
am I limited to editing only these templates?
I'm trying to edit showthread through TMS. EDIT: I just read that I can onyl use TMS on templates I already edit so if I already manually edit the template I want why am I also adding that edits in TMS? I'm confused. and do I always have to edit manually first to make it appear in the drop down list of TMS then change the one I manually edited back to the default and then add the edits in TMS? Someone share me how you do it. |
#521
|
|||
|
|||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|