Version: 4.0, by Trigunflame
Developer Last Online: Nov 2019
Version: 3.5.3
Rating:
Released: 02-09-2006
Last Update: 02-11-2006
Installs: 164
Uses Plugins
Code Changes Additional Files
No support by the author.
Compress Forum Templates Speed up your Forums & Save Bandwidth
Description:
This hack compresses your sites Templates into the database resulting in a significantly smaller page size and faster loading pages.
The benefits of this Template Compressor as opposed to virtually any other that you have installed is that this compresses the templates into the database.
Other hacks compress the pages on every page load which takes CPU/Memory usage as well as slows down the actual output of the page.
1. Download Zip File, Extract files..
2. Read install.txt and follow it
3. Note: Anytime you update your templates, make sure to click "Compress Templates".
4. If you have any problems with certain hacks not working, add affected templates to "Template Ignore" setting in the Admin Control Panel settings.
Common Templates That May Need To Be Added to Ignore Settings:
Version 4.2: Forgot to upload ZIP File..
Version 4.1:
Changed setting location, you now modify them in the Admin Control Panel under Template Compressor Settings; there you can specify the templates to ignore.
Flashchat, others sometimes cause problems; so by default a few vbchat templates are listed in the ignore setting.
If you have problems with any other hacks not showing, trying add the 'forumhome' template to the ignore setting and recompress your templates.
Version 4: Integrating Hellcats regex, hopefully will solve some problems.
I think this works great with most versions The error everyones having is really simple: the regex seeks out all comments, spaces, etc. and reduces or removes them. Pretty much EVERY hack that 'self installs' so to speak uses template comments or other common code areas as a way to 'inject' themselves with a str_replace or preg_replace. Those comments are GONE when you compress your templates, so your hacks have no way to find where to go . To fix these, either put in the optional variable the hack gives (such as $cyb_chatbox as an example), hard code the templates information as needed from the plugin (this is how I put in the 'Who has visited' hack), or change what the plugin looks for, if it looks for a comment, change it to look for something unique in your code around the same area (obv less reliable method). Just don't let the plugins pick where they go, put them where you want yourself, and you can use this great!
Now this means this hack takes a little more experience then some others, but honestly, if you use hacks, mods, or template edits, you SHOULD be more experienced, or just don't do it.
One last comment: I have gotten this to work with EVERY hack i have (except form hack I had to put the answer templates in the bad array exceptions), and I have some difficult ones like the "Who's online in the last 24 hours", the flashchat mods, the Cyb-Chatbox, etc. It's not too hard if you look beyond this as it's this hacks fault, it's doing it's function, the OTHER hacks are not built for this, and it's YOUR job as a webmaster to make it work for you. These plug-ins are making forum owners soft IMO, either use them with some understanding, or if they confuse you there's always the uninstall/delete option, don't blame the coder
Compress Forum Templates Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
09-25-2008, 07:14 AM
The error everyones having is really simple: the regex seeks out all comments, spaces, etc. and reduces or removes them. Pretty much EVERY hack that 'self installs' so to speak uses template comments or other common code areas as a way to 'inject' themselves with a str_replace or preg_replace. Those comments are GONE when you compress your templates, so your hacks have no way to find where to go . To fix these, either put in the optional variable the hack gives (such as $cyb_chatbox as an example), hard code the templates information as needed from the plugin (this is how I put in the 'Who has visited' hack), or change what the plugin looks for, if it looks for a comment, change it to look for something unique in your code around the same area (obv less reliable method). Just don't let the plugins pick where they go, put them where you want yourself, and you can use this great!
