12

lightning:navigation is not supported in communities .Take a look at Summer18 release notes here that clearly mentions below These resources aren’t supported in other containers, such as Lightning Components for Visualforce, Lightning Out, or Communities. This is true even if you access these containers inside Lightning Experience or the Salesforce mobile ...


8

The pub-sub module checks for page references when firing events, so that the event is scoped and only in the current page. In Communities, we actually now support lightning-navigation as of Spring '19: http://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_networks_navigationchanges.htm However, there are some limitations, currently ...


7

Its definitely possible to use an iframe inside the lightning component .The out of box Visualforce component also internally just iframes the Visualforce inside the lightning component .Even the new lightning:container does an iframe of the third party application inside the lightning component . As the comment said if there are http and https urls are ...


7

Make sure the component is available for communities by adding implements="forceCommunity:availableForAllPageTypes" to https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_config_for_builder.htm


7

The pub-sub module checks for page references when firing events, so that the event is scoped and only in the current page. In Communities, we do support lightning-navigation as of Spring '19: http://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_networks_navigationchanges.htm However, there are some limitations, currently ...


7

From docs, you have to add <target>lightning__RecordPage</target> in the lwc component meta, for it to accept recordId from the detail page. <targets> <target>lightning__RecordPage</target> </targets> Indicates that the component takes a record Id as an attribute. EDIT: Apparently this works in App builder, but in ...


6

If you select the appropriate scope in your CSS, you can hide options in the Profile Header component: For the profile menu option: .profile.uiMenuItem{ display: none; } You can modify the CSS under the branding options However, this will affect all your users. If you would prefer this to change based on profile (your admins might want to be able to ...


6

try to add oncancel event in your component. <lightning:recordForm objectApiName="Custom_Object__c" recordTypeId="{!v.Applicant.recordTypeId}" layoutType="Compact" columns="2" mode = "edit" onload="{!c.handleLoad}" ...


6

The cards should be in their own layout boxes (instead of being the layout boxes), and should not be floating. Elements that restrict size changes (e.g. slds-size_1-of-3) should be wrapped around whatever it is you're trying to size. Most of the time it doesn't matter, but it helps to get in the habit of doing so, and doing so means using lightning:...


6

Apparently Salesforce is not clever enough to understand when you put in {!recordId} as a default value. Removing the default value and setting the property in the community fixed the issue. <property name="recordId" type="String" label="Record ID" description="The value should be {!recordId}."/> Update: For people stumbling across this answer ...


5

if PickupLocationtooltip is a separate component, then you won't be able to access it's internals with Locker Service enabled. What you will need to do to perform actions on this component is to either use events to communicate or define a public interface on the PickupLocationtooltip component via an aura:method If you expose a method, you can call this ...


5

Here is an example of embedding an iframe in a Lightning Component: https://github.com/nikitakarpenkov/iframe-lightning-component The component itself is in the IframeComponent.cmp file: https://github.com/nikitakarpenkov/iframe-lightning-component/blob/master/aura/IframeComponent/IframeComponent.cmp <aura:component implements="forceCommunity:...


5

It turned out, that waiting has helped. I've tried it the first time after about 12 hours after the Sandbox has become available. Then I got the error. Then I republished. Still got the error. 3 more hours passed. Now the error is gone - without having done anything else... Very strange behavior...


5

For my usecase, I was able to find a workaround by doing a regex from a string instead of raw like so : var myWorkingRegex = new RegExp('/'); since you do not need to bound your regexes in a string with a / at the end. It looks pretty straight-forward, just do not have two consecutive // in a raw regex. Two // in a string looks like it is parsed correctly ...


5

Answering my own question, in case it's useful to someone in the future. It turns out that the iframe issue was a red herring: the key point was the code 302 in the URL, which indicated a redirect because of likely invalid access. So the solution was to (a) ensure that the VF page was accessible to the user's profile (which it was already), (b) add the VF ...


4

You can de-scope the bootstrap from entire Napili Template. Instead apply for specific sections. This can be done using Less.js .bootstrap-div { //put the bootstrap @includes here } so <div class="bootstrap-div"> Bootstrap works here </div> <div> No bootstrap </div>


4

According to Salesforce Support this functionality is by design and there is no known workaround. I recommend voting for the following Idea and hope that Salesforce takes action: https://success.salesforce.com/ideaView?id=08730000000DvgQAAS


4

Additional clarification for "visible in community sites". The iframe src needs to be dynamic if the page will be visible in both standard Salesforce as well as a Lightning Community. This is because the relative URL for standard Salesforce access to your Visualforce page is /apex/YourPageName. However, if you have a community with the URL name "...


4

LightningStylesheets=true has limitations and will try to style your page as close as it can to SLDS, however, it does not support all apex:tags, I would suggest you read apex:slds vs lightningstylesheet option which explains in more detail the difference. Without your VF page code, we cant really suggest the best approach either.


4

What you need here is an application event. Application events by definition states: Application events follow a traditional publish-subscribe model. An application event is fired from an instance of a component. All components that provide a handler for the event are notified. In your scenario, you will need to register an application event and fire it ...


4

Lightning is salesforce.com's future. They've invested heavily in it, and I don't think Visualforce has even had more than 5-10 features released for it in a number of years now, and those were mostly security- and Lightning-related. You may as well starting rewriting your UI in Lightning Components now, completely as possible, because if history is any ...


4

So, the specifications for aura:if explicitly state it needs an expression, however the attribute isTrue itself does say its a boolean. Given that, I would expect your syntax to work however it looks like it may be treating it is a truthy String. The easiest fix is to pass in an attribute like this: <aura:attribute name="myBool" type="Boolean" default="...


4

The only real option is to create a page and embed the Visualforce page within it. That will allow it to be added to the navigation menu as a community page. The page would be a Standard page with 1 full width column. Then it can be set to have a Visualforce page in the content area. There will be a drop down of all the available VF pages After ...


4

You didn't actually read the file. You need to call one of readAsArrayBuffer, readAsBinaryString, readAsDataURL, or readAsText. You should call one of those methods after setting your onload handler. You can read more about the FileReader on MDN.


4

By design, components are not allowed to access "the Window". For that reason, you'll not be able to get one to open in a new Window. What you will be able to do though is allow the user to press a pop-out button on the component so it pops-out into it's own Window. By design, you won't be able to cause that functionality to occur automatically. It will ...


3

No, additionally, this is mentioned in step 3 of the documentation/blog post you linked: Step 3: Go to the Community Management console and update your administrative settings, topics, moderation criteria, etc. as these do not carry over automatically. Unfortunately, the change set does not cover everything, you will still have to modify some things ...


3

Right, looks like you're right about the menuItem var not being available until some magic happens. A consistent way around this would be to check that v.menuItems is a length greater than 0 in the rerender method, so something like rerender: function(component, helper) { var menuItems = component.get('v.menuItems'); if (menuItems.length > 0) { ...


3

Looks similar to this Known issue. Below workaround might help. Add below CSS to Community branding custom CSS. .oneAlohaPage .mask { display: none; }


3

Whenever you create a Community(Napili) on the Salesforce for the first time, some custom sample lightning components(with standard functionality) will be added/installed. We just need to make simple changes and make use of them on the right community pages to make them work. Those components include: Login Form, Self-Registeration, Forgot Password and ...


3

Please use below code to redirect to community login page : window.location.replace("<community-domain>/secur/logout.jsp?retUrl=<redirect-URL>"); Eg: window.location.replace("/testPortal/secur/logout.jsp?retUrl=%2Flogin"); window.location.replace("https://mycommunity-domain.com/secur/logout.jsp?retUrl=https%3A%2F%2Fmycommunity-domain.com%...


Only top voted, non community-wiki answers of a minimum length are eligible