Description This Modification is a tool for Hack Coders.
Since vB version 3.5.4 there is an improved File Version checker included as part of the diagnostics. All files in the forumhome directory will be checked if they are know and if the content is not changed.
To do this vBulletin uses a file called ./includes/md5_sums_PRODUCTID.php
This file contains all known files (for the hack the file is written for) and a MD5 hash of the files.
If you don't supply this file, admins will be warned for unknown files in their forumhome directory if you hack upload new files there. To create such a file by hand is not easy, but this hack can do it for you.
How to use:
AdminCP->Plugin System->Version File Manager
You will see a list of all Products installed on the board.
Click edit behind your Product and on the next screen, place all files that will be uploaded for your Hack in the text box. Each on their own line, with a absolut path as from the forumhome directory.
When you are ready to package and release your product, choose Generate MD5 File from the Dropdown menu.
There will now a new file be generated in your includes directory named md5_sums_PRODUCTID.php
Include this file in your Product zip-file (upload/includes directory).
Finished
You must have write access to your ./includes directory!
Not tested on systems with open_basedir restriction.
Copyright etc.
# Copyright ?2006 MarcoH64
# This Modification may not be redistributed in whole or significant part or changed without prior written agreement of author.
Please don't forget to click Install at vbulletin.org.
If you like this work and would like to support the author, donations are always welcome at Paypal: marcoh64@gmail.com
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
When you click on the diagnostic tool and suspect version, the files that you have done this too should no longer show up as suspect. If it isn't doing what it is supposed to it will say that they don't contain the expected contents.
When you click on the diagnostic tool and suspect version, the files that you have done this too should no longer show up as suspect. If it isn't doing what it is supposed to it will say that they don't contain the expected contents.
I'm an idiot. Sorry about that and sorry that I didn't respond sooner, when I would run the md5 generator on the files, then go back to the diagnostic tools it would say that the file did not contain the expected content. So what I did was go into the code in vbulletin and grab the function that they were using and it seemed to work, like I said it very likely could be user error but it didn't seem to create an md5 hash that matched what vbulletin would get. Sorry about the lack of explanation, I hate it when people do that