The Hack Tracking Log - now's the time for all your questions! Come here and ask!

[KuraFire]

Originally Posted by MetalGearMaster

I don't understand how exactly the HTL KNOWS whether a hack is a "normal," imported," or "uninstalled" hack. Is it like a page where we can "add" hacks just like we can add styles and input all the info ourselves, and then we can select whether it is a normal hack or an imported hack? and then if we ever uninstall it, click on uninstall in that same page?? something like that at all?

and what's the difference between Normal hacks and Imported Hacks? My guess is that normal hacks are those that are done with a .htl file, but then whats an imported hack???

MGM out

I'll explain this briefly now, cos I'm about to go sleep. Also because it will be made very abundantly clear to you once you get to see the HTL with your own eyes, fully functional etc.

With the HTL, a Hack is not just some file edits and other things you have performed/changed on your vBulletin, but also an entry in a database table. This table holds ALL data relevant for the Hack (paired with another table that takes care of file and template modifications).

Adding Hacks (note: not installing them, but creating them yourself) is indeed done much like the Add Style page (or perhaps rather, the Add User page, as there's a lot of data on that page). In here, however, you don't specify what kind of Hack it is. That's done from the HTL's Install Routine system.

What basically happens when you install a Hack is this:

1) at first you get to choose: Real install, Test Run, Verbose Test Run, and (in case you're not running the install sequence from an already installed Hack) Import to Database.
Real Install will, evidently, really perform all actions and require you to make the file edits.
Test Run and Verbose Test Run will not make any changes whatsoever, but take you through the entire Install Routine for the Hack nonetheless. Verbose will give complete output to what will happen during each step of the installation, should you choose to perform a Real Install.
Import to Database means: insert this Hack's data into my database table(s), without making any changes whatsoever to my system. The benefit for that is that you can look into all the details of the Hack, before choosing to actually install it. You can do test runs of an Imported Hack (meaning: not install anything, but see what happens during install), you can delete Imported Hacks, and you can edit/alter them as your own if you feel you should (keep in mind the Author's copyright and wishes!).

2) if you choose a Real Install or (Verbose) Test Run, you will proceed to go through the various steps of the Install Routine. During each step, the HTL System will keep track of what step you have performed, and store that data in the database with your hack (just like how the vB installation/upgrade keeps track of what Step you are at). If you don't follow the Installation run (if it's a Real install) all the way to the very end, the Hack will appear in the Unfinished Installs section on the Manage Hacks page. From there, you can choose to continue where you left off.

If you choose to import a hack into your database, it will be imported with a certain 'status flag' being set in a way that tells the system that this Hack is not actually installed, but merely imported. Then it will show up in red for you, to tell you that it's an Imported hack.


Make things a bit clearer? Guess I wasn't very brief huh? Ahwell