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 release reverts some of the changes made in 7.x-1.12 as they proved to be unstable. This also changes the form_builder_cache in an incompatible way (Sorry there is no other way to do this) - So if you are upgrading from 1.12 please make sure to … :
This release fixes a syntax error in the migration to 7.x-1.11. Please read the release notes of 7.x-1.11 carefully if you are upgrading from versions prior to 7.x-1.11.
This release restores PHP 5.3 compatibility and includes minor API changes. Please check it for compatibility (with other form_builder based modules) before updating and as always: Make backups!
This release adds a new dependency on ctools. Please be sure this module is available to your Drupal site before running update.php (or drush updb).
This release of Form Builder adds a few new pieces of functionality, such as the ability to clone fields, clicking to add fields from the palette, and highlighting fields.
This release also fixes several bugs, upgrading is recommended for all users.
This release of Form Builder adds a few new pieces of functionality, such as the ability to clone fields, clicking to add fields from the palette, highlighting fields, and support for Webform "unique" validation.
It also addresses a number of bugs and adds compatibility with jQuery 1.9 and higher. Upgrading is recommended for all users.
This release of Form Builder focuses on data integrity issues. In particular, it handles reordering of new elements and nesting within fieldsets in more robust ways. This upgrade is recommended for all users of Form Builder.
This release of Form Builder focuses on data integrity issues. In particular, it handles reordering of new elements and nesting within fieldsets in more robust ways. This upgrade is recommended for all users of Form Builder.
Major release since the 0.9 version. Lots and lots of changes. While all users are recommended to upgrade, proceed with caution when upgrading from the 0.9 version. This version is stabilized and is suitable for use with the Webform project.
Change list:
#1404988: Set default option keys to numbers and increment intellegently.
#1472546: Chrome scrolls to top of page after every drag.
#1446642: Unable to add fields to newly created fieldset when a description is present.
Major release since the 0.9 version. Lots and lots of changes. While all users are recommended to upgrade, proceed with caution when upgrading from the 0.9 version. This version is stabilized and is suitable for use with the Webform project.
Change list:
#1404988: Set default option keys to numbers and increment intellegently.
#1472546: Chrome scrolls to top of page after every drag.
#1446642: Unable to add fields to newly created fieldset when a description is present.
The 0.9 release of Form Builder makes numerous improvements and brings the module closer to a production-level module. Note that Form Builder still contains numerous bugs and sub-modules that are not complete. Use of this module in production is not recommended.
The 0.9 release of Form Builder makes numerous improvements and brings the module closer to a production-level module. Note that Form Builder still contains numerous bugs and sub-modules that are not complete. Use of this module in production is not recommended.
This release of Form Builder fixes a major problem when saving form elements back to the form cache and offers better support for new releases of Options Element module.
This version of Form Builder makes the following improvements:
The Form Builder palette block is no longer required to be enabled. Form builder will put the palette in the main content area if the block is not enabled, allowing for better compatibility with themes and easier set up.
Better hover in and out recognition
Better handling of empty fieldsets
Adds icons and CSS for "email" and "markup" fields
Initial public release of Form Builder. Do not use this module in a production environment. It's suggested to not enable the Node Form support at all, as it will seriously cripple the configuration of node types at admin/content/node-type/[type-name].