First of all, 2.0 is great. I love using it and I'm excited for everyone to be able to use it on.... drumroll....Friday, April 10th.
Yes, we (finally) set a release date for it. 2.0 is so easy to use and it's jam-packed with shiny new features. I hope you love it.
Update: Read more about the v2.0 release
There are some things I want you to know before (or right after) updating to 2.0, just to help the update go smoothly. These are the big things you should know about:
- Email Notifications
The way email notifications send in 2.0 is more like the way emails send from your email account. When you put multiple addresses in the "To" field, only one email sends to all the recipients. Prior to 2.0, a separate email would be sent to each recipient in the 'Recipients' box. So what does this change mean for you? If you do not want your email recipients to see all other recipient email addresses, move the recipients from the 'To' box to the 'BCC' box after updating to 2.0.
Formidable 2.0 uses Google's new reCaptcha, which is much cooler and cleaner than the old reCaptcha. If you are using the reCaptcha field on any of your forms and are currently using global keys, you will need to set up a Site Key and a Private Key for each site where you use the reCaptcha field.
- frm_where_filter hook
The frm_where_filter hook functionality has been updated to improve security. This is one of the most commonly used hooks, so please check your site to see if you're using it. If you are appending a string onto the $where value, like this:Formidable Forms is the best WordPress Form Builder plugin. Get it for free!
$where .= 'add to where string';
then this will no longer work. If you're using this hook to set a completely custom where string like this:
$where = 'my custom where string';
then that will continue to work in 2.0. Specifically watch out for the .= in your function. Previously, we had two examples in our docs that used this. They were the "Show unique values" example and the "Starts with" example. The functionality from these examples has been added to 2.0, so if you were using either of these examples, all you need to do now is remove the custom code, then go into your View and add a filter that says "Field Name is unique" or "Field Name starts with...".
So, those are the big things you should be aware of. If you want to know about the smaller changes that might affect you, keep reading.
Inline submit button
If you're using this custom CSS to put your submit button inline, you can remove the custom CSS (it won't work anymore since the form HTML has changed). Then go into your form's Settings and set the Submit Button Alignment to Inline. In order to get the submit button to line up just right, you'll usually need to go into your Formidable > Styles > Buttons and adjust the submit button margin.
The "Track referrer information and pages visited" option in the Formidable Global Settings has been removed in order to reduce the load on each page. If this is something you have been using and you really want to keep using it, just let us know in the help desk. We will consider putting it into an add-on.
Field input ids
The HTML in radio button, checkbox, and scale fields has changed a bit. The input id now uses the field key instead of the field ID. So it used to be like this:
but now it looks like this:
FrmEntry::getOne() field keys
Before 2.0, the FrmEntry::getOne() function returned an array of entry values referenced with both the field id and key. The structure was like this:
$entry->metas['fieldkey'] = 'hi';
$entry->metas = 'hi';
For purposes of reducing memory load, the extra field key metas have been removed. If you are using them in custom code, you can add this line along with your code:
Just a heads up, if you are not running the most current version of Twilio when you update Formidable, your Twilio settings will not carry over.
If you're using any $frmpro_* globals in custom code, it's time to remove them. They were deprecated in 1.07.05 and have been completely removed in 2.0. A common one that you may want to check for in your custom code is global $frmpro_form.
We have switched to using all static function calls now, so if you're using any of our PHP hooks on your site and you want to avoid deprecated messages, you can get rid of the non-static function calls. A common one is:
global $frm_entry; $test = $frm_entry->getOne( $entry_id );
Now, you would just use:
$test = FrmEntry::getOne( $entry_id );
Enough with the boring stuff, I want to briefly mention my three favorite features in Formidable 2.0.
- Style templates
In 2.0, it is so much easier to make your forms look just the way you want. You can create multiple style templates in order to give each form a unique look and feel. You may want to insert a form in your sidebar, for example, and you want to hide the field labels and set the submit button to 100% width. In the past, this would require custom code. Now, you can just create a new style template for the form in the sidebar. On top of that, we are offering many more styling options in 2.0.
- Repeating fields
In the past, if you wanted to have a group of, let's say 5 fields and you wanted them to repeat up to 10 times, you would have to add at least 50 fields to your form plus conditional logic on your fields. In 2.0, you can just add a Repeating Section to your form and add the handful of fields that you want to repeat. It's that easy.
- Form Actions & Emails
I love the new look of the form actions, especially the emails. Email actions are much cleaner and offer more options so it feels like creating an email from your email account.
Disclaimer: This post doesn't cover all of the cool features added in 2.0. We'll add a separate post with more info on the new features.