Try our conversational search powered by Generative AI!

AI OnAI Off
Products
Packages [expand] [collapse]
Services
Released in version
All versions
2.4.1
2.4.0
2.4.0-pre
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
2.2.1
2.2.0
2.1.1
2.1.0
2.0.7.9000
2.0.6.9000
2.0.5.9000
2.0.4.9000
2.0.3.9000
1.3.1.8000
1.0.1.7131

Release notes for Optimizely CMS and Customized Commerce updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project.

Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.

  • Bug – Display bug fixes.
  • Critical bug – Display only critical bug fixes.
  • Feature –  Display only new features (all features).
  • UI Feature – Display only end-user (user interface) features.

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

Latest changes

Item type
Filter on date
Items/Page
Clear filters
Area ID Type Description Released
MAI-2058
  SharePoint Connector used incorrect authentication type

SharePoint Connector used an incorrect authentication type. Authentication failed after upgrading to version 2.4.0 of the Connect For SharePoint plugin. 

EPiServer.ConnectForSharepoint 2.4.1; (Or a related package);
Oct 18, 2022
MAI-2009
  Add option to authenticate to SharePoint using auth token

The username and password authentication was changed on the Connect for SharePoint screen with the following information.

  1. Site URL. Specify the URL of the SharePoint repository.
  2. Connection type.
      • On-premises. Select this option if you have a local on-premises SharePoint repository. On-premises has only the Basic authentication type option.
      • Online. Select this option if you have a remote Office 365 SharePoint repository. Select Basic or Modern authentication type option. If you select the Modern option, you must also fill in in the following with your credentials: ClientId, ClientSecret, and Realm. 

You can switch between local on-premises and online cloud repositories and have both repositories copy files to the same media folder or different folders. See SharePoint On-Premises VS. SharePoint Online (2013).

EPiServer.ConnectForSharepoint 2.4.0; (Or a related package);
Apr 05, 2022
MAI-1868
  Sharepoint: Error while downloading or inserting a document can result in excessive CPU usage

If an error occurs more than 3 times while downloading or inserting the same SharePoint document, the processor will orphan the thread and leave it in a state of constantly checking its status.

EPiServer.ConnectForSharepoint 2.3.5; (Or a related package);
Mar 02, 2021
MAI-1864
  Sharepoint: Configurable thread pool

The thread pool for the SharePoint connector is now configurable.

 

AppSettings  = "EPiServer:Sharepoint:MessageThreads" 

Valid properties: 1 through 16

EPiServer.ConnectForSharepoint 2.3.5; (Or a related package);
Mar 02, 2021
MAI-1494
  SharePoint: Cannot load Microsoft.SharePoint.Client.Runtime when installing fresh version of SharePoint.2.3.2
STEPS TO REPRODUCE

1. Install EPiServer.ConnectForSharePoint.2.3.2 to CMS site.
2. In Admin mode, open the SharePoint settings page.
3. Enter credentials.
4. Click the 'Test connection' button.

---> CURRENT: Error when connecting to SharePoint site: Could not load file or assembly 'Microsoft.SharePoint.Client.Runtime, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

TEST CONFIGURATION

EPiServer.CMS.11.10.4
EPiServer.ConnectForSharePoint.2.3.2

The issue only occurs if installing a new, fresh version of EPiServer.ConnectForSharePoint. When upgrading from EPiServer.ConnectForSharePoint.2.3.1, it works well.

EPiServer.ConnectForSharepoint 2.3.3; (Or a related package);
Oct 17, 2018
MAI-1482
  Selected View not set for Sharepoint list item prior to calling processor

An upgrade from Episerver v9.10.1 to Episerver v11.9.0 required updating EPiServer.ConnectForSharePoint from v2.1.1 to v2.3.1. The new version can retrieve Sharepoint items, but they are missing most of their fields.

EPiServer.ConnectForSharepoint 2.3.2; (Or a related package);
Oct 11, 2018
MAI-1144
  ConnectForSharepoint does not update the correct list of files

Steps to reproduce:

1. Create two document Libraries on the SharePoint site, Doc_Store and Vid_Store.
2. Upload documents to Doc_Store folder.
3. Run the SharePoint Update job for the first time.
4. Upload documents to Vid_Store folder.
5. Run the SharePoint Update job for the second time.
==> In EPiServer CMS: Doc_Store folder's documents disappear. Vid_Store folder shows its documents.
6. Run the SharePoint Update job for the third time.
==> In EPiServer CMS: Doc_Store folder shows its documents. Vid_Store folder's documents disappear.

Expected: The add-on shows the list of documents for each selected SharePoint folder.

Actual: The add-on shows and hides a folder's documents each time the SharePoint job is run.

Environment information:

  • EPiServer CMS 10.10.4
  • EPiServer.ConnectForSharePoint 2.2.1
  • SharePoint Enterprise 2013 15.0.4571.1502 on premises
