ISPConfig 2.2.24 is available for download. This ISPConfig release adds support for CentOS 5.2 and OpenSuSE 11.0. A new interface for cronjobs and support for mod_python has been added. Several minor bugs were fixed. Detailed Changelog ------------------ - Added: support for OpenSuSE 11.0. - Added: Support for CentOS 5.2. - Added: support for Cron Jobs. - Added: Support for Python scripts (.py) via mod_python. - Added: .biz and .info to the whois search. - Added: Translations for "Create DNS-MX" and "Traffic MB". - Added: Alphabetical sorting of the sites in move website tool. - Update: Updated PHP to version 5.2.6. - Update: Updated ClamAV to 0.93.1 - Update: Updated Spamassassin to 3.2.4. - Update: Updated Dutch language Files. - Changed: Allow multiple MX records with same priority. - Changed: The enforcing user quota patch, introduced in ISPConfig 2.2.23 is disabled now by default. To enable it, change the variable $go_info["server"]["force_user_quota"] to 1 in config.inc.php - Changed: Enable XML in ispconfig PHP if libxml2-dev is installed. - Changed: Set loglevel to "warn" and umask to "0022" in suphp.conf. - Changed: Disabled TRACE and TRACK methods in vhosts. TRACE and TRACK are HTTP methods which are used to debug web server connections. In addition, it has been shown that servers supporting the TRACE method are subject to cross-site scripting attacks, dubbed XST for "Cross-Site Tracing", when used in conjunction with various weaknesses in browsers. An attacker may use this flaw to trick your legitimate web users to give him their credentials. - Bugfix: Prevent /var/www/sharedip/index.html to be overwritten when upgrading/installing. - Bugfix: Bug #22 fixed, changed files are now UNIX encoded. - Bugfix: Bug #73 fixed. - Bugfix: remove CRs from automatically sent mails. - Bugfix: Fixed bug in mailsuer login when the dovecot user@domain login is used. - Bugfix: Added same name regular expression test in mailuser login then it is used in main login. - Bugfix: Fixed vsftpd support on Libc6 systems. - Bugfix: Added missing newline at the end of manual additions in the configuration files. - Bugfix: Removed unnecessary dot at the end of CNAME records in the DNS Manager. Download -------- http://www.ispconfig.org/downloads.htm Forums ------ http://www.howtoforge.com/forums Installation Instructions ------------------------- Download the ISPConfig-2.2.24.tar.gz from sourceforge.net: http://prdownloads.sourceforge.net/ispconfig/ISPConfig-2.2.24.tar.gz?download Installation on the shell as root user: tar xvfz ISPConfig-2.2.24.tar.gz cd install_ispconfig ./setup The installer automatically detects the installed ISPConfig version and performs an update.
Thanks Till for the work. I will install it soon. One question, why did you not update ClamAV to the latest version 0.93.3 ?
Thanks so much Till !! Been waiting for this to upgrade along with upgrading from Centos 5 to 5.2. Is there a recommended process for that? Should I upgrade ISPconfig first or update Centos first? I also notice some users on the Centos forums suggest a reboot before and/or after updating Centos, you think this is required? Thanks again Till and Falko.
I have no experience with upgrading Centos, but I would update centos first and then update ISPConfig, so that ISPConfig will use the updated libraries when it compiles the binaries during update process.
Instal ok but minor bug Update to 2.2.24 ok on mandriva 2007.1 but Tools > Whois > info about domain .biz, select dont hold value when submit button is clicked and i dont get info about my domain. Is hosted on ispconfig, any idea where can i get log about whois action?
Update from ISPConfig 2.22 to 2.2.24 successful I just successfully updated one Debian Etch server from ISPConfig 2.2.22 to 2.2.24. Later this week i will update my other server as well. Thanks for the work!
does that mean there is a new interface now where we can implement cron jobs via ISPConfig? If so, where do we find it? All I see right now is a check box which says cron job.
1. You *have* to reboot *each* time a kernel is updated. 2. You *should* update regularly, not just from one major version to next major version. If you wait that long with updating you are asking for trouble. (Because of security holes that you don't fix and because an update from one major version to another may have a few more glitches than going with all the minor updates in-between.)
I updated from 2.2.23 on CentOS 5.2. Just fine. I noticed that you don't reinvoke the certificate creation process and thus the certificate doesn't get replaced. Thank you. What gets replaced, though, are all the changes that I made with the form editor. This is all reset to the install default, which is a pity. Is there a way to backup these data and reapply after the update? I figure this might not be easy as there could be new forms/fields/values and if I reapply the backup the new functionality would get wiped from the interface. Anyway, if you have some idea how to achieve this I would be grateful for sharing. And, should I add this as a feature request either in this forum or on the bugtracker?
what happends whit users logged on when doing upgrade? Im running Debian 4 etch, i just download the update 2.2.24, and just untar it an run ./setup ? is there any question under the upgrade? do i have to reboot ore restart any services after the upgrade ? Regards Marcus Lindberg
