FormBuilder 0.75


We’re back with another release of FormBuilder.  This version adds two new, though related, features to the codebase.

  1. Hidden Select and Radio Values
    We have updated the code to prevent someone from viewing the source of a form and being able to see what actual values are submitted with the form data for the Selection Dropdown and Radio Button fields.  This has numerous uses, one of which is addressed with the next feature.
  2. Selectable Form Recipients
    We have enabled the form creator to be able to have a special field in the form specifying alternate form email recipients.  This means that you can create a selection box allowing the visitor to select where the form email should go.  For example, if you want to use one form for multiple purposes, the visitor can select which topic they are addressing simply by choosing a selection item and the email resulting from the form data they fill out, will be sent to the appropriate person.  Item #1 above prevents the visitor from seeing the actual email address that the data is sent to, allowing you to protect your email addresses, while exposing this functionality.  You can read more about how to use this feature, here in the FormBuilder documentation.

You can download this latest version of FormBuilder from WordPress.org.

11 Responses to “FormBuilder 0.75”

Is there a way to set the amount of characters for a form field? I would like to limit the amount of characters on a single form field. If not, this would be a nice option for future updates.

By the way, your plugin is fantastic! Thanks so much for the great tool!

James says:

Hey Chris.

We don’t have that capability yet, however it IS on our radar due to it being something we’d like to have too.

James

Lori says:

This product doesn’t work, it breaks my site as soon as it’s activated. When I hit the activate button it takes me to a new blank page & that’s all. And it kills the page for my viewers, so I can’t admin anything and they can’t view anything. I’ve tried uninstalling, reinstalling, re-downloading from the site, still, it just breaks it.
I’m very disappointed and frustrated.

James says:

Hi Lori,

I will email you personally to help with diagnosing what is going on with this for you.

James W.

Lori says:

Thanks for your help James, the version of wordpress I was using was too old 2.0.4. Upgrading was very straightforward and resolved the issue.

I appreciate your help.

Mindi says:

I like how easy it is to set up a form, but I am having a problem with it messing up my overall Theme. Is there a way to fix the width of the form so it doesn’t mess up the sidebar?
Thanks
Mindi

Mel says:

Hi, I’ve been using formbuilder for a while now but I suddenly get this error message:
Warning: session_start() [function.session-start]: open(/tmp/sess_9c3871049f1ef43968887561830eafe4, O_RDWR) failed: Permission denied (13) in /home/mamazone/public_html/mamablogue/wp-content/plugins/formbuilder/captcha/CaptchaSecurityImages.php on line 26

Can someone help?

Kenneth says:

Hi James,

Any chance you could get formbuilder to store form results in a sql table? would be tremendously appreciated!!!!

Thanks

Kenneth

Ron says:

Great Plug-in!

Just one thing: There seems to be a javascript conflict with a theme I’m testing.
http://freebiesdock.com/freemium-wordpress-theme/

It’s causing the lavalamp effect to quit working.

Any ideas on how to resolve it?

Gracias.

James says:

@Mindi: This is a bug fix we’re releasing with the next version.
@Mel: Looks like your server isn’t configured to store PHP sessions properly. You’ll want to talk to your website hosting provider about that.
@Kenneth: We do already have limited ability to do that with the latest versions of FB. You can enable it on the FormBuilder management page. (Tools – FormBuilder)

James says:

@Ron: I don’t know exactly what the problem would be. For FB, we’re simply calling the prototype plugin that comes bundled with WP, using the proper WP javascript enqueue commands. Is it possible that somehow the lavalamp effect you’re using is conflicting with our call to prototype.js?