Sorry, maybe I should have explained how to use it. It's a command-line script, so you have to run it on a command line. You can get a command line by logging into your server via SSH or Putty, or by installing Python on your local computer and running the script in a DOS box or terminal window. The command to run (using Linux forward-slashes; convert them to backslashes on Windows) is:
./md5xml.py '1.5.22' ../Joomla_1.5.22-Stable-Full_Package-bz2
The format of this is:
./md5xml.py = the script you're running
'1.5.22' = the version of Joomla for which you're creating a new XML file
../Joomla_1.5.22-Stable-Full_Package-bz2 = the path to the directory where the complete unzipped copy of the Joomla installation file is found
The above command will output a file named 1.5.22.xml in the same directory from which you ran the script. You can copy that file into your Version Verification Tool installation where the other XML files are found to allow you to verify your Joomla installation.
Thanks so much for helping us out! Yes, we got a bit behind on VVT, and that's pretty unexcuseable when users need to know if their new installation is setup properly. We just updated to version 1.7 of VVT, which includes XML files for 1.5.21 and 1.5.22. We removed 1.5.0-1.5.9 from this release due to the size of the zip going over 2mb, which is the upload limit on a decent % of servers.
In the future, we may include our (PHP based) XML generator as well as your Python script, if you're ok with it. There are a ton of other uses that VVT could be used for (checking individual extensions, for instance) that we may try to put into a release. With multiple scripts to create the XML file, it may help users to create the necessary check files on their own to test what they want.
Again, really appreciate the assistance, and any feedback you have, we'd love to hear it!
alzander wrote:In the future, we may include our (PHP based) XML generator as well as your Python script, if you're ok with it.
It's fine with me for you to include the script I made in a future release. I didn't put it under a license, so it's public domain. I know it might have helped people if I had written my script in PHP rather than Python, but I figured a general purpose command line script is still fairly useful, and I thought it might be faster for me to do it in Python. Since it's a command line script, on some server configurations it could be called from PHP (or any other language) like this:
system("md5xml.py '1.5.22' ../Joomla_1.5.22-Stable-Full_Package-bz2");
It can also be called from a shell script that iterates through several available Joomla releases and creates all their XML files in a single batch operation; that's why I made it a general purpose shell script.
Thank you for the Version Verification Tool! It helped me double/triple-check my Joomla installation's file integrity in a difficult debugging problem I ran into. I'm happy to give something back as a thank-you!
I created an initial PHP version called md5xml.php for use on servers where Python is not an option. The PHP version is not (yet) as configurable as the Python version, but if you read through the code you can probably figure out where to modify it to get it to work for you.
timblack1 wrote:I created an initial PHP version called md5xml.php for use on servers where Python is not an option. The PHP version is not (yet) as configurable as the Python version, but if you read through the code you can probably figure out where to modify it to get it to work for you.
Again, you're free to use the code as you see fit--it's in the public domain.