FormBuilder v. 0.53
FormBuilder version 0.53 is a minor feature and bug fix release. Two issues have been addressed and are as follows:
- Feature: Suppression of Errors
We found that it is sometimes necessary to suppress errors on forms when posting GET data to them. By default, when GET variables are posted to the form in order to predefine fields, the remaining required fields will display their error messages, indicating that the user still must fill out those fields. You can now suppress those errors by including the &suppress_errors=true variable in the URL. - Bug Fix: Forms on Protected Pages
It was brought to our attention that forms were still appearing on pages which had been password protected in WordPress. We have fixed the bug to only allow forms to be displayed once the correct password has been entered.
You can download FormBuilder v. 0.53 here: FormBuilder 0.53
2 Responses to “FormBuilder v. 0.53”
WP Development Blog
View our latest plugins and themes on our blog. You may also subscribe to our RSS feed.
Plugins
- Comment Count
- Event Calendar
- FormBuilder
- SendFeed
- and more...
- FormBuilder 0.89 Released
- FormBuilder Now On GitHub
- FormBuilder v. 0.86
- FormBuilder v. 0.852
- FormBuilder 0.84 Released
- FormBuilder 0.83 Released
- Events Calendar 0.26 Released
- Events Calendar 0.25 Released
- Comment Count v1.20
- Historical Comment Count
- Genesis said: Well we can cirofnm that moh.gov.np has blocked...
- Ozge said: Pray GOD Blesses me so i can Bless oethrs every...
- Jung said: Thank you for the good wiruetp. It in fact was a...
Latest Posts
Latest Comments
I get this error when I try to deactivate FormBuilder
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘formbuilder_deactivation’ was given in /var/www/web29/web/wp-includes/plugin.php on line 164
Warning: Cannot modify header information – headers already sent by (output started at /var/www/web29/web/wp-includes/plugin.php:164) in /var/www/web29/web/wp-includes/pluggable.php on line 391
Hi Loren,
Thank you for sending this in. We’ll be looking into it and will get back to you.
James