Known issues in Content Manager
The following list describes issues known to exist in Content Manager.
- Host name not included in the Content Manager URL used by Experience Space BFF
- When running the Tridion Sites installer, you can specify a host header. The installer correctly sets this host name in binding in IIS but it does not set the host name in the Tridion.ContentManager.Url property used by the Backend for Frontend (BFF). As a result, Experience Space is unable to connect to the Content Manager API and then fails to load.
- If .NET Core Hosting Bundle is installed before Microsoft IIS on a clean system, a reinstall of .NET Core Hosting Bundle may be needed
- When installing on a clean Microsoft Windows Server machine, IIS may not yet be installed. You may initially install .NET Core Hosting Bundle before installing IIS. If you do so, you may end up with an inconsistent system. This issue is also described in the Microsoft article about the .NET Core Hosting Bundle: see the Important note at the top of https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/hosting-bundle?view=aspnetcore-6.0.
- Using both template-based publishing and templateless, data-only publishing with the same content can lead to unwanted side effects
- Tridion Sites offers two methods of publishing: template-based publishing and its replacement, templateless, data-only publishing. While you are migrating from template-based publishing to templateless, data-only publishing, you may find yourself considering using both methods at the same time for the same publication.
- Leaving the Access Management unselected in the Content Manager installer will not uninstall the feature
- By default, the Access Management feature is not selected in the installer. If you are upgrading from SDL Tridion Sites 9.5 and you have the Access Management feature installed, leaving the option unselected will not cause it to be removed.
- Smart Tagging of content in Asian languages does not work
- Inconsistent publishing results related to Region Schemas and templateless, data-only publishing
- The templateless, data-only publishing feature (introduced in SDL Tridion Sites 9.5) adds new options to several Schema types, including Region Schemas. The two general Schema-level options make it possible for you to individually select Schema fields to be publishable and searchable, and the field-level options enable you to select individual fields for publishing and search.
- When using Azure Active Directory for Single Sign-On, a User can have at most 150 groups assigned to them
- The following Microsoft Azure documentation topic describes a limitation in Azure Active Directory: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims#options-for-applications-to-consume-group-information. As the topic states, "Azure Active Directory limits the number of groups it will emit in a token to 150 for SAML assertions, and 200 for JWT to prevent tokens getting too large. If a user is a member of a larger number of groups than the limit, the groups are emitted and a link to the Graph endpoint to obtain group information."
- Publishing is 8% slower using Microsoft Windows Server 2022 or 2019 compared to Microsoft Windows Server 2016 if you use AWS
- Publish performance testing of the Tridion Sites 9.6 release using Windows 2022, Windows 2019 and Windows 2016 revealed an 8% decrease in performance in Windows 2022 or Windows 2019 compared to Windows 2016 if you use AWS. Note that as from Tridion Sites 10, Windows 2016 is no longer as supported operating system version.
ISearchIndexingHandleris not backward compatible-
The Core Service may raise an error like the following one:
Unable to load 'Search Index Handler' for assembly 'SearchIndexerUnifiedExtension.dll' and type 'SearchIndexerUnifiedExtension.SearchIndexerUnifiedExtension' Method 'ExtractIndexFields' in type 'SearchIndexerUnifiedExtension.SearchIndexerUnifiedExtension' from assembly 'SearchIndexerUnifiedExtension, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation. Component: Tridion.AddonService.SDK Errorcode: 865 User: USER StackTrace Information Details: at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type) at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Reflection.Assembly.GetType(String name, Boolean throwOnError) at Tridion.ContentManager.Search.Indexing.SearchIndexingEngine.GetSearchIndexingHandlersFromConfiguration() at Tridion.ContentManager.Search.Indexing.SearchIndexingEngine.GetSearchIndexingHandlersFromConfiguration() - CMSession.CoreServiceClient requires a rebuild of your GUI extensions
- To get the Core Service client instance, your GUI extension can use the public helper property CMSession.CoreServiceClient. Content Manager Explorer, for example, exposes the latest Core Service client endpoint through this property. After an upgrade, this property returns a different version of the CoreService client than before the upgrade.
- .NET method Uri.EscapeDataString(urlString) has changed behavior
-
Version 4.0 or older of the Microsoft .NET Framework is not supported. This may have an effect on how your URLs are parsed if they contain brackets:
- In .NET 4.0 and older, characters that are reserved in RFC 2396 are escaped. RFC 2396 allows brackets.
- In .NET 4.5 and newer, characters that are restricted in RFC 3986 are escaped. RFC 3986 restricts brackets.
-
Use of
RecursiveinOrganizationalItemItemsFiltercauses other filter parameters to be ignored -
An
OrganizationalItemItemsFilterlets you combine multiple filter parameters. One filter parameter isRecursive, which causes the filter to recurse into child organizational items. However, settingRecursivetotruehas the unintended side effect of rendering almost all other filter parameters ineffective, as if they were not set. Specifically, ifRecursiveis set totrue,ItemTypesis the only other filter parameter that gets processed; the filter ignoresBasedOnSchemas,SchemaPurposes,ComponentTypes,TemplateTypeIds,LockFilterandNotBasedOnSchema.