Admin Tools 2.0 released, with many new features. Read on for the complete list.
We are please to announce that Admin Tools Core and Admin Tools Professional version 2.0 was just released. This release delivers exciting new features and addresses Joomla!™ 1.6 compatibility issues.
This release was normally scheduled for Thursday, but we decided to release it today. The reason was the release of Joomla! 1.6.1 by the Joomla! project. Unfortunately, due to technical issues with cURL and mooTools, it was impossible to use Admin Tools 1.1.2 to upgrade to this release. Admin Tools 2.0 addresses these issues. Given the high priority issues fixed in Joomla! 1.6.1, we decided to release our software earlier in order to assist you with your site upgrades.
[div class="download" class2="typo-icon"]You can download the software from our Downloads page. If you are an ATPRO or AKEEBADELUXE subscriber make sure that you have logged in to the site before attempting to access the downloads page, otherwise you won't be able to see and download the Professional release.[/div]
Want the best protection for your Joomla!-powered sites? Protect all of your sites now costs less than a night at the movies! Go Professional today and experience the difference.
Sincerely,
Nicholas K. Dionysopoulos
Lead Developer, AkeebaBackup.com
What's new?
More security! (Admin Tools Professional)
- Malicious User Agent filtering
- CSRF / Anti-Spam (reverse CAPTCHA) protection
- Bad Behaviour (including full support for Project Honeypot IP blacklisting) integration
- Geographic Blocking: block site visitors based on the country or continent they come from
- Automatic block for IPs repeatedly triggering security exceptions. Configurable triggering level and length of their blocking.
- DFI (Direct file inclusion) detection - DFIShield
- Uploads scanner (UploadShield) blocks uploaded files with suspicious names or containing PHP code anywhere inside them
- Protection against the most common XSS attacks (XSSShield)
- Send an email on failed Super Administrator access attempt
- Show the IP of the user accessing the site on all emails sent by Admin Tools
- Send an email when the Web Application Firewall detects a security exception
- Improved SQLiShield feature, catches even more SQL Injection attempts
- Block front-end access to all Super Administrators
More ease of use!
- Scheduling configuration from within the component page (Professional version)
- A checkbox to select all/none items in Master Password page
- Integration with Joomla! 1.6 ACL
- Per-user ACL for Joomla! 1.5
- Can now automatically purge old security log entries based on a schedule (Professional version)
- HTTPS-izer: Convert all links on the page to use the https:// protocol when the site is accessed over SSL
- Old .htaccess now backed up as .htaccess.admintools
- .htaccess Maker: "index.php to root redirection" now supports three settings: off/standard/alternate to workaround restrictions on some servers
- Improved language handling on Joomla! 1.6 (mostly talking about the toolbar buttons)
Less bugs!
- The Joomla! update status module and the system plugin were not installed in the Core release
- Saving the Component Parameters would reset everything on Joomla! 1.5
- Security exceptions logging didn't include the URL (thanks Ervin)
- Passing a text key to the tp query parameter would bypass the tp=1 detection (thanks Ervin)
- PHP 5.2 on IIS will return a copy of the object when $o = Factory::method() is used instead of $o =& Factory::method()
- System plugin: the language file wouldn't be loaded on Joomla! 1.6
- Module parameters wouldn't be translated in Joomla! 1.6
- Upgrading Joomla! was impossible on servers lying about their cURL support status
- Enabling the System - Admin Tools plugin on a Joomla! 1.6 site would cause the site to fall back to English due to a Joomla! 1.6 bug/feature
- Changing the database prefix and collation would not work on MySQL 4.1 hosts. Disabled these features for MySQL versions earlier than 5.0.
- Changing the database prefix could FUBAR your Joomla! 1.6 site because of a bug/feature/change of behaviour in the Joomla! Framework. A workaround is now in place.
- Would not upgrade to Joomla! 1.6.1