[HTL] Hack Tracking Log

This Hack is released under an EverythingvB.com
FullAttribution-LimitedDerivs-LimitedTranslation License

Hack Tracking Log
Version: 1.00 Gold
vB-version: 3.0.0 RC 3
Developer: KuraFire
Install-difficulty: Easy
File-edits: 3
Template-edits: 0

[high]
Official Hack Tracking Log Product page:
www.everythingvb.com/products/htl/
[/high]


Brief Description of the Hack:
The Hack Tracking Log is an advanced system for maintaining all your vBulletin hacks. You use it to install and / or create hacks, and it will automate many processes for the Admin.

Last update: Tuesday, January 27 (03:33 am CET)
The earlier bug fix caused a new bug to arise. Yes, you may smack me with the cluebat. I f00ked up in my bugfix. *slaps self*
Anyhoo, to patch your install, just overwrite your admincp/hackadmin.php with the new version found in the NEW ZIPFILE, attached below.
I've improved the entire

Former update: Monday, January 26 (2:42 PM CET)
BUG FOUND! A minor, harmless bug was found in the Make vB.org Post section of /admincp/hackadmin.php - to upgrade, re-download the zipfile (clear your cache first!) and overwrite hackadmin.php on your server with the new one. If you haven't yet installed the HTL, make sure to get the latest download and you should be fine. Thanks Rein for the report ^_^


Information on the HTL:
The Hack Tracking Log is an advanced utility for vBulletin administrators (in particular). It allows you to create, manage, install and track vBulletin hacks in detail. For a full features overview, please see the HTL Features Overview on EverythingvB.com That place also holds the full official HTL Documentation, including a F.A.Q. and a Step by Step guide to making a new Hack.


For GENERAL QUESTIONS:
https://vborg.vbsupport.ru/showthread.php?t=60582


For BUGS and OTHER SUPPORT:
http://www.everythingvb.com/forumdisplay.php?f=4


IMPORTANT and/or USEFUL READS!
Advantages to using the HTL
How to Support the HTL
Why should I make HTL-only hacks?


HACK INSTALLATION DETAILS:
New files for this Hack:
/admincp/hackadmin.php
/cpstyles/vBulletin_3_Default/hacklog.gif
/cpstyles/vBulletin_3_Silver/hacklog.gif
/includes/adminfunctions_hacklog.php
/includes/adminfunctions_installroutine.php
/includes/config_htl.php
/hacklog.php

Files modified for this Hack:
/admincp/index.php
/includes/adminfunctions_navpanel.php
/includes/adminfunctions_template.php

New templates for this Hack:
HACKLOG
hacklog_overviewbit
hacklog_hack

New DB tables for this Hack:
hack
hacklog


Tutorial:
How to easily Upgrade your vBulletin using the Hack Tracking Log


PLANNED FOR 1.1:
- Uninstallation of Hacks (section is unfinished atm);
- Text file generators (for vB.org's policy);
- A more flexible List All Modifications page;
- More sensible template insertion (all styles at once)
- Select All link above File/template edit fields for easy selecting (src)
- new vBoption: Restrict hack access to the Allowed Userid's field (yes/no).
Things from these two threads:
http://everythingvb.com/showthread.php?t=27
http://everythingvb.com/showthread.php?t=33


Version 1.1 will come fairly soon, so make sure to Install this hack so that you will receive the update when it comes

Statistics:
- 4702 lines of code
- 616 lines of XML (phrases, templates, settings)
- 229 Kb worth of Hack data

Have fun


COMMON PITFALLS DURING INSTALL:
If you have problems, see the Help section of the Documentation


This post was generated by the Hack Tracking Log

[SloppyGoat]

Great!!! Does this mean that the Miserable Users hack will be re-released for HTL soon?

[PiotrasG]

finally got it installed great hack, makes life lots easier.

[riyatch]

Originally Posted by riyatch

KuraFire, thanks for the response.
what modifications to those files do i have to make??
sorry for the lame question, just starting to learn this stuff.

kura, please disregard my last question. i got it working and its a great mod!!!!!!! thanks

[KuraFire]

Glad you got it working

SloppyGoat: Yeah, I'll release the HTL version of the Miserable Users for vB3 soon

[Kalakov]

just installed on rc4 its pretty easy

[SloppyGoat]

Cool! Nice work!

[Kohhal]

Quick question : when running the install sequence, if the install doesn't finish for whatever reason then it's listed as unfinished. You then have 2 options, delete or continue - but how do you edit the hack if there was a mistake in it? ie. set it back to it's pre-installed status? Maybe deleting it from here would do it but I don't want to risk it right now...

[NuclioN]

Altough this hack has a great potential there are some issues with it also. I've installed the shoutbox hack and it does not remove pre-installed tables properly so the install stops and it leaves an unfinished hack. Removing the tables by hand in the database is to difficult, it installs tables all over the place. When an author does not write a text install/remove instruction your database is full of useless tables or you must have a backup with all tricky consequences eventualy when you want to dump this. I hope this incident with the shoutbox is a single event and i hope all HTL hacks will have a uninstaller/install textfile also.

[KuraFire]

@ TheMasterG:
Nominally, a hack should not be installed when there's a mistake in it. There are various ways of going around the 'safety measures'. The easiest would just be to manually update the hack's status in your database. To do so, verify what hackid it has, then run this query:
UPDATE hack SET atstep=-1 WHERE hackid=THATHACKID
Note 1) keep in mind that if you're using a table prefix, you have to add that before "hack";
Note 2) replace THATHACKID with the hackid, of course

Other ways are, for example, to just delete it, upload the new .htl file (the one that isn't faulty), import that to the database (NO real install!), then edit that hack and disable all steps that you've already done, and then save & do a real install for that hack, thus continuing where you left off.

@ NuclioN:
I don't really get what you mean...

[Link14716]

I found a bug in the generation of phrase XML files.

When you have a set of phrases that use the hack prefix and the phrasetype prefix of your custom prefix, along with a group that only have your hack prefix (i.e. are meant to go into the custom grou), two sets of <phrasetype name="xxx"> would appear, and only the second group would be imported - thus meaning that a lot of phrases aren't installed properly.