Return to doc.sitecore.com

Valid for Sitecore 6.5-7.0
Release Notes

The latest release information about the Web Forms for Marketers module version 2.3.

1.  Release History

Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.

June 23, 2014

The Web Forms for Marketers module 2.3 rev.140617 is released.

Tested with Sitecore CMS 6.6 rev.130111 (Update-3) and 7.0 rev. 140408

Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: to run the WFFM on CMS 7.0 see the workaround in the Known Issues.

Change log.
Issues resolved:

December 10, 2013

The Web Forms for Marketers module 2.3.0 rev.131126 is released.
Tested with Sitecore CMS 6.6 rev.130111 (Update-3) and 7.0 rev. 130918 (Update-2).

Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: to run the Web Forms for Marketers module on CMS 7.0, see the workaround in the Known Issues section.

Change log.
New features

Issues resolved:

January 31, 2013

The Web Forms for Marketers module 2.3.0 rev.130118 is released.

Tested with Sitecore CMS 6.6 Update-3 rev.130111 and CMS 7.0 rev. 130424.

Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: for running WFFM on CMS 7.0 see workaround in the Known Issues

Change log.
Important changes

Issues resolved:

April 3, 2012

The Web Forms for Marketers module 2.3.0 rev.120216 is released.

Tested with Sitecore CMS 6.5.0 Update-3 rev. 111230.

Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.

Important changes

Issues resolved

December 19, 2011

The Web Forms for Marketers module 2.3.0 rev.111209 is released.

Tested with Sitecore CMS 6.5.0 rev. 111123.

Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.

New Features

Important changes

Issues resolved

June 8, 2011

The Web Forms for Marketers module 2.3.0 rev.110530 is released.

Tested with Sitecore CMS 6.5.0 rev. 110602.

Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.

New Features

Important changes

Issues resolved

2.  Known issues

The following known issues are present in the latest version of the Web Forms for Marketers:

WFFM does not work on Sitecore CMS 7.0

Reference number: 382886

If you are running Web Forms for Marketers 2.3.0 on Sitecore CMS 7.0, after opening a form on the frontend or in the Form Designer, you might encounter the error message “Could not load file or assembly 'HtmlAgilityPack, Version=1.4.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”

Workaround:

  1. Add the following “runtime” section to the web.config file after the </configSections> tag:
     <runtime>
                    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
                                      <dependentAssembly>
                                                    <assemblyIdentity name="HtmlAgilityPack" publicKeyToken="bd319b19eaf3b43a" culture="neutral" />
                                                    <bindingRedirect oldVersion="1.4.0.0" newVersion="1.4.6.0" />
                                      </dependentAssembly>
                                      <dependentAssembly>
                                                    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
                                                    <bindingRedirect oldVersion="3.5.0.0" newVersion="4.5.0.0" />
                                      </dependentAssembly>
                      </assemblyBinding>
      </runtime>
  2. Save the changes and restart the website.

JavaScript errors when using Internet Explorer 10

Reference number: 387493
Various JavaScript errors may occur when posting forms created using WFFM module and running Internet Explorer 10.

Solution:
There are two possible solutions:

A web form cannot be submitted after upgrading WFFM 2.2.0  to WFFM 2.3.0

Reference number: 358042

If you upgraded Web Forms for Marketers module from 2.2.0 to 2.3.0 version, you may encounter the error message "We experienced a technical difficulty while processing your request. Your data may not have been correctly saved" after submitting a form.  The error message in the Sitecore log file is “WARN Web Forms for Marketers: an exception: has occured while trying to execute an action.”

Workaround:

  1. Go to the "/sitecore/system/Modules/Web Forms for Marketers/Settings/System/System Action" folder in the master database.
  2. Move the “/Save Actions/Tag Action“ and “/Save Actions/Register a Goal” items to the “System Action” folder.
  3. Delete all sub-folders under the “System Action” folder.
  4. Publish the site.

Web Forms for Marketers does not fully support MVC enabled sites in Sitecore 6.6. This will be fixed in a future update.

Reference number: 378012

Currently, the Web Forms module doesn't support Sitecore MVC.

Workaround:
Web forms shouldn’t be attached to items with MVC-based presentation.

MVC-based pages can’t be opened in Page Editor after installing WFFM

Note: This known issue was fixed in Web Forms for Marketers 2.3.0 rev.130118.

Reference number: 376196

In Sitecore CMS 6.6 with installed WFFM module when you open MVC-based page in Page Editor an exception may occur.

Workaround:

  1. Place the “Sitecore.Support.376196.dll” file in your “bin” folder. 
  2. Open the “App_Config\Include\forms.config” file, find the following line:

<processor type="Sitecore.Form.Core.Pipeline.InsertRenderings.Processors.GetPlaceholder, Sitecore.Forms.Core"/>

           And replace it with the following one:

<processor type="Sitecore.Support.Form.Core.Pipeline.InsertRenderings.Processors.GetPlaceholder, Sitecore.Support.376196"/>

