Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
In addition to this security vulnerability, the following changes have been made since the 6.x-1.0-alpha1 release:
Bad 'page arguments' in l10n_groups module
- Menu updates. Use the Drupal 6 built in ways to invoke functions from include files. No need for a custom wrapper.
- Fixed missing access argument on export tab, which resulted in it not showing up.
- Fixed badly updated form in export screen, now includes form_state as mandated in Drupal 6.
- Move Tar.php check to a real hook_requirements() check as suggested in @todo.
- Add potx version compatibility check to make sure people run with the right potx version.
#321637 by myself: support for disabled projects; makes it possible to discontinue project translations (not looking for new releases but keeping old data) and maintaining suggested projects not yet picked up by the server but known.
Instead of t() we should use the return value of get_t() in install functions
- #324012: added toggle for "Show All" in admin settings
- #324012, #324668: fixed issue with CCK fields not showing
- #324584: fixed incorrect assignment of default class values in the ToC
This update to Webform fixes a critical bug regarding sending e-mails (all e-mail content was blank). It also fixes a few other minor bugs and allows optgroups to be used in select lists.
The sixth maintenance and security release of the Drupal 6 series. Only fixes for security vulnerabilities and other bugs have been committed. New features are only being added to the forthcoming Drupal 7.0 release.
This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the security announcement: