FormBuilder 0.60


We are very excited to announce the release of FormBuilder 0.60, featuring many new features you have been requesting.  Here’s a brief run-down:

  • Feature: Internationalization Support
    We have incorporated the ability to support internationalization on the forms you now create.  This included numerous database updates as well as code modifications.  See further notes on this below.
  • Feature: New Field Type: Followup URL
    Allows you to redirect visitors to an alternate URL in the event that the form is filled out successfully.
  • Feature: Duplicate Form Checking
    The plugin will now keep track of the most recently submitted form data, preventing the exact same information from being submitted again from the same IP.
  • Feature: Redirect ONLY Module
    Added a new module (found in the ACTION field of the form) which allows the form to simply redirect the user to another page, rather than actually submitting form data or sending an email.  Useful to add a quick button to a page, in order to redirect users somewhere else.
  • Bug Fix: WordPress in a Subdirectory
    Previously FormBuilder was experiencing problems when installed on a WordPress site in a subdirectory of the document root. (ie www.yourdomain.com/blog/wordpress)  This bug has now been fixed, and FormBuilder should work well regardless of where in the filesystem WordPress is installed.
  • Bug Fix: Prototype.js Library
    FormBuilder has been reconfigured to use the WordPress built-in prototype.js library, rather than including it’s own.  Should help to provide better compatibility with other plugins which may use the same library.

Important Notes:

The introduction of internationalization support in the FormBuilder plugin resulted in some unexpected consequences due to bugs found in PHP version 4.xx.  In certain situations, PHP warnings will be displayed on the form when non-ascii characters are used.  This is actually due to a bug in PHP v. 4.xx and is not resolved until PHP version 5.xx.  The warning in question looks like this:

Warning: cannot yet handle MBCS in html_entity_decode()! in /var/www/yourdomain.com/htdocs/blog/wp-content/plugins/formbuilder/formbuilder.php on line 379

Unfortunately, because of the fact that this is a PHP error, there is not a lot we can do to resolve it.  More details can be found here.  If you are experiencing this error, we suggest the following solutions:

  • Install or activate PHP 5.xx
    As your website host to upgrade your version of PHP to 5.xx.  As of July 13, PHP 4 is becoming obsolete and PHP 6 is soon to arrive.
  • Disable warning notifications on your site
    While the warnings will still exist, they will not display on your pages.

We hope you like the improvements and we would love to hear any feedback you might have.

Click here to download FormBuilder from the WordPress Plugin Database.

This entry was posted on Thursday, June 26th, 2008 at 1:42 pm and is filed under FormBuilder, WordPress. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “FormBuilder 0.60”

  1. Kotyk.com » Formbuilder 0.60 Says:
    June 26th, 2008 at 6:34 pm

    [...] FormBuilder 0.60 has been released. To Do: Add to Digg | Add to Del.icio.us | Print This Post | Email to a friend | Leave a Comment [...]

  2. Allen Says:
    August 14th, 2008 at 3:57 pm

    I upgraded to this latest version of the plugin and it broke one of my other plugins (smoothgallery). Because smoothgallery controls content that is on the front and center of my homepage, I just had to deactivate my formbuilder plugin until I can get this resolved, which in turn breaks all my forms on the site. I have tried to find the older versions of your plugin so I can roll back, but have not been able to find them. Are they archived somewhere?

  3. Sheldon Kotyk Says:
    August 14th, 2008 at 9:16 pm

    Hi Allen, I’ll get James to send you a zip but what error were you getting? I’d rather get that error fixed up for you? Are you using php4?

Leave a Reply