EPiServer.ConnectForSharePoint 2.3.1; (Or a related package);
Mar 25, 2018
MAI-314
  404 on EPiServer.ConnectForSharepoint script

Steps to reproduce

  1. Install a fresh Alloy site
  2. Add EPiServer.ConnectForSharepoint.

Expected: No errors.

Actual: after installing EPiServer.ConnectForSharepoint, 404 and script errors in the console.

Request URL:http://localhost:52953/EPiServer/EPiServer.ConnectForSharePoint/%7BVersionString%7D/ClientResources/Scripts/SharePointModule.js
Request Method:GET
Status Code:404 Not Found

Starting module: EPiServer.ConnectForSharePoint
epi.js:965 EPiServer.ConnectForSharePoint [Object]
dojo.js:1675 GET http://localhost:52953/EPiServer/EPiServer.ConnectForSharePoint/%7BVersionString%7D/ClientResources/Scripts/SharePointModule.js req.injectUrl @ dojo.js:1675injectModule @ dojo.js:1516forEach @ dojo.js:106(anonymous function) @ dojo.js:731guardCheckComplete @ dojo.js:1251injectDependencies @ dojo.js:730contextRequire @ dojo.js:794req @ dojo.js:137_runModuleInitializer @ epi.js:1006(anonymous function) @ epi.js:949signalListener @ dojo.js:8325Deferred.then.promise.then @ dojo.js:8546when @ dojo.js:9065(anonymous function) @ epi.js:948signalListener @ dojo.js:8325Deferred.then.promise.then @ dojo.js:8546when @ dojo.js:9065_startModule @ epi.js:944(anonymous function) @ epi.js:938forEach @ dojo.js:3612(anonymous function) @ epi.js:937signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480(anonymous function) @ epi.js:1014(anonymous function) @ dojo.js:3135signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480(anonymous function) @ XhrWrapper.js:208(anonymous function) @ dojo.js:3135signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480(anonymous function) @ Extender.js:59signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369(anonymous function) @ dojo.js:8358signalListener @ dojo.js:8325Deferred.then.promise.then @ dojo.js:8546signalListener @ dojo.js:8333signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369(anonymous function) @ dojo.js:8358notify @ dojo.js:8123complete @ dojo.js:8104resolve.callback @ dojo.js:8151notify @ dojo.js:8132complete @ dojo.js:8104resolve.callback @ dojo.js:8151notify @ dojo.js:8132complete @ dojo.js:8104resolve.callback @ dojo.js:8151notify @ dojo.js:8140complete @ dojo.js:8104resolve.callback @ dojo.js:8151notify @ dojo.js:8132complete @ dojo.js:8104resolve.callback @ dojo.js:8151(anonymous function) @ dojo.js:14641signalListener @ dojo.js:8325signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8346signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480signalDeferred @ dojo.js:8369signalListener @ dojo.js:8340signalWaiting @ dojo.js:8316Deferred.resolve @ dojo.js:8480handleResponse @ dojo.js:15345onLoad @ dojo.js:15371
dojo.js:1834 Error: scriptError(…)(anonymous function) @ dojo.js:1834(anonymous function) @ dojo.js:345forEach @ dojo.js:106req.signal @ dojo.js:344(anonymous function) @ dojo.js:1669
dojo.js:1837 src: dojoLoader
dojo.js:1837 info: ["/EPiServer/EPiServer.ConnectForSharePoint/

{Version…ring}

/ClientResources/Scripts/SharePointModule.js", Event]

EPiServer.ConnectForSharepoint 2.2.1; (Or a related package);
Sep 24, 2017
MAI-934
  Excessive CMS database queries during synchronization of Sharepoint Data

The FolderMappings store is generating numerous db queries while we attempt to sync the data from Sharepoint to Episerver.

EPiServer.ConnectForSharepoint 2.2.0; (Or a related package);
Jul 09, 2017
MAI-933
  Cannot Re-Sync data after deleting list/view folder manually from CMS

Steps to reproduce

1) Create a new EpiServer site.
2) Install the SharePoint connector and configure it to synchronize to a CMS folder.
3) Verify that data (folders and files) was created in CMS and matches what was in Sharepoint.
4) In CMS, delete the list/view folder.
5) Note the error regarding specific permissions being required. This error also shows up in the log file.
6) Note that the folder is not actually deleted, but all of its sub content is.
7) Attempt to delete the folder again. Note that

  • In some cases, CMS spins wildely and never returns.
  • Clicking refresh causes the view to be refreshed.
  • The folder is not gone.
    8) Run the Sharepoint job that updates the data and note that no data is updated. The view/list folder is not created.
EPiServer.ConnectForSharepoint 2.2.0; (Or a related package);
Jul 09, 2017
1 2 Next