Diagnostics for Joomla 
Version
1.5.9 (last update on Mar 21, 2010)
Rating
Compatibility
Votes
19
Favoured
39
License
Other
Non-Commercial
Type
Views
82713
Date Added
20 September 2006
byhenkinzuidamerika on January 6, 2010
Despite what other people noticed this utility is capable of checking (any) joomla release. Only a small configuration needs to be done to diagnostic.php (from line 13)
$jversion = '1.5.9';
$mosConfig_absolute_path = '/usr/local/www/site' ;
$task = 'generate';
(change the absolute path to where your joomla is)
on line 232 add:
$opath = $mosConfig_absolute_path ;
(just before this piece of code:
if(is_null($opath)){
return;
}
)
Now run diagnostics.php from your web browser, and it will create a new joomla_$jversion.txt for you. (You might want to delete any md5 lines from the tmp and log directory).
Now change back the $task on line 15 to:
$task = '';
and you can check your joomla installation.
$jversion = '1.5.9';
$mosConfig_absolute_path = '/usr/local/www/site' ;
$task = 'generate';
(change the absolute path to where your joomla is)
on line 232 add:
$opath = $mosConfig_absolute_path ;
(just before this piece of code:
if(is_null($opath)){
return;
}
)
Now run diagnostics.php from your web browser, and it will create a new joomla_$jversion.txt for you. (You might want to delete any md5 lines from the tmp and log directory).
Now change back the $task on line 15 to:
$task = '';
and you can check your joomla installation.
byMiggl on October 15, 2009
While the functionality seems increadibly useful, it really is only as useful as long as it is kept up to date with Joomla. The most current version I was able to find for download was for Joomla 1.5.9. Unfortunately, at the time of the review, the current Joomla version is 1.5.14, so it isn't really useful.
I do look forward to an updated version - I would then rate it 5/5. Right now I have to give it only a 2/5 since it isn't functional for the latest Joomla release.
I do look forward to an updated version - I would then rate it 5/5. Right now I have to give it only a 2/5 since it isn't functional for the latest Joomla release.
byRiverside on July 9, 2009
This is a decent utility. It's not an extension. Unzip the file, upload both to Joomla home directory, and use browser to go to diagnostics.php. It's that simple. The only problem with this utility is that I think too many people may not understand that if you have already done a lot of customizing on your site, the tool will pick up on it, showing files as corrupt or changed. I have many that have been changed. I changed them, so I know to ignore that.
The multiple notices of file errors most people are seeing here, and not believing are more than likely the following error:
"File does not contain _VALID_MOS OR _JEXEC."
Go ahead and choose not to believe it. But don't come to any of us crying when your site is cracked!
That missing line leaves you open to vandals, and a LOT of extensions don't include it. There are SO many files in Joomla itself, AND in the extensions, it's not hard to believe how easy it is for this to be forgotten by our well meaning developers, but it's BOUND to happen.
This is a GREAT tool to use as soon as Joomla is installed, and after each plugin installation. Install, run this, correct the errors, and run it again. You'll see those errors disappear. I've done it.
This is a FANTASTIC extension, but you have to understand how to use it. It says my configuration.php file is either corrupt or has been changed. That's not an error. I HAVE changed it. I know what I did, so I know I can ignore that error.
All this tool does, is all it claims to do. Check files against a list and set of criteria, predetermined in the text file that comes with it.
Also, you HAVE to make certain the verison you are running MATCHES the Joomla version you are testing TO A "T!"
The multiple notices of file errors most people are seeing here, and not believing are more than likely the following error:
"File does not contain _VALID_MOS OR _JEXEC."
Go ahead and choose not to believe it. But don't come to any of us crying when your site is cracked!
That missing line leaves you open to vandals, and a LOT of extensions don't include it. There are SO many files in Joomla itself, AND in the extensions, it's not hard to believe how easy it is for this to be forgotten by our well meaning developers, but it's BOUND to happen.
This is a GREAT tool to use as soon as Joomla is installed, and after each plugin installation. Install, run this, correct the errors, and run it again. You'll see those errors disappear. I've done it.
This is a FANTASTIC extension, but you have to understand how to use it. It says my configuration.php file is either corrupt or has been changed. That's not an error. I HAVE changed it. I know what I did, so I know I can ignore that error.
All this tool does, is all it claims to do. Check files against a list and set of criteria, predetermined in the text file that comes with it.
Also, you HAVE to make certain the verison you are running MATCHES the Joomla version you are testing TO A "T!"
byhongkongkev on January 21, 2009
I downloaded this extension today and discovered it is nice and simple because it compares the files/MDF signature of your Joomla installation against a supplied list of files/MDF's within a text file. The drawback is the text file is dated 5 Feb 08 and a simple check at doc.joomla.org with the Joomla v1.5 release dates revealed v1.5 was released on 22 Jan and 1.5.1 released on 8 Feb. It therefore currently checks only v1.5; subsequent Joomla upgrades have different files. There are no MD5 lists at doc.joomla.org (the MD5 info only refers to a single number for the package itself) and you will need to use a standalone MD5 checker to generate a comparative text file after expanding an original full (not upgrade) ZIP Joomla package of the installed version.
bywdstation on January 2, 2009
It showed me almost every single file has some kind of error. But I don’t believe that.
I don’t think it’s working properly. Also it showed me some missing files which were not missing.
I don’t think it’s working properly. Also it showed me some missing files which were not missing.
byDavidBoggitt on December 25, 2008
I tried to do a diagnostics for J1.5.8 site, but got a warning on literally every file! Can't believe that's right so I've a horrible feeling that this project is dead... which is an awful shame! Please bring it back!
P.S. I tried it on a fresh install of 1.5.8 too and had the same problem...
P.S. I tried it on a fresh install of 1.5.8 too and had the same problem...
byyaani on April 29, 2008
You should run this diagnostic test on every new Joomla installation. It will tell you if any files were corrupted or are missing during the ftp, the ftp log doesn't always show the missing or corrupted files. It can save you a lot of hair pulling when things don't work right because one little file somewhere is incomplete.
byNixim on April 6, 2008
usefull little app. I have seen and used.
Man was I shocked. I reinstalled Joomla.
Man was I shocked. I reinstalled Joomla.
Well let me start by saying I have downloaded tons of files here and have never wrote a review yet. However this one needs one. This works awesome right out of the box. Showed me alll the errors I didn't know I had and a few that I new I had to have. AWESOME AWESOME get it now..
byChaosKaizer on December 19, 2006
its not that hard to used this tool. Just upload the two(2) files into your joomla root and run it on your http://mysite/diagnostic.php
it will check the md5 hash value of each joomla default files and also verified the file header (_VALID_MOS) if not set that u get warning.
this is very useful, try it
it will check the md5 hash value of each joomla default files and also verified the file header (_VALID_MOS) if not set that u get warning.
this is very useful, try it
byduncans on September 21, 2006
I like this a lot.
One thing I did was change the file name from diagnostics.php to something else, or it could give someone a shopping list of files to try. Maybe even better to uninstall it when done or add some password protection.
One thing I did was change the file name from diagnostics.php to something else, or it could give someone a shopping list of files to try. Maybe even better to uninstall it when done or add some password protection.





