Skip to content
PHP CSS JavaScript Shell
Find file
Latest commit be58e3e @nciske nciske Readme updates
Signed-off-by: Nick Ciske <>


=== WordPress-to-lead for Salesforce CRM ===
Contributors: stonydaddydonkeylabscom, nickciske,
Tags: crm, contact form, contactform, wordpress to lead, wordpresstolead,, salesforce, salesforce crm, contact form plugin, contact form builder, Wordpress CRM
Requires at least: 3.5.2
Tested up to: 4.3
Stable tag: 2.6.7
License: GPLv2
Donate link:

WordPress-to-Lead for Salesforce CRM creates a solid integration between your WordPress install(s) and your account!

== Description ==

WordPress-to-Lead for Salesforce CRM creates a solid integration between your WordPress install(s) and your [Salesforce CRM]( account! People can enter a contact form on your site, and the lead (or case) goes straight into Salesforce CRM: no more copy pasting lead info, no more missing leads: each and every one of them is in for you to follow up.

### Check out the screencast

You can fully configure all the different settings for the form, and then use a shortcode to insert the form into your posts or pages, or you can use the widget that comes with the plugin and insert the form into your sidebar!

Please see this [WordPress-to-Lead Demo video]( to get a full grasp of some of the power this plugin holds (though it's a bit outdated!).

#### Previous contributors:
* [Joost de Valk](
* [ModernTribe](

== Screenshots ==

1. An example form generated with WordPress-to-Lead for Salesforce CRM (with optional CAPTCHA) -- both post and widget forms are shown in the TwentyEleven theme
2. The backend administration for WordPress-to-Lead for Salesforce CRM
3. The new form editor (multiple forms, hidden fields, add new fields, thanks URL, lead source per form)

== Installation ==

1. Upload the `plugin` folder to the `/wp-content/plugins/` directory or install via the Add New Plugin menu
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Enter your Organization ID on the WordPress-to-Lead plugin configuration page.

== Frequently Asked Questions ==

= Does this plugin have any hooks or filters? Is there documentation? =

Yes, quite a few.

[Hooks & Filters Documentation](

= I'm not seeing any errors, but the entry didn't get added to Salesforce! =

To turn on in browser debugging, add a hidden field (enabled) named `debug` and set the value to `1`.

To turn on debugging via email,  add a hidden field (enabled) named `debugEmail` and set the value to `` (your email address).

Also check for debug logs at SalesForce to see if a validation rule is the culprit: `Administration Setup | Monitoring | Debug Logs`.

= What are the built in field names? Not all the fields are working when I use the Field Label in the lead edit screen? =

SalesForce is inconsistent in naming built in fields, and even misreports the names of some fields (like `MobilePhone`, which is actually `mobile`) in the customize fields screen. Generating a Web to Lead form gets you the real names, but the list below should help as well.

<strong>Built in fields</strong>

First Name	first_name
Last Name 	last_name

Title		title
Website		URL

Phone		phone
Mobile		mobile
Fax	        fax
Email		email

Address		street
City		city
State/Prov.	state
Zip			zip
Country 	country

Description 	description
Industry 		industry
Rating			rating
Annual Rev. 	revenue
Employees		employees
<strong>Other Fields</strong>
Lead Source 	lead_source
Email Opt Out 	emailOptOut
Fax Opt Out		faxOptOut
Do Not Call		doNotCall

Lead Record Type recordType

Campaign	Campaign_ID

Campaign Member Status	member_status
<strong>Name may vary (these are lookup fields), generate a Web-to-Lead form with these fields included for the actual value</strong>

SIC Code
Product Interest
Current Generator(s)
Number of Locations

= How do I setup Web to Lead/Case for my SalesForce Account? =

[Setting Up Web-to-Lead](

[Setting Up Web-to-Case](

= How do I setup a Web to Case form? =
Choose _Web to Case_ in the **Form Settings** (bottom of the form editor page).

= Where do I find my Salesforce organization ID? =
To find your Organization ID, do the following steps:

1. Log in to your account
2. Go to Setup &raquo; Company Profile &raquo; Company Information
3. You'll find the Organization ID in the lower right hand corner of your screen

= How do I use a SalesForce custom field? =

1. Go to Setup &raquo; Customize &raquo; Leads &raquo; Fields
1. If your custom field does not exist yet, create it now.
1. Find the API Name for your field (e.g. Custom_Field_Example__c). If it doesn't end in "__c" it's not the API name and will not work.
1. Add a new field to your form using the form editor on the plugin admin screen
1. Enter the API Name as the field name (left most box), then fill out the other fields normally (make sure to enable the field!).
1. Save your changes -- new submissions will now post that custom field to SalesForce.

= How do I use the checkbox field? =
Like any other field. Note that it is a single checkbox, not a checkbox list (yet).

*Note:* You must provide a value for your checkbox. Generally `1` is what you want (unless you're expecting something other than true/false in SalesForce). If you don't provide a value, your checkbox will never get sent with the form data (and even if it did, it won’t "check" the box at SalesForce as "empty" = unchecked).

_Checkbox lists and radio buttons will be in a future update._

= How do I pre-check a checkbox? =
Before you do, consider if a pre-checked checkbox (opt-out) is [really what you want to do](

If you insist on proceeding anyways: see the _Pre-check a checkbox_ example in [Other Notes](

= How do I use the select (picklist) field? =

**Hint: Use the form importer!**

Use it like any other field -- however you'll need to specify the options (and optional values) for each field using the options box (far right). You'll also need to use the "internal name" from Salesforce as your field name (see next FAQ).

The value box for a select list is the default value (the one selected on a fresh form).

/* Preferred format: */

// Use same data for display and value passed to SF

// Use different data for display and value passed to SF, require user to select something (assuming field is required)
Select One|

// Use different data for display and value passed to SF

/* Legacy Format (does not allow the use of colons in names or values): */

//Use same data for display and value passed to SF

//Use different data for display and value passed to SF, require user to select something (assuming field is required)
Select One: | name1:value1 | name2:value2

//Use different data for display and value passed to SF
name1:value1 | name2:value2

_Note: Leading & trailing whitespace is trimmed when names and values are displayed, so feel free to use spaces to make things more readable._

= How do I use the Date field? =

Choose it from the dropdown, that's all you *have* to do.

If you want to customize the date format or display/functionality of the datepicker UI, you can set the options by entering a list of options in the Options box of the field editor, one per line. Note that you must end each option with a comma, or you'll end up with a javascript error instead of a datepicker.


Default date format - Year, Month, Day
`dateFormat : 'yy-mm-dd',`

Month, Day, Year
`dateFormat : 'mm-dd-yy',`

Day, Month, Year
`dateFormat : 'dd-mm-yy',`

Day, Month, Year + Show the button panel
dateFormat : 'dd-mm-yy',
showButtonPanel: true,

More information about the datepicker options can be found here:

1. Examples:
1. API Reference:

= How do I find the "internal name" of my picklist field? =

**Hint: Use the form importer!**

Picklists in SalesForce (Web to Lead at least) are a strange beast -- you'd think you could pass the field name and SF would map it on their end... but they don't make it that easy. Instead you need to use the internal SF ID of the picklist... which looks more like: `00Nd0000007p1Ej` (this is just en example, this is not the id of your field).

Where do you find this cryptic value? You can find it in two places (that I know of):

1. Edit the field and it'll be in the URL:
e.g. ``

2. Generate a Web to Lead form with your field included and it'll be in the HTML
e.g. `TestPicklist: <select  id="00Nd0000007p1Ej" name="00Nd0000007p1Ej" title="TestPicklist">`

Then take the "name" you get (00Nd0000007p1Ej in this example) and enter that as the *field name* in your form editor. Yes, you enter this obtuse string of digits instead of the human readable field name (i.e. MyCustomField__c).

= How do I use the HTML field? =

1. Optionally enter a label (field will display full width if a label is not entered.
2. Enter HTML code in the options box.

_Note: You cannot use the HTML box to enter a custom field, as only "known" fields are submitted to salesforce and HTML fields are not submitted (just displayed). Be careful to avoid the `<form>` or `</form>` tags in an HTML field as they will likely break your form._

= How do I use a lookup field with a picklist field in the plugin? =

**Hint: Use the form importer!**

Since it's a lookup field the value of the options has to be SalesForce's <strong>internal id</strong>, not the value you'd think it would be. Otherwise when Jane Doe gets married and becomes Jane Smith you'd break all the links to her user.

Basically, you need to generate a Web to Lead form in Salesforce and grab the option values from the HTML it generates.


Find the lookup field. This is the bit you're looking for:
`<option value="00Nd0000007p1Ej">Joe Schmoe</option>`
`<option value="00Nd0000007p1aB">Jane Doe</option>`

00Nd0000007p1Ej (just an example) is the SF internal ID for that choive. Enter that as the value in your pick list field options like this:

`00Nd0000007p1Ej:Joe Schmoe|00Nd0000007p1aB:Jane Doe`

= How do I change the order of input fields? =
Right now, the only way of ordering input fields is by changing the position numbers on the right hand side of the input fields table in the admin settings. Drag and drop re-ordering is on the roadmap.

= How do I apply my own styling to the form? =
Instructions for disabling or overriding the CSS are included on the plugin settings screen (see Style Settings).

= What does "Use WPCF7 CSS integration" do? =
This option adds the WPCF7 classes to the form fields so you get the WPCF7 CSS styles applied (if that plugin is also activated).

= Is it possible to make multiple forms with this plugin? =
Yes, version 2.0 introduces this feature.
Version 2.1 allows you to duplicate forms to reduce re-entering data.
Version 2.5 allows you to import Web-to-Lead forms from Salesforce.

= How do I change the Lead Source that shows up in Salesforce? =
You can easily change this by going into the WordPress-to-Lead admin panel and, under form settings, changing the Lead Source for that form. Daddy Analytics uers can set this to blank to have it automatically filled.

= I want to include the full URL the form is embedded on, but SF limits the lead source to 40 characters -- how would I do that? =

The lead source supports using %URL% as the lead source (which will be replaced with the form embed url), but SF inexplicably limits the lead source to 40 characters.

Here's how to route around that:

How to use:
1. Create a custom URL field at SalesForce (or Text field that holds more than 255 characters if you desire). A URL field makes it clickable in the lead detail view(s).
2. Replace URL_CUSTOM_FIELD_NAME below with the name of the custom field you setup in SalesForce,
   it will be something like EmbedUrl__c
3. Add a hidden field to each form with the same field name (e.g. "EmbedUrl__c")
4. Profit

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_embedurl', 10, 3 );
function salesforce_w2l_field_embedurl( $val, $field, $form ){

    // Target a specific field on all forms
    if( $field == 'URL_CUSTOM_FIELD_NAME' )
         $val = esc_url("http://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']);

    return $val;


= Can I change the submit button? =
Of course you can! Go into the WordPress-to-Lead admin panel and, under Form Settings, change the text from the default "Submit" to whatever you'd like it to be!

= Will I lose data if I upgrade to 2.0? Do I need to change anything? =
Nope! The plugin will migrate your existing data to the new format. Your existing form will become Form 1 and be output by the [salesforce] shortcode).

= How do I show my other forms? =
Just use `[salesforce form="X"]` (X is the form number).
Or select a form number in the widget.

= I put my campaign name in the Campaign_ID field but it's not working =
The Campaign_ID field requires the Campaign ID -- the name will not work. To find the Campaign_ID, go your the campaign page and look in the URL bar for the ID:


In this example, 621U000000IJat is the Campaign_ID -- make sure you use the ID from the campaign you want the lead attached to and not the example ID shown here.

= Does the return/thanks URL have to be on my site? =
No, as long as it's a valid URL it will work. However it should be an absolute URL regardless of where it is located.
e.g. not just /thanks/

= Is there a limit to how many leads can be captured? =
While the plugin has no limits, SalesForce does limit API calls per day:

_The daily limit for Web-to-Lead requests is 500. If your organization exceeds its daily Web-to-Lead limit, the Default Lead Creator (specified in the Web-to-Lead setup page) receives an email containing the additional lead information._

See also: [How many leads can we capture from our website?](

= Can I hide the admin message insisting I enter my organization id? =

Yes. Be careful -- that's there to remind you that the plugin doesn't do much without one.

Add this to functions.php or a custom plugin (see other notes for more detailed instructions):

add_filter( 'salesforce_w2l_show_admin_nag_message', '__return_false', 10, 1 );

== Filters and Hooks ==


* These should be placed in your active theme functions.php or a functionality plugin.
* Never edit a plugin directly (unless you understand the implications of doing so).
* You can use Pluginception to create a custom plugin for these to make them independent of your theme:

= Filters =


Change the API url the plugin posts data to. Passes the form type (lead or case)

add_filter( 'salesforce_w2l_api_url', 'my_w2l_api_url', 10, 2 );

function my_w2l_api_url( $url, $form_type ){
	return '';


Provide your own validation logic for each field.

_An error array is passed in, along with the field name, submitted value, and field configuration (type, default value, required, etc)._

Here's an example of blocking common free email providers:

add_filter('sfwp2l_validate_field','block_non_biz_emails', 10, 4);

function block_non_biz_emails( $error, $name, $val, $field ){

	if( $name == 'email' ){

		$non_biz_domains = array( '', '', '', '' );

		$domain = array_pop(explode('@', $val));

		if( in_array( $domain, $non_biz_domains ) ){
			$error['valid'] = false;
			$error['message'] = 'Please enter a business email addresss.';


	return $error;

You can add to the $non_biz_domains to block other providers as well.


HTML of the form before it's returned to WordPress for display


Change from name (user confirmation)


Change from email (user confirmation)


Change from name (admin notification)


Change from email (admin notification)


Adding this code to your functions.php file will add 3 emails to the list. You can add as many as you want and each will get an admin notification email.


function salesforce_add_emails( $emails ){

//uncomment line below to remove site admin


return $emails;



Allows you to filter (append, prepend, modify) the email message content sent to the user or admin(s).

add_filter('salesforce_w2l_cc_user_email_content','salesforce_filter_user_message', 10, 1);

function salesforce_filter_user_message( $message ){

	$message = 'Before the user message' . "\r\n\r\n" . $message . "\r\n\r\n" . 'After the user message';

	return $message;


add_filter('salesforce_w2l_cc_admin_email_content','salesforce_filter_admin_message', 10, 1);

function salesforce_filter_admin_message( $message ){

	$message = 'Before the admin message' . "\r\n\r\n" . $message . "\r\n\r\n" . 'After the admin message';

	return $message;



**salesforce_w2l_returl_{Form ID}**

Allows you to filter the value of a field before it is output to dynamically populate it with a value, auto set it based on another value, etc.



// Filter Return/Success URL on a specific form
// salesforce_w2l_returl_{Form ID}
add_filter( 'salesforce_w2l_returl_1_tester', 'salesforce_w2l_returl_1_tester_example', 10, 1 );
function salesforce_w2l_returl_1_tester_example(  $returl ){

	return '';



**salesforce_w2l_success_message_{Form ID}**

Allows you to filter the contents of the success message before it is output to dynamically populate it with a value, auto set it based on another value, etc.



// Filter Success Message on a specific form
// salesforce_w2l_success_message_{Form ID}
add_filter( 'salesforce_w2l_success_message_1_tester', 'salesforce_w2l_success_message_1_tester_example', 10, 1 );
function salesforce_w2l_success_message_1_tester_example(  $success ){

	return 'Testing 123';



**salesforce_w2l_field_value_{Form ID}_{Field Name}**

Allows you to filter the value of a field before it is output to dynamically populate it with a value, auto set it based on another value, etc.

Note that the second filter requires you to replace {Form ID} and {Field Name} to be replaced with the relevant form id and field name.

If you need access to the field or form settings in your filter you can use:

`$field = salesforce_get_field( $field_name, $form_id );`

`$form = salesforce_get_form( $form_id );`


// Pre-check a checkbox

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_value_precheck_example', 10, 3 );

function salesforce_w2l_field_value_precheck_example( $val, $field, $form ){

	$form_id = 1; // form id to act upon
	$field_name = 'checkboxfield__c'; // API Name of the field you want to auto check

	if( $form == $form_id && $field_name == $field && ! $_POST )
		return 1; // or whatever the value of your checkbox is

	return $val;


// Store HTTP referrer in a field (this is not 100% reliable as the browser sends this value to the server)

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_value_referrer_example', 10, 3 );

function salesforce_w2l_field_value_referrer_example( $val, $field, $form ){

	$form_id = 1; // form id to act upon
	$field_name = 'referrer__c'; // API Name of the field you want to autofill

	if( $form == $form_id && $field_name == $field ){
		if( isset( $_SERVER['HTTP_REFERER'] ) ){
			return $_SERVER['HTTP_REFERER'];

	return $val;


// Autofill fields based on thew query string (using Google Analytics tracking variables in this example)

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_value_querystring_example', 10, 3 );

function salesforce_w2l_field_value_querystring_example( $val, $field, $form ){

	$form_id = 1; // form id to act upon
	$field_name = 'source__c'; // API Name of the field you want to autofill
	$qs_var = 'source'; // e.g. ?source=foo

	if( $form == $form_id && $field_name == $field ){
		if( isset( $_GET[ $qs_var ] ) ){
			return $_GET[ $qs_var ];

	return $val;


// Autofill a user's country based on IP

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_value_geoip_example', 10, 3 );

function salesforce_w2l_field_value_geoip_example( $val, $field, $form ){

	// Based on this plugin:
	// Adjust this code to the one used by your geo detection plugin

	if( !function_exists( 'geoip_detect2_get_info_from_current_ip' ) ) return;

	$form_id = 1; // form id to act upon
	$field_name = 'country__c'; // API Name of the field you want to autofill

	if( $form == $form_id && $field_name == $field ){

		$userInfo = geoip_detect2_get_info_from_current_ip();
		//$val = $userInfo->country->isoCode; // e.g. US
		$val = $userInfo->country->name; // e.g. United States


	return $val;


// Autofill a date

add_filter( 'salesforce_w2l_field_value', 'salesforce_w2l_field_value_date_example', 10, 3 );

function salesforce_w2l_field_value_date_example( $val, $field, $form ){

    $form_id = 1; // form id to act upon
    $field_name = 'mydatefield__c'; // API Name of the field you want to auto check

    if( $form == $form_id && $field_name == $field && ! $_POST )
        return current_time('Y-m-d'); // or whatever date format you want

    return $val;



Allows you to remove the form action.

// Remove Form Action
add_filter( 'salesforce_w2l_form_action', 'salesforce_w2l_form_action_example', 10, 1 );
function salesforce_w2l_form_action_example(  $action ){

	return '';



Allows you to alter the lead source (per form or globally).

// Alter Lead Source
add_filter( 'salesforce_w2l_lead_source', 'salesforce_w2l_lead_source_example', 10, 2 );
function salesforce_w2l_lead_source_example(  $lead_source, $form_id ){

	if( $form_id == 1 )
		return 'Example Lead Source for Form #1 on page id #'.get_the_id();

	return $lead_source;



Allows filtering of the [wp_remote_post]( arguments (e.g. extend the timeout, increase redirect limit, etc).

add_filter( 'salesforce_w2l_post_args', 'salesforce_w2l_post_args_example' );

function salesforce_w2l_post_args_example( $args ){

	$args['timeout'] = 10; // http timeout in seconds
	return $args;



Allows filtering of the post data before it is sent to SalesForce.

add_filter( 'salesforce_w2l_post_data', 'salesforce_w2l_post_data_example', 10, 3 );

function salesforce_w2l_post_data_example( $post, $form_id, $form_type ){
	error_log( 'POST ARGS = '.print_r( $post, 1 ) );
	$post['test'] = 'test';
	return $post;


Suppress the organization id missing nag message (return false).

add_filter( 'salesforce_w2l_show_admin_nag_message', '__return_false', 10, 1 );

= Actions =


Allows you to do something (read only) with the post data before it's submitted to SalesForce.

e.g. Send it to another API, log it to a database, etc.

If you need to change the data, use the _salesforce_w2l_post_data_ filter.

add_action('salesforce_w2l_before_submit', 'salesforce_w2l_before_submit_example', 10, 3 );

function salesforce_w2l_before_submit_example( $post, $form_id, $form_type ){
	error_log( 'BEFORE SUBMIT '.print_r($post,1) );


Allows you to do something (read only) with the post data when there is an error submitting to SalesForce.

e.g. Notify someone via email, log it somewhere, etc.

add_action('salesforce_w2l_error_submit', 'salesforce_w2l_error_submit_example', 10, 4 );

function salesforce_w2l_error_submit_example( $result, $post, $form_id, $form_type ){
	error_log( 'ERROR SUBMIT ' . print_r($result,1) );


Allows you to do something (read only) with the post data after it's submitted to SalesForce.

e.g. Send it to another API, log it to a database, etc.

add_action('salesforce_w2l_after_submit', 'salesforce_w2l_after_submit_example', 10, 3 );

function salesforce_w2l_after_submit_example( $post, $form_id, $form_type ){
	error_log( 'AFTER SUBMIT '.print_r($post,1) );

== Changelog ==

= 2.7 =
* Fix widget constructor to be compatible with WP 4.3 (thanks Steven Stevenson)
* Store form configuration data in one (non auto-loaded) option per form to avoid option trimming and memory issues for larger installs (sponsored by SPS commerce)

= 2.6.7 =
* Add setting to remove WP CF7 javascript to fix it hijacking forms with WP CF7 CSS integration turned on
* Add setting to enable SSL verification of SalesForce SSL cert when connecting to the API
* Use protocol-less URLs for external resources -- fixes insecure content issues (thanks Charles Augello)
* Pass $post to `salesforce_w2l_api_url` and `salesforce_w2l_cc_admin_email_subject` (thanks Haruhiko Kobayashi)

= 2.6.6 =
* Add setting to make it easier to CC multiple people on new submissions
* Add settings to specify the from name & from email for emails sent by the plugin (note: other plugins may override these settings via filters)
* Add examples for filtering field values
* New ad artwork/links

= 2.6.5 =
* Use esc_url_raw instead of sanitize_url
* Update tested with version

= 2.6.4 =
* Add Date field with jQuery datepicker functionality
* Add email field type (a text field with auto-validation)
* Update ad artwork
* Add filter for retUrl (redirect URL)
* Add filter for success message

= 2.6.3 =
* Fix incorrect form id/anchor bug that broke scrolling to the form after submit

= 2.6.2 =
* Fix "Wrong parameter count for trim()" bug in form editor.

= 2.6.1 =
* Fix javascript error when not using placeholder label layout
* Make colons after labels optional (see form settings near the bottom to disable)

= 2.6 =
* Add filter to allow suppression of the admin screen nag about a missing organization id
* Fix bug that was adding a colon after checkboxes and HTML field labels
* Fix checkbox label alignment on top-aligned forms
* Fix Top Aligned label radio option not being checked when selected (admin)
* Add label layout option for sidebar forms
* CSS tweaks to improve field spacing and improve default sidebar layouts
* Restrain overly wide select fields in sidebar forms
* Beautify CSS formatting consistent

= 2.5.6 =
* Further improve auto detection of new options format

= 2.5.5 =
* Fix bug in auto detect of new options format that could break fields with newlines and pipes mixed together

= 2.5.4 =
* Improve importer to allow forms that have been modified to be imported (thanks Mark Loeffler)
* Fix new hidden fields becoming text fields upon save (typo)

= 2.5.3 =
* Added a new picklist options format: newlines and pipes (vs pipes and colons) to allow colons to be used in names/values (and make it easier to read)
* Make all input tags self closing e.g. `<input />` for xhtml compatibility
* Disable W3TC object caching when captcha is used (until a cache friendly captcha solution is added)
* Add Content-Type header to form POST

= 2.5.2 =
* Tested up to 4.0
* Add plugin icon
* Form id 1 can now be duplicated
* Duplicate forms have (copy) appended to the form name to clearly mark them as the duplicated form

= 2.5.1 =
* Refactor `salesforce_cc_admin` to allow a customizable subject (translators: affects localization strings)
* Email admin on submission errors as well as successes, append result data
* Add `salesforce_w2l_post_data` filter (see 'Other Notes')
* Add `salesforce_w2l_before_submit`, `salesforce_w2l_error_submit`, `salesforce_w2l_after_submit` actions (see 'Other Notes')

= 2.5 =
* FAQ: Clarify the mess that is picklist fields/names
* Fix label with when using top aligned labels
* Add clearfix to sf_field container
* Fix PHP notice when deleting a form
* Added importer option (finally) to make it easier to generate W2L forms at SF then auto import them

= 2.4.4 =
* Allow debug mode to be set (was getting set to 0 before submit)
* Remove debugEmail from user email fields
* Update debug info and add built in field name info on FAQ

= 2.4.3 =
* Fix PHP warnings due to switch to strlen for required field validation

= 2.4.2 =
* Fix bug where "0" (zero) was not considered a valid value for required fields

= 2.4.1 =
* Fix regression bug where checkboxes turn to text fields due to capitalization of option label

= 2.4 =
* Allow lead_source to be a form field (i.e. don't overwrite value if it already exists)

= 2.3.9 =
* Allow filtering of wp_remote_post arguments
* Add picklist FAQ regarding field names
* Add Multi-Select field (aka MultiPicklist)
* Refactor code to properly handle strings and arrays as field values (to support multi-selects)
* Add embed URL example code to FAQ

= 2.3.8 =
* Add lead source back into admin email
* Add filter for lead source

= 2.3.7 =
* Fix issue where deleting form title made the edit link disappear
* Fix settings url in alert to go to settings tab
* Add filter to allow form action to be removed

= 2.3.6 =
* Fix issue with OID and other fields being appended to the user confirmation email
* Add `salesforce_w2l_cc_user_suppress_fields` filter to allow supression of fields in the user confirmation email

= 2.3.5 =
* Readme improvements

= 2.3.4 =
* Fix bug in load_plugin_textdomain call
* Readme improvements
* Change value input size to match label field

= 2.3.3 =
* Fix confusing wrapping on form editor on very wide screens (reported by cindybou)
* Change name of and add note to filters and hooks section

= 2.3.2 =
* Add filter for field values
* Add salesforce_get_form and salesforce_get_field helper functions

= 2.3.1 =
* Version number bumps

= 2.3 =
* Allow some settings to be overridden per form (Success Message, Captcha, OrgId, etc)
* Support for option to use placeholders instead of labels (per form)
* Remove newlines in form HTML that were being converted to <br> upon output
* Add Settings link to plugin list screen
* Grey out non enabled fields in admin
* Set a default checkbox width as some themes think input{ width: 100% } is a good idea...
* All default CSS now uses relative sizes
* Prevent multiple submission of form data (even if it's the same form id on the page multiple times)
* Remember "send me a copy" between submits
* Defined DONOTCACHEPAGE if captcha is enabled
* Fix PHP notices when form is submitted
* Update ads and landing page URLs
* Add support links to plugin list page, restore plugin link
* Load text domain on plugin init, add .pot file

= 2.2.5 =
* Fix PHP warnings and notices

= 2.2.4 =
* Add email and captcha error to settings page.

= 2.2.3 =
* Added filter to user and admin email content

= 2.2.2 =
* Fix deprecated (in PHP 5.3) ereg_replace functon in captcha lib

= 2.2.1 =
* Fix untranslatable string (invalid email)
* Set input height to auto (18px causing issues with themes containing plentiful padding)
* Change "Daddy Analytics Webform URL" to "Daddy Analytics Web to Lead URL ID"
* Fixed slashes issues in field labels, select options and field labels in emails
* Test using new deploy script:

= 2.2 =
* Bug: Fixed checkboxes not retaining checked state after submit
* Bug: Only output DA JS when token has been entered
* Wrapped all output in a div tag to allow styling of success and error messages
* Added #anchor to action to keep form on screen after submit when not the first item in a page (may not work in older versions of IE)
* Add per field validation filter and error output (thanks to for sponsoring this feature)
* Added tabs to plugin settings page
* Moved form list to its own tab (vs the bottom of the settings screen)
* Added syntax highlighting to defaut CSS example on new Styling tab
* Tested and working in WordPress 3.8

= 2.1.1 =
* Fixes a bug that caused the organization id field to be hidden on new installs

= 2.1 =
* Add drop down field type (thanks jbuchbinder)
* Improve form HTML (thanks jbuchbinder)
* Add from and reply to options for emails (thanks jbuchbinder)
* Add delete checkbox to form editor (thanks jbuchbinder)
* Add HTML field type (thanks jbuchbinder)
* Add simple checkbox field (thanks jbuchbinder)
* Add ability to duplicate forms (thanks jbuchbinder)
* Add WPCF7 CSS integration option (thanks jbuchbinder)
* Add wrapper divs with class names to visible fields
* Remove Powered by SF for all forms
* Make required field indicator consistent with message
* Comments to lead option (thanks simonwheatley)
* Global DaddyAnalytics settings added to make integration easier
* Added filters to aid in extending the plugin
* Hide fields with no label in admin and user email
* Required fields now trim whitespace from the value before validation (e.g. a space or tab is no longer a valid value)
* Fixed checkbox/label alignment
* Readme improvements
* Added daily limit info to FAQ
* Removed previous contributors no longer involved in plugin development, added credit to readme
* Refactored and cleaned up codebase
* Added filters to allow code based overrides of select features (see Other Notes for details)
* Added Web to Case option (per form setting)
* Fixed first field being added having a duplicate position to last field
* Select fields can have a default value set

= 2.0.3 =
* Captcha image now works on subfolder installs (e.g. /wordpress/)
* Removed captcha dependence on including wp-load.php

= 2.0.2 =
* Small formatting fixes (checkbox spacing and submit button CSS)

= 2.0.1 =
* Fixed issue with captcha URL being broken on some installs
* Added several filters, including one to allow editing of the distribution list for new lead notifications and one to allow filtering of the form HTML before output
* Fixed bug where captcha would wrap outside form on some themes
* Fixed bug where forms other than id 1 did not show field labels in emails
* Fixed bug causing unexpected output upon activation
* Fixed bug that caused form to always be in 'sidebar' mode
* Now supports more than 1 form per page
* Forms now have a unique ID for use with CSS and jQuery: salesforce_w2l_lead_[ID] and salesforce_w2l_lead_[ID]_sidebar
* Fixed a bunch of notices and warnings

= 2.0 =
* Improved internationalization
* Multiple forms can be created and inserted via shortcode or widget
* Spam protection (with optional captcha)
* Fixed "Cannot use object of type WP_Error as array" bug
* Fixed bug that showed successful submissions as "Failed to connect to"
* Hidden fields can now be used
* Campaign_ID can now be set per form
* Widget now hides description text upon submission
* Admins can receive an email of submissions
* Users can request a copy of their submission (if enabled)
* Custom return/thanks URL can be defined per form
* Country field added

= 1.0.5 =
* Fix in backend security, preventing XSS hack in the backend.

= 1.0.4 =
* CSS fix for when sidebar widget and contact form are on the same page.

= 1.0.3 =
* Fix in email verification.

= 1.0.2 =
* One more escape, plus a check to see whether the email address entered is valid.

= 1.0.1 =
* Added escaping around several fields to prevent XSS vulnerabilities.

= 1.0 =
* Initial release.

== Upgrade Notice ==

= 2.7 =
This version changes how option data is stored (it will auto migrate data to the new format leaving the old format available in case a rollback is needed).

= 2.6.1 =
The default CSS changed in the 2.6 release. If you've customized the form output, double check your form styling after upgrade.

= 2.6 =
The default CSS changed in this release. If you've customized the form output, double check your form styling after upgrade.

= 2.5 =
Now features an importer: Generate your Web-to-Lead form at Salesforce, provide the HTML code to the plugin, then automatically import it into WordPress to Lead in a *single click*!

= 2.2 =
Includes new CSS rules: make sure to update any custom CSS files with the new *.sf_field span.error_message* rule.
Changes how error messages are output. Please review your *error message* on the settings screen to make sure it still makes sense in the new context.

= 2.1 =
This version includes most of the functionality in the "jbuchbinder" GitHub fork many users installed. Most users should not experience any issues upgrading. However, the "current date" field is not included in this release.

= 2.0 =
This version fixes a bug that caused the plugin to appear broken, despite sending leads to
Something went wrong with that request. Please try again.