Products
Packages [expand] [collapse]
Services
Released in version
4.29.2
4.29.1
4.29.0
4.28.0
4.27.1
4.27.0
4.26.0
4.25.1
4.25.0
4.24.3
4.24.2
4.24.1
4.24.0
4.23.0
4.22.0
4.21.0
4.20.0
4.18.0
4.17.0
4.16.0
4.15.1
4.15.0
4.14.1
4.14.0
4.12.0
4.11.0
4.10.0
4.9.1
4.9.0
4.8.1
4.8.0
4.7.0
4.6.1
4.6.0
4.5.0
4.4.4
4.4.3
4.4.2
4.4.1
4.3.0
4.2.2
4.2.1
4.1.0
4.0.1
4.0.0
3.1.0
3.0.0
2.1
2.0.0.2
1.1.4.9000
1.1.2.9000
1.0.0.9000

Release notes for Episerver updates

This overview lists the latest changes included in Episerver updates delivered as NuGet packages and services. You can filter the information for products and versions, bug fixes and features. As a developer working with Episerver solutions, use the information to decide which updates to apply to your project. See Installing Episerver updates for information on how to install.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Changes in EPiServer.Forms

Item type
From date
To date
Items/Page
Id Type Title Released
AFORM-2552
  Need to set "Cache-Control: no-store" in header of init script request

1. Install Forms, create a page with form.
2. View the page in View Mode.
3. See the request /EPiServer.Forms/DataSubmit/GetFormInitScript (in network tab of Chrome dev tool)
4. Expected: Cache-Control: no-cache, no-store
5. Actual: Cache-Control: private

Version/s: EPiServer.Forms 4.29.2;
Aug 06, 2020
AFORM-2536
  Generating a report is saved on disk instead of in blob can cause problems for non-sticky load balanced environment

The problem is when generating a report specificly the call

https://www.abc.se/EPiServer/EPiServer.Forms.UI/DataExporting/PrepareExport

It saves the file to the disk using Path.GetTempPath() eg the systems temp path. That means that the callback in a non sticky load balanced enviroment most likely will hit another instance when trying to get the file.

A good option for where to save it is in the blob storage if there is one configured.

In order to use Azure blob storate
1. Add config to web.config

<episerver.framework>
  <blob defaultProvider="azureblobs">
      <providers>
        <add name="azureblobs" type="EPiServer.Azure.Blobs.AzureBlobProvider,EPiServer.Azure"
              connectionStringName="EPiServerAzureBlobs" container="mycontainer"/>
      </providers>
  </blob>
...

2. In Forms.config add setting to use the provider

<episerverforms dataExportBlobProviderName="azureblobs">

Version/s: EPiServer.Forms 4.29.1;
Jun 30, 2020
AFORM-2539
  Bug in Episerver Forms v.4.28
Steps to Reproduce

1. Create a new Form.
2. Add a element textbox.
3. Add submit button
4. Go to viewmode and inspect submit button.
5. Check value of class attribute

Expected: value is "Form__Element FormExcludeDataRebind FormSubmitButton"
Actual: Empty.

Steps to Reproduce

In the SubmitButtonElementBlock.ascx (modules_protected\EPiServer.Forms\EPiServer.Forms\Views\ElementBlocks), we set the class attribute two places in the tag. First with the result of GetValidationCssClasses and then after with if/else check for the image. These have to be combined to one class attribute.

Version/s: EPiServer.Forms 4.29.1;
Jun 30, 2020
AFORM-2544
  Double Slash in Link Placeholder URL in the Form Notification Email
Environment Information

VM: SVMCV437719
VM Creds: EPI Creds

CMS site: http://www.alloy.com/
CMS Login: http://www.alloy.com/util/login.aspx
CMS Creds: admin/Admin001!
Zendesk Ticket Number 437719

Steps to Reproduce
  1. Load Papercut Client App
  2. Start Alloy Site
  3. Login in Credentials
  4. Go to About Us > Contact Us Page
  5. Select a file to upload
  6. Select Submit
  7. View Email In Papercut
  8. Click link in the email. Double slashes in URL.
Customer Impact Statement

Customer claims that the double slash in the email causes an issue with access to the asset through the CDN. So the idea is to remove the double slash issue to resolve the issue and concern.

Issue Description

When the form is using a file upload feature and we set a link placeholder for that content in the notification email it appears as a double slash for the URL.

Example would look like this.

https://www.iata.org//contentassets/a396b155cbbc49dfa7aa7e0591e5da08/uploaded-files/003_637168546944627060.jpg

Attachment List

List any attachments that are pertinent to investigation that have been included

Version/s: EPiServer.Forms 4.29.1;
Jun 30, 2020
AFORM-2450
  Default placeholder text displayed instead of entered text in multi-step forms

When a visitor enters rich text in the place of a placeholder in multi-step forms, the entered text is usually displayed in the next step of the form. In some cases, this can cause performance issues. Select Disable placeholders replacement in the Settings tab of rich-text form elements to not display entered text in the following step. Instead, the default placeholder text will be displayed.

