Episerver - update 355

Release summary

New release of Episerver Campaign (new Marketing Automation start time options). Bug fixes for Episerver CMS Core and Episerver CMS UI.

Released items February 23, 2021

Area ID Type Description Released
CMS-18005
  Should not allow to create "regularExpression" validation if pattern is invalid

Steps to reproduce:
Define a content type via Definitions Api.
Note: A "regularExpression" validation is added to a string property but its pattern is invalid. For example, "pattern": "[0-9]++"

{
	"name": "PageRegExValidationInvalidCase3",
	"baseType": "Page",
	"editSettings": {
		"available": true,
		"order": 0
	},
	"properties": [
        {
			"name": "String1",
			"dataType": "PropertyString",
			"validation": [
				{
					"name": "RegularExpression",
					"severity": "error",
                    "pattern": "[0-9]++",
					"errorMessage": "String 1: pattern is invalid"

				}
			]
		},
        {
			"name": "StringList1",
			"dataType": "PropertyStringList",
			"validation": [
				{
					"name": "itemRegularExpression",
					"severity": "error",
                    "pattern": "[0-9]++",
					"errorMessage": "String List 1: pattern is invalid"

				}
			]
		}
	]
}

Expected result: 
Content management is created with invalid pattern return 400- Bad Request.

Actual result:
Content type is created with invalid pattern. 

Content management is created with invalid pattern return 500.

EPiServer.CMS.Core 11.20.5;
Feb 23, 2021
CMS-17771
  Fallback language is sometimes selected instead of language version when using simple address

Steps to reproduce:

  1. Enable multiple languages like this:
  2. Set root to enable all the languages and set the fallback language to "en" for every language except en.
  3. On page Alloy Plan, set simple address to "alloy".
  4. Create different language versions of Alloy plan and set simple address to "alloy" for all the different language versions.
  5. Go to the different language versions by using their simple address. So for German go to site.com/de/alloy or Swedish site.com/sv/alloy.

Expected result:

The different language versions of the page should be displayed.

Actual result:

Sometimes, the English version is displayed even if there is a language version available.

 

EPiServer.CMS.Core 11.20.5;
Feb 23, 2021
CMS-17919
  Accessibility issues with the login page

There are some accessibility issues with the login page (Util/login.aspx) according to WCAG 2.1.

Bug 1: Missing Language of Page in <html>

For example: an English site should use <html lang="en">.

Reference: https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html

Bug 2: Labels are not connected to form controls

For example: the label for UserName refers to an element ID that does not exist on the page. The input ID is LoginControl_UserName.

<li>
    <label for="UserName">Name</label>
    <input name="LoginControl$UserName" type="text" id="LoginControl_UserName" />
    <span id="LoginControl_RequiredFieldValidator1" style="display:none;">­     </span>
</li>

Reference:  https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html

Bug 3: There is no text in the header <h2 class="text--error">

For example: <h2 class="text--error"></h2>

 

 

EPiServer.CMS.UI 11.33.0;
Feb 23, 2021

Marketing_32.svg Episerver Campaign

Episerver Campaign 8.50

  • Marketing Automation: Advanced node
    In the Advanced node, you can specify which recipients are passing through the Marketing Automation campaign at which time. You can now specify even more precisely when Episerver Campaign should check the criteria.

    Example 1: If you set the interval to Every 1 weeks, on Wednesday from 15:00, the criteria is checked every Wednesday at 15:00.
    Example 2: If you set the interval to Every 2 months, each 1st from 14:00, the criteria is checked on the first day of every second month at 14:00.

    See the Episerver User Guide: Marketing Automation nodes.

More on releases

Related topics

Last updated: Feb 23, 2021