Experience Cloud Developer Guide

Get Up to Speed with Experience Builder Sites
Develop Experience Builder Sites: The Basics
Brand Your Aura Site
Develop Secure Sites: Authenticated and Guest Users
Develop Secure Sites: CSP, LWS, and Lightning Locker
Analyze and Improve Experience Builder Site Performance
Add Pardot Tracking to Your Experience Builder Site
Use a CMS with Your Experience Builder Site
Report on Deflections: The Deflection Signals Framework
Deploy an Experience Cloud Site from Sandbox to Production
Deploy Your Experience Cloud Site with Change Sets
Deploy Your Experience Cloud Site with the Metadata API
ExperienceBundle for Experience Builder Sites
Avoid Deployment Issues When Moving to Enhanced LWR Sites
Considerations for Deploying Authenticated LWR Sites
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Considerations for Deploying Authenticated LWR Sites

Beginning in Winter ’23, new LWR sites created through Experience Builder or Connect API don’t include /s at the end of their URLs. URLs for authenticated LWR sites created before Winter ’23 still include /s, and this URL structure update impacts deployment if sandbox and production URLs don’t match. Learn which deployment scenarios are supported and how to resolve unsupported deployment errors related to /s.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Developer, Performance, and Unlimited Editions

The described scenarios assume that sandbox and production are on the same version of Salesforce. Deploying a site from a newer version to an older version isn’t supported.

Note

Metadata API Deployments

  • Creating a site through Metadata API deployment is supported, whether the source site’s URL includes /s. If the source site’s URL includes /s, the new target site’s URL includes /s. If the source site’s URL doesn’t include /s, the new target site’s URL doesn’t include /s.
  • To update a site with Metadata API deployment, the source site’s URL and the target site’s URL must match. Both URLs must include /s, or neither URL can include /s.
  • To resolve a Metadata API deployment error related to /s, update your metadata bundle to add or remove /s from the source site’s URL. Ensure that the source site’s URL matches the target site’s URL. You can’t add /s to or remove /s from the target site’s URL.

Change Set Deployments

  • Creating a site through change set deployment is supported, whether the source site’s URL includes /s. If the source site’s URL includes /s, the new target site’s URL includes /s. If the source site’s URL doesn’t include /s, the new target site’s URL doesn’t include /s.
  • To update a site with change set deployment, the source site’s URL and the target site’s URL must match. Both URLs must include /s, or neither URL can include /s.
  • To resolve a change set deployment error related to /s, rename either the source site or the target site through the API or Experience Builder. Renaming one of the sites creates a site instead of updating the target site. You can’t add /s to or remove /s from either the source site’s URL or the target site’s URL.