In Sitecore CMS 6.6, a web form can’t be saved after it was edited in Form Designer from Page Editor

Note: This known issue was fixed in Sitecore CMS 6.6.0 rev. 120918.

Reference number: 368711

In Sitecore CMS 6.6, when you open Form Designer from Page Editor and edit the form, there are problems when you try to save the item after that. When clicking the Save button in Page Editor, the following message appears:
 "One or more items have been changed. Do you want to overwrite these changes?"
If you click “Ok”, the item is saved, but the web form changes lost.

Workaround:
Edit the web form components inline (directly on the web page) when possible or open Form Desiger from Content Editor or Sitecore Desktop.

Usability and Save Failure reports do not work in Sitecore 6.5.0 Update-4

Reference number: 362936

When the Web Forms for Marketers module is installed on 6.5 Update-4 or later, the user will get an exception "Report cannot be rendered" when the user try to run the Usability or Save Failure reports.

The full error message is as follows:
“Report /sitecore modules/shell/Web Forms for Marketers/Reports/Form Usability Report.mrt cannot be rendered : System.Data.SqlClient.SqlException: Hint 'noexpand' on object 'VisitEvents' is invalid.Statement(s) could not be prepared.”

The issue is caused by changes in DMS 2.0.1.

Workaround:

To resolve the issue, perform the following actions:

  1. Find the following item in the content tree:
    /sitecore/system/Settings/Analytics/Reports SQL Queries/Form Visits
  2. Remove " WITH (NOEXPAND)" from the text in the SQL field.
  3. Save the item.
  4. Repeat the steps for the following item:
    /sitecore/system/Settings/Analytics/Reports SQL Queries/Form Statistics

Installation error

Reference number: 326481

If you are upgrading from Web Forms for Marketers 2.2 using the Update Installation Wizard, you may encounter an installation error: “Error installing <package name>.” An exception occurred when installing the package. If you encounter this issue try to rename the package to a shorter name and install it again. If you still experience issues please contact Sitecore Customer Service via http://support.sitecore.net (using reference number 326481).

Form Dropout tracking does not work correctly under certain conditions

Reference number: 346464

Form Dropout tracking does not work correctly if the ASP .NET sessionState variable is set to “StateServer” mode. (346464)

Send Email Action translation issue

Reference number: 313313

When you are translating a web form, in the Send Email action you cannot set unique values in the Subject and Message Body fields for each language.

Possible workaround: If you have Email Campaign Manager installed use the Send Email Campaign Message action:

  1. Create a new Standard Message using the Email Campaign Manager.
  2. Translate the message into different languages.
  3. Add the Send Email Campaign Message action to your web form and customize it.

Cannot enter unique values for some parameters in the Send Email Action.

Reference number: 333322

Users cannot set unique values in the "From Address” and “From Name” parameters for each web form. 

Possible workaround: If you have Email Campaign Manager installed use the Send Email Campaign Message action:

  1. Create a new Standard Message using the Email Campaign Manager.
  2. Set values in the “From Address” and “From Name” parameters.
  3. Add the Send Email Campaign Message action to your web form and customize it.

Impossible to add a form in Page Editor when the Datasource Location is empty or contains path to a non-existent item

Reference number: 352647 

If the “Datasource Location” field of the “/sitecore/layout/Renderings/Modules/Web Forms for Marketers/Form” item is empty or contains a path to a non-existent item, the form inserting functionality in Page Editor may stop working. This may happen when the “/sitecore/context/home” item is deleted or renamed, because initially the field contains the path to this item.

Workaround:
Change the “Datasource Location” field value to path to an existing item to which the most of the page editor users have the read access (for example, the site root item).

Web Forms placed on the cached sublayouts don't work.

Reference number: 354946

Web Forms placed on the sublayouts with the enabled caching do not work. It is an expected behavior. When the cached sublayout is requested Sitecore returns the cached HTML output omitting the usual ASP.NET web control life cycle. For more information about the Output Caching in Sitecore CMS, see Presentation Component Reference

Workaround: Disable caching for sublayouts containing the web form.

"Send Email Campaign Message" save action does not work in Live mode

Reference number: 358115

The "Send Email Campaign Message" save action does not work in Live mode.

Workaround:

  1. Create the SendStandardMessageExt class:
    namespace Test
    {
      using Sitecore.Data;
      using Sitecore.Form.Core.Client.Data.Submit;
      using Sitecore.Form.Submit;
      public class SendStandardMessageExt : SendStandardMessage
      {
        public override void Execute(ID formid, AdaptedResultList fields, params object[] data)
        {
          if (Sitecore.Context.Site == null)
          {
            return;
          }
          bool disableFiltering = Sitecore.Context.Site.DisableFiltering;
          try
          {
            Sitecore.Context.Site.DisableFiltering = true;
            base.Execute(formid, fields, data);
          }
          finally
          {
            Sitecore.Context.Site.DisableFiltering = disableFiltering;
          }
        }
      }
  2. Add a reference to this class in the /sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions/Send Email Campaign Message item (the Assembly and Class fields of the item)