Version: 1.00, by Adrian Schneider
Developer Last Online: Nov 2022
Category: Administrative and Maintenance Tools -
Version: 3.7.0 Beta 4
Rating:
Released: 02-12-2008
Last Update: 02-12-2008
Installs: 82
Uses Plugins
Additional Files Is in Beta Stage
No support by the author.
Development Tool: Automatic Template Compiler
Requirements: PHP 5, vBulletin 3.5+
Summary: Allows you to edit HTML files directly instead of using the AdminCP template editor. ATC will automatically update the database if any changes are detected. This is intended for a development environment only, and will only run while in debug mode.
Why: Template development is a huge PITA because of how templates are stored in the database - they are compiled. This means you cannot simply save a file, or update the database, because vBulletin needs to compile them first, and maybe even update the style cache. This saves TONS of time copy pasting and switching between your editor, your page, and the vBulletin template editor box.
How it works: ATC maintains a checksum (md5 hash) of each template body, and when it finds that one is out of sync with your working copy, it will save that template automatically in a very efficient manner. It updates both the template about to be displayed in memory and also the real copy in the database.
It also includes a very basic import utility so you can copy your existing templates into the filesystem for easy editing.
How to use it: Follow the install instructions, and then whenever you edit a file, the changes will transfer to vBulletin itself.
This was written in PHP 5 (OO) and I have no plans to make it work with PHP 4, but I may eventually build an interface to manage the settings, but for developers, configuring it should be no problem.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
you say you need to put ?do=atc_import as a variable on a page to import existing templates, but don't you mean ?do=import ?
however, thanks for this good time-saver
Someone has to be, otherwise we'll still be having this discussion when PHP20 comes out. PHP4 is a dead language. It has been officially "end of lifed" since the end of last year.
It's time we started exerting pressure as a community on all those hosting companies who refuse to upgrade, by voting with our feet. There are plenty of good hosts who do provide PHP5, and would be more than happy to take your business.
However, in this case the usual excuse that "my host doesn't support it" doesn't fly, as this tool is purely for use on local development machines, where it is up to you what version you run. Even if you still need to code to PHP4 standards, there's no reason you can't run PHP5. Just don't use any of the new features in your code.
If you have to have PHP4 available for testing, just run XAMPP, which has a neat little button that lets you switch between 4 and 5.
Can you do me a favor and move the config out of the plugin? Even if it's just a simple ACP option with stuff like:
myprojectid;1.0.2
anotherproduct;2.1.1
... and modify the plugin to grab that data and import / export any listed products.
At the moment, whenever we update your product, we lose any config data in the plugin. And lets face it, you do so like to rewrite and update your code.
Speaking of updating, how about also adding the help and version URL's in the product?
hmm, if i edit a template (file) and save it and refresh my page it shows the changes.
But if I refresh my page again, they are gone...
You'll have to PM me login details to try and debug that one. Try rebuilding your styles to see if that fixes it (does you no good, but narrows it down for me).
I'm about to upload an updated version where the config is moved into options.
Edit: i found the problem: he saved it in another style than the style i was working in.
I'm testing the new version Aj mentioned. As well as moving the config into an ACP option, I also bullied him adding configurable style-ids per product for import and export. So that will solve your problem.