The forums/includes/md5_sums_* files are used to store md5sums of the files for vB
and other modules so that Admins can run the "Suspect File Versions" diagnostic to find out which files have been modified (or have not been properly upgraded) from the base module install.
Because vBG doesn't distrubute an md5_sum_vbgallery.php file with the distro, all vBG files fail the diagnostic.
I'm attaching a simple shell script that you can use to see how the md5_sums files are supposed to look. It's a bit of a hack but it was fast to code.
gen_vb_md5.sh /path/to/vBG/source/forums /path/to/vBG/source/forums/includes/md5_sums_vbgallery.php
Note: Because of the way that vb
:admincp/diagnostic.php works, vBG will not be able to take full advantage of the md5sum file version checking code without adding a hack to the diagnostics.
However, I've filed an enhancement request with vB
(see: Diagnostics md5sums version header for use by "Suspect File Versions" diagnostic - vBulletin Community Forum
) to make the code more robust and allow for third party devs to take advantage of it. However, doing so would require a change to each of your file headers.