The Mollom module v1.0 for Drupal 7 has been officially released by the drupal developer. The release for Mollom delineates the changes incorporated in the Drupal 7 module to ensure the functionality under all situations so as to sync with the latest code. The major improvements to core are:
• Making it possible to alter the form validation for handlers during validation. This allows the module to conditionally show a CAPTCHA if its a spam
• Corrected and improved the caching of $form_state in the case of form validation errors, previews, multi-step ("wizard") forms, and other scenarios in which a form is rebuilt or re-rendered, and might have new or updated state information that should be cached. Removed the auto-rebuilding magic of the 'storage' property, to cache most of $form_state when form caching is enabled, and ensured that form constructors can already decide on caching and rebuilding.
The Drupal 7 update for Mollom necessitated to fully remove plenty of code that was previously required to work around limitations and bugs in Drupal's Form API.
Along the way, more than 2,200 test assertions for the Mollom module's automated unit tests were made in order to ensure that its functionality works correctly in almost every possible scenario. Effectively, Mollom's module tests are quite possibly the most aggressive Form API tests for Drupal, as it uses almost all of its advanced features.
• Making it possible to alter the form validation for handlers during validation. This allows the module to conditionally show a CAPTCHA if its a spam
• Corrected and improved the caching of $form_state in the case of form validation errors, previews, multi-step ("wizard") forms, and other scenarios in which a form is rebuilt or re-rendered, and might have new or updated state information that should be cached. Removed the auto-rebuilding magic of the 'storage' property, to cache most of $form_state when form caching is enabled, and ensured that form constructors can already decide on caching and rebuilding.
The Drupal 7 update for Mollom necessitated to fully remove plenty of code that was previously required to work around limitations and bugs in Drupal's Form API.
Along the way, more than 2,200 test assertions for the Mollom module's automated unit tests were made in order to ensure that its functionality works correctly in almost every possible scenario. Effectively, Mollom's module tests are quite possibly the most aggressive Form API tests for Drupal, as it uses almost all of its advanced features.
