Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This screencast is about the Webform module's new "How can we help you?" menu, which is designed toencourage new users to join the Drupal community and Drupal Association, so that they can get involved and help support Drupal and the Webform module.
The latest release of the Webform module for Drupal 8 includes a schedule email handler, support for core's quick edit module and experimental system tray, and better tools to manage external libraries.
This screencast highlights new features included in the latest release of the Webform module for Drupal 8. These new features include better support for anonymous submissions and drafts, simplified submission management, submission logging, condition email routing, emailing all users assigned to a specified role, enhanced checkboxes, image picker, map support for location element, and improved webform scheduling.
This screencast highlights new features included in the latest release of the Webform module for Drupal 8. These new features include cardinality support for multiple value elements, duplicating handlers and submissions, international phone support, scheduling the opening & closing of webform, and finally an application evaluation demo.
This release contains a security fix (see the advisory). An upgrade is recommended to all users of webform 7.x-3.x
Besides the backport of the security fix this release also includes a backport of the webform4 webform_get_submissions(). This allows other modules (ie. webform_submission_uuid) to extend the webform submission data more easily.
7.x-4.14 is a primarily bug fix release. Updating is recommended for all users of the 7.x-4.x branch.
The majority of the issues addressed in this release arose from community-written patches. A few received community review while the bulk were maintainer-reviewed. The best path to having your pet issues resolved is to write clear issue summaries, provide patches, and then review other patches with a request to receive reciprocal community review.
Recent releases represent 100's of hours of development. As of this writing, the 7.x issue queue is nearly empty. When Dan start maintaining Webform almost two years ago, there were 330 open issues and 130 open bug reports.
Recent releases represent 100's of hours of development. As of this writing, there are almost no open bugs, one open support request, and only a few open feature requests. When Dan start maintaining Webform over a year ago, there were 330 open issues and 130 open bug reports.
Recent releases represent 100's of hours of development. As of this writing, there are no open bugs, no open support requests, and only a few open feature requests. When Dan start maintaining Webform over a year ago, there were 330 open issues and 130 open bug reports.
Recent releases represent 100's of hours of development. As of this writing, there are no open bugs, no open support requests, and only a few open feature requests. When Dan start maintaining Webform over a year ago, there were 330 open issues and 130 open bug reports.
This release represents 150 hours of development. As of this writing, there a no open bugs, no open support requests, and only a few open feature requests. When Dan start maintaining webform about a year ago, there were 330 open issues and 130 open bug reports.
This release of 7.x-4.x fixes a number of bugs. Updating is recommended for all users of the 7.x-4.x branch.
If your update procedure does not clear the caches and you skipped updating to 7.x-4.6, you will need to manually clear at least the class registry. This release includes a new class, WebformConditionals, which may not be recognized by Drupal otherwise. The easiest way to clear your class registry is to clear all caches.
This release of 7.x-4.x fixes a number of bugs. Updating is recommended for all users of the 7.x-4.x branch.
If your update procedure does not clear the caches, you will need to manually clear at least the class registry. This release includes a new class, WebformConditionals, which may not be recognized by Drupal otherwise.
When a webform component is used as the "To" address or addresses for sending an e-mail, the name of the component is not sufficiently sanitized when it is displayed in the list of e-mail settings, leading to a Cross Site Scripting (XSS) vulnerability.
When a webform component is used as the "To" address or addresses for sending an e-mail, the name of the component is not sufficiently sanitized when it is displayed in the list of e-mail settings, leading to a Cross Site Scripting (XSS) vulnerability.
This release of 7.x-4.x fixes two security issues, a number of bugs, and introduces new features. Immediate updating is strongly recommended for all users of the 7.x-4.x branch. See SA-CONTRIB-2015-063 - Webform - Cross Site Scripting (XSS) for details.
When a webform is made available as a block, the node's title is used as the default block title. This title is not sufficiently sanitized, leading to a Cross Site Scripting (XSS) vulnerability.
When a webform is made available as a block, the node's title is used as the default block title. This title is not sufficiently sanitized, leading to a Cross Site Scripting (XSS) vulnerability.
This is a minor bug-fix update. Updating is recommended for all 7.x-4.x branch users.
Upgrading from Webform 3.x to 4.0
If you're upgrading from Webform 3.x, please make a database backup prior to upgrading and check that all modules that extend Webform on your site are Webform 4.x compatible. Slight differences in the class names and IDs may result in updates being needed to your site's CSS. See the API changes between 3.x and 4.x documentation for more information.
This is the first stable release of the 7.x-4.x branch. This is a major upgrade from the 7.x-3.x branch, and contains numerous bug fixes and feature enhancements.