Version/s: EPiServer.Forms 4.29.0;
May 06, 2020
AFORM-2499
  ASP.NET automatically sets SameSite cookie header, so Forms cannot update some cookies in a new browser

ASP.NET automatically sets the SameSite=None attribute for a cookie sent from a client (generated HttpCookie instances). Forms updates the cookie instance and sends it back to client.

However, with browsers that support the cookie's SameSite attribute (2019 draft), if we have cookie with the SameSite=None and the attribute Secure is not set (the connection also has to be secure if Secure is set - with proper SSL certificate), the cookie is rejected (not updated) in browser.

Prerequisites
  • IIS server runs on .NET Framework 4.7.2 or later.
  • Google Chrome version 80 or later.
  • Enable the #same-site-by-default-cookies and #cookies-without-same-site-must-be-secure features in chrome://flags
Steps to Reproduce
  1. Create a multi-step form (2 steps should be sufficient) and add it a page.
  2. Visit the page.
  3. Open DevTools to monitor requests (in Network tab) and cookies (in Application tab).
  4. Delete all cookies with format EPiForm_<Form_GUID>_<.EPiForm_VisitorIdentifier> (e.g. EPiForm_3371b7db-7c19-4154-8dd2-491bb0047f9c_02178fb9-4d0f-48b4-b681-1860f6c0b926:cmsadmin).
  5. Submit the first form step.
  6. A new request is sent and its response headers should have a header like Set-Cookie: EPiForm_337...b926:cmsadmin={"formGuid":"3371...d403867","isFinalized":false}; path=/; HttpOnly and this cookie should be added.
  7. Submit the final step.
  8. The Set-Cookie header will have a new attribute SameSite=None. The cookie's new value (e.g. "isFinalized":true) is not updated.
  9. (Optional) Submit any in-between steps. The Set-Cookie header will also have a new attribute SameSite=None.
Expected

All Set-Cookie headers for EPiForm_<Form_GUID><.EPiForm_VisitorIdentifier> should _not have SameSite=None, and the cookie is updated.

Actual

All Set-Cookie headers after the first submit request have SameSite=None attribute, and the cookie is not updated.

Version/s: EPiServer.Forms 4.29.0;
May 05, 2020
AFORM-2526
  Firefox: When reloading page, form doesn't return to first step

Note: This bug doesn't happen with Chrome, Edge and IE; only Firefox

Prerequisite: Form1 has Step1, Text, Step2, Number and Submit button. Form1 is on Page1.

Steps to reproduce
1. View Page1.
2. Press the Next step button.
3. Reload Page1.

Expected:
Form1 should go back to Step1.

Actual:
Form1 is on Step2.

Version/s: EPiServer.Forms 4.29.0;
May 05, 2020
AFORM-2524
  In Readonly mode, hide Reset button on Mapping tab

Steps to reproduce:
1. Install Forms and add some external systems (MAI connectors, etc.).
2. Create a new form.
3. Map the form to an external data source.
4. Publish the form.
5. Create a Swedish version of the form.
6. Edit the Swedish version of the form.
7. Go to the Mapping tab.

Expected:
Hide or disable the Reset button.

Actual:
The Reset button looks disabled, but you can still click it.

Version/s: EPiServer.Forms 4.29.0;
May 05, 2020
AFORM-2479
  Form elements should be rendered properly in viewmode

Prerequisite: A form has a field dependency configuration.
When the page is loaded, the elements are shown/hidden based on dependency configuration. Normally, this works as expected. But, in some cases (such as network latency), when the page loads, all elements are shown but, 1 second later, some elements are hidden.

The current behavior is to show all elements by default. Then, the Field Dependency Tracker runs. When it finishes, a form's elements will be shown/hidden depending on the configuration.

The solution: Hide elements with valid field dependency settings by default by adding 'hide' class while rendering. When the form is loaded and JS code is executed, the Field Dependency Tracker is triggered to show/hide form elements based on dependency settings against form submission data.

Version/s: EPiServer.Forms 4.28.0;
Mar 31, 2020
AFORM-2469
  Improve Form element to fullfill the WCAG 2.0 level AA compliance

According to the discussion at https://www.yammer.com/emvp/#/threads/show?threadId=1083938207

We need to improve form element behavior, such as input validation, so the user can fix any errors.

  • If there is an error when submitting, set the input element's aria-invalid attribute = true.
  • Add the input element's aria-describedby attribute to the validation error message.
  • Added the alt attribute to some Img elements.
  • Removed the placeholder attribute if it is empty.
  • Fixed the tab order of the ImageChoiceElement so the validation works.
  • If the submit action fails, the image is focused as it is at the first invalid element.
Version/s: EPiServer.Forms 4.28.0;
Mar 31, 2020
1 2 3 4 5 6 Next