The "Optimize" feature (tracking and edge personalization) is not included in this release (it's coming shortly in 4.1).
Some Sitecore 9 versions (9.0.0 and 9.0.1 specifically) are not supported in this release due to a breaking change in Sitecore Diagnostics API. 9.0.2 and above are supported. Contact us for the hotfix if you are running these earlier versions.
The value of the
UNIFORM_API_TOKENenvironment variable must be lowercased.
The Nuxt starter kit is not updated to v4.0 yet.
Media items with duplicate names are re-uploaded during every Media Sync operation. Resolving duplicate item names is a pre-requisite for the stable operation of the connector (reference id #925).
- Ensure that the
AllowDuplicateItemNamesOnSameLevelsetting is set to false:
<setting name="AllowDuplicateItemNamesOnSameLevel" value="false" />
- Remove any items with duplicate names at the same level of the content tree using Sitecore Powershell Extensions module or ad-hoc script
- Ensure that the
If Content Sync is enabled, the Map Service API output will be re-synced without the publish handler enabled (reference id #515).
Item changes are not picked up during incremental deployment if the item's
__Standard Valueshave changed (reference id #462).
Since the Incremental Deployment is not enabled by default, any Sitecore publishing operation, in any mode even single item publish, will trigger full site redeployment. This will delay the end of the publish operation. Consider setting up Incremental Deployment as described here to change this default behavior (reference id #265).
Using Sitecore 9.3, you may be affected by a known issue where sometimes the Sitecore links are generated incorrectly. Please request a hotfix from Sitecore Support using id
#393126as a reference, or upgrade to Sitecore 10.
For Sitecore 8.2 installations where the CM and CD instances are split out, some configuration files Uniform ships will need to be adjusted for CM/CD split, as the Role Configuration is not officially supported in those earlier versions of Sitecore.
SXA support limitations:
- Datasource items that have their own layout are not supported yet.
- Page designs are not supported yet.
The Netlify deployment provider does not support incremental HTML generation phase (this is mitigated by an incremental Content Sync).
Deleting an item requires a subsequent republish operation of any other page-level item that is in scope for a given Site Configuration in order for Content Sync and Deployment to handle deletes.
Renaming or moving an item requires republishing operation of the subtree starting with the item that was moved or renamed.