Version: 1.00, by Link14716
Developer Last Online: Oct 2023
Version: 3.0.3
Rating:
Released: 11-09-2004
Last Update: Never
Installs: 26
Supported DB Changes
I decided to release what I thought was a stable build 3 early. For those who actually used build 2 in their hacks (if there are any), delete the build 2 files and replace them with the build 3 files (except the example hack). Build 3 changes the way the HIS file are laid out, so hack_install.php was changed quite a bit. Seriously, upgrade. Your build 1/2 hack files will work with build 3.
Now that I've finished my public service announcement, I must not that a hack creator script, allowing for easy creation of the hack files, is not included in this release. I decided to release build 3 before the creator script is finalized. If you want to create hack files now, you'll have to first make a folder for your hack (replacing spaces with underscores), a folder inside for the build number (1 probably, but you can use another number). Then, move the example index.php over and edit it as necessary. Then, upload the folder and index.php to the hacks folder, select it, check "Generate Files" and continue. It will generate all the files needed except the query and modification files. For those, just follow the example file's syntax.
Now, onto the HIS!
The Hack Installer System (HIS) is an HTL-like hack. However, it suceeds in one major place the HTL failed: vBulletin.org compliance.
The HIS is a hacker tool - it does not need a seperate installation. It only needs one database table, which is created automatically the first time the script is ran. Thus, it can be distributed along with your hack as its installer as long as you follow the terms:
You may NOT modify hack_install.php or hack_install_bx.php (where x is the build number) and leave it named as such. If you modify hack_install_bx.php, rename your modified hack_install_bx.php to something entirely different (probably yourhack_install.php) first. ONLY THE OFFICIAL UNMODIFIED FILES MAY BE NAMED hack_install.php AND hack_install_bx.php. Even if you modify and rename, the original copyright text at the top must remain intact.
Eh, well, I think that is all the terms. Anyways, on to this "hack".
This is based off of the uCash & uShop installer, which was based off of the vBadvanced Homepage 1.01 installer by Tigga (Brian Gunter), used with permission.
Build 3 is attached, screens should be attached in this post and in the following post.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I was fooling around with this hack, and optimized it to my needs. I have saved much time in modifying clients bulletin boards. This hack was missing a couple of stuff, but I stuck it in. I will post back with some details that some may take advantage of to fully utilize the whole power of this hack.
Looking into using HIS for a new hack i am writing, thx for making life a bit easier Link.
Running into 1 problem (well not really problem atm):
If there is a database error during install, the db_mysql.php can't include the './includes/functions_log_error.php' because current directory is different then expected. This will be more a nuisance during testing then when a hack is finished.