Documentation Center

Known issues

The SDL Digital Experience Accelerator contains some known issues.

DXA web application fails to load
Problem: When trying to access the DXA web application the following error is displayed:
Unauthorized Request -- Please check your configuration settings to 
make sure your authentication details are correct.
Solution: The error is caused by an OAuth enabled on the SDL Web 8 CD side, which is disabled in the DXA web application by default. To enable the OAuth in DXA:
  1. Open %DXA_WEB_APP_HOME%/Web.config.
  2. Set the value to true for the following key/value pair:
    <add key="oauth-enabled" value="true"/>
  3. Make sure that the oauth-client-id and oauth-client-secret values match the ones configured for your SDL Web 8 CD side.
Importing DXA into Content Manager fails under SDL Tridion 2013 SP1

Problem: Import fails with following error when importing on a system with ECL installed: Error: Tridion.ContentManager.FilterException: The Filter condition 'ForRepository' is invalid. The item tcm:0-3-1 does not exist.

Solution: Disable the ECL event handler before the import, and re-enable again after the import:
  1. Open the %TRIDION_HOME%\config\Tridion.ContentManager.config in a text editor.
  2. Locate the <configuration><extensions> node.
  3. Comment out the following line using <!-- and -->:
    <!--
    <add assemblyFileName="C:\Program Files
    (x86)\Tridion\bin\Tridion.ExternalContentLibrary.TcmExtension.dll"
    />
    -->
  4. Save Tridion.ContentManager.config.
  5. Restart all your Tridion Content Manager services.
  6. Retry the import.
  7. After import, re-enable the ECL event handler again by removing the XML comment tags and restart your Tridion Content Manager services again.
Model mappings for embedded fields

Model mappings for embedded fields may only work properly when using default semantics, i.e. the XML names of embedded fields on CM-side correspond to camel-cased property names of the View Models.

Problem: When applying Model mappings to embedded fields, mappings are only guaranteed to work if you use default semantics.

Solution: Ensure that you use default semantics for these mappings, that is, that the XML names of the embedded fields in Content Manager correspond to property names of the View Models (which use "camel case").