Skip to main content
Featured group

Lightning Web Runtime Experiences

Our central hub of collaboration for participating in Lightning Web Runtime Experiences (prev. Communities). You'll find access to key online resources and direct assistance from the Product and Engineering teams.

LWR Quick Tip: Full Width Section layout

 

Hi folks - welcome to a new series of short posts introducing tips & tricks, and new features in Experience Cloud LWR 🚀. 

 

Want to have a full width hero-banner section whilst the rest of the site content is constrained? That's now easily achievable with the Spring '24 release!

 

Here's how you do it: 

In your hero-banner Section, configure the Section Max Content Width field to be 'Full Width'. Then, in the Section > Style tab, set Padding to be 0. 

 

Check out the video demo hereLWR Quick Tip: Full Width Section layout Hi folks - welcome to a new series of short posts introducing tips & tricks, and new features in Experience Cloud LWR 🚀.

 

@* Experience Cloud *@Lightning Web Runtime Experiences #Experience Cloud @* Salesforce Commerce for B2B & D2C *

4 comments
0/9000

This one is directed to the product team primarily. Is there anything on the roadmap to add the Case Deflection Component to LWR sites now that the Contact Support Form Component is there? We are looking at case deflections and would need to build this all in LWC without the latter component? Thank you!

5 answers
0/9000

I have an LWR Digital Experience and have given the Guest User access to a Visualforce Page. In the Visualforce Page, I'm trying to display a Lightning Web Component. I have followed this documentation but it's not working - https://developer.salesforce.com/docs/platform/lwc/guide/lightning-out-public-apps.html.

 

In my Chrome console I get this error:

c/lightningOutApp.app?aura.format=JSON&aura.formatAdapter=LIGHTNING_OUT 404 (Not Found)

 

I have a case open with Salesforce Support but they can't figure out why it's not working, even though I followed the documentation.

 

Has anyone else come across this issue and know how to fix it?

 

@* Experience Cloud *

@*Experience Cloud Developers*

 

Jeff

3 answers
0/9000

We get 501 - Not Implemented for when posting SAML request for LWR site. It really prevent us to offer LWR when external identity provider is needed. @George Abboud are there any plans to prio this in the near future? We confirmed with SF Support(Case #469243770) that redirections are currently unavailable 

11 answers
  1. Mar 26, 2025, 12:41 PM

    Thanks for the clarification, that makes sense. It's true that website frameworks aren't typically expected to handle POST requests during standard browsing. Our use case appears to be an exception. 

    I appreciate the suggestion regarding Visualforce. We'll definitely consider leveraging the VF site path for scenarios that require POST request processing.

0/9000

Hello Everyone,

 

I am facing the below error when I am trying to deploy my LWR Site to QA Sandbox.

 

Error Message : Error: You can only select profiles that are associated with the experience.

 

I retrieved the components related to Network using Change Set and retrieved the same in VS code using sfdx force:source:retrieve command. Only one Profile is being used in community which is included.

 

Please help in case you have any leads on this issue.

2 answers
  1. Mar 15, 2025, 12:15 PM

    Hey you may try to remove all other profile except System admin one. In my case did same and re-upload the change set by cloning and it's got resolved.  

     

    Hope this will help you.

     

    Thanks & regards 

    Rahul Kumar 

    Sr. Salesforce Developer

0/9000

Enhanced CMS has the ability to preview content. However, most of us build custom LWCs using the experience/cmsDeliveryApi getContent module and that only retrieves published content. The LWC I have uses a string property that has the contentKey passed in using a data binding expression {!Item.contentKey}. How should a LWC be built to support content authors to preview content from a CMS workspace while also supporting efficient LWC development? Is there a REST API method that would allow this? 

cc: @David Green @George Abboud @Geno Mathew @* Experience Cloud *

4 answers
  1. Feb 14, 2025, 7:02 PM

    Hi @Neil Hayek

     

    Thanks for checking with the team. 

     

    The standard components can't achieve the exact branding a customer requires. We also might have more advanced content modeling than what out-of-the-box CMS provides by using workarounds with contentKey references using Text nodes that enable us to create structured content for an entire page's content, which the CMS components cannot do.

0/9000

Unlike Aura sites, LWR sites don't support the lightning-file-upload base component. While I don't mind rolling my own file upload component, with Apex you're limited to files around ~4.5 MB, otherwise you hit heap size errors. That's too low a limit if you have to accept (for example) scanned documents in a PDF format, which can get up to 15-20 MB.

 

There is a workaround involving the Ajax Toolkit in a Visualforce iframe if the user is authenticated, but it doesn't work in a Guest User context. 

 

I raised this same issue on StackExchange and got an interesting (if not very secure) solution from sfdcfox. Now I'm posting to the Trailhead Group to improve the odds that the product team will recommend a path forward.

 

Will lightning-file-upload be supported in LWR sites in the future, as it is today in Aura sites? Is there some undocumented way to create a new ContentVersion record with lightning/uiRecordApi in an LWC? Anything else I should know to help guide decision-making?

47 answers
  1. Dec 10, 2024, 6:21 PM

    Hi @Hares Saade, you can work around this error by enabling the setting mentioned by @Fabien Taillon from inside General Settings under Salesforce Files. Additionally, starting Spring '25, this feature will be Generally Available, with this setting enabled by default. Hope this helps! 

0/9000

I'm trying to create an object page for a custom object in an enhanced LWR Site. In the "old" LWR metadata structure (route), this is specified both by the routeType and the objectApiName attributes:

How to correctly specify object pages in enhanced LWR Sites?

However, in the enhanced LWR metadata structure (route), I can only use the routeType attribute. objectApiName is not defined in the schema: Enhanced LWR route.pngobjectApiName error.png

 

The problem is that the object prefix (detail-a1o) of our custom object is different in our scratch orgs and our sandboxes. This means that the object subpages are listed under the wrong object as shown below!

 

Scratch orgs:Wrong object.png

 

Sandboxes:Correct object.png

Is there another way of setting the correct object reference in Enhanced LWR routes or is this a bug?

20 answers
  1. Jan 24, 2025, 12:01 AM

    For enhanced LWR sites, instead of having a separate objectApiName, we embed this information in routeType itself. 

    The following format change has been made last year and should hopefully address the challenge described above. 

     

    Example: For a custom object with objectApiName: helperEntity, the routeType of the detail would be detail-helperEntity__c. 

     

    Please note a fresh retrieve is required to retrieve the new format. 

     

    Please let us know if you are still running into a problem 

    @Kai Amundsen. cc @George Abboud @David Green @Geno Mathew

0/9000

LWR looks great and the future, however, as of now, there is basically no way to package and distribute them. As and ISV, Lightning Bolt solutions are great and distribute nicely. When can we include LWR solutions via Lightning Bolt as well?

3 answers
  1. Jan 29, 2025, 9:43 AM

    Thank you, @David Green

    for adding me.  

     

    Hello

    @Kai Amundsen

    , Thanks for your feedback! We’re glad you’re excited about LWR. Currently, we don't have a release date for supporting packaging and distributing LWR solutions via Lightning Bolt, but we appreciate the suggestion. We’re always looking to improve and evolve based on feedback from our community 

     

    Thanks again for your support and for being part of the conversation.

0/9000

We have an Experience Cloud site being display in an App via a WebView.  When the user clicks on the Web View tab it is supposed to login to Exp Cloud LWR enhanced site.  This uses Gigya SAP OIDC login.  All of this is working fine.  The issue is that Community Users have a 24 time out.  The app has no such time out.  The app has the Gigya token and has passed it over but it isn't refreshing.

0/9000