New virtual-server 3.61, virtual-server-theme 6.1

Howdy all,

I’m rsyncing Virtualmin virtual-server version 3.61 and the Virtualmin Framed Theme virtual-server-theme version 6.1 into the repositories as we speak (and a few minor updates of a few plugins). It’s a nifty new update, with lots of bugfixes. But, the biggest news is in the theme. I’ve back-ported a few interesting bits from the in-progress AJAX theme into Virtualmin Framed Theme, so it’s got quite a lot of changes (though all small enough, and well-tested enough, to make me reasonably confident it isn’t going to break for anyone). The changes are mostly cosmetic, but we’ve been long overdue for a cosmetic update, so it’ll be a nice change anyway. Also, most theme-generated HTML is now roughly W3C valid, and Jamie and I have been making great progress on converting Webmin and Usermin over to using the ui-lib calls (which means that in the next release or two of Webmin and Usermin, pretty much everything will be valid XHTML 4.01). This won’t be noticeable, in general, but it can make a difference in edge cases, like odd browsers, screenreaders and such, so I’m happy to see it nearly complete. Accessibility is an area where systems management tools are historically very weak, but we’d like to change that in Webmin/Virtualmin/Usermin.

Changes in Virtualmin since version 3.60:

[li]Updated the Piwik script installer to version 0.2.9, phpCOIN to 1.4.4, Joomla to 1.5.6, phpMyAdmin to, dotProject to 2.1.2, SugarCRM to 5.0.0g, Wordpress MU 2.6, Gallery to 2.3-rc-1 and 1.5.8, TWiki to 4.2.2, Coppermine to 1.4.19, Trac to 0.11.1, Bugzilla to 3.2rc1, Movable Type to 4.2, Zikula to 1.0.2, WordPress to 2.6.1, MediaWiki to 1.13.0, Drupal to 5.10 and 6.4, TikiWiki to 2.0, and ZenPhoto to 1.2.[/li]
[li]When the virtualmin --help command is run, it now outputs a list of all available API commands with short descriptions, broken down into categories.[/li]
[li]Extra administrators can now have contact email addresses, which can be used when sending email to all domain owners. These can be set via the web interface, or the command-line API.[/li]
[li]Added a Module Config option in the advanced section to change the path for the API helper command, and improved automatic selection of a path if the default directory /usr/sbin is not writable.[/li]
[li]Third-party content styles can now be deleted by the master admin from the Content Styles page.[/li]
[li]Added the --default-ip flag to, to revert to a shared IP address.[/li]
[li]Custom links can be limited to virtual servers with a specific template if you have any custom templates defined, for more control over when each link is displayed.[/li]
[li]Backups now include any custom template used to create virtual servers, which allow domains to be restored even on systems that do not yet have the original templates.[/li]
[li]When a virtual server’s IP address is changed, the addresses of all alias domains are updated to match.[/li]
[li]The Website Options page now has a field to enable matching all sub-domains for the virtual server’s website, via a * DNS entry and Apache server alias directive. This can also be enabled for some or all domains using the command-line API.[/li]
[li]If a backup is taken on a system that uses ~/mail for user folders and restored on one using ~/Maildir, they will be properly converted during the restore (and vice-versa).[/li]
[li]When a domain is restored on a new system, the MySQL socket file path and options that reference the home directory in its php.ini file are updated to match the new system.[/li]
[li]Preserve encrypted passwords when backing up domains, in case they don’t match the plaintext password stored by Virtualmin. Also, have validation report an error in the case of a mismatch.[/li]
[li]Re-organized the custom links page to move editing of each link into a separate form, and allow links to be limited to virtual servers with some feature enabled.[/li]

Note that the Joomla 1.5.6 update is a serious security update–many folks have already addressed that with an ad hoc Install Script that Jamie has posted a few times in the issue tracker over the past couple of days, but if you’re still running Joomla 1.5.4, you need to update ASAP.

As always, if you run into any problems, let us know in the ticket tracker.

Joe<br><br>Post edited by: Joe, at: 2008/08/22 01:56