9

No. The change from Classic to Lightning only affects internal users, and not Communities and other external-facing technologies. Visualforce is still a supported technology and will be for the foreseeable future. We will not be forced to switch to Lightning Communities, etc for some time. Removing the Classic interface is a decision to reduce development ...


1

Yep, you should be able to do this. You can't actually swap out a whole theme component out, but you can wrap it in different css - then you can define two different sets of css in the css file. Then, just handle a change theme event to toggle the theme. <aura:attribute name="theme" type="String" default="light"/> <div class="{!v.theme}"> ...


1

Yes, it is possible through forceCommunity:themeLayout interface. Sample component: <aura:component implements="forceCommunity:themeLayout" access="global" description="Sample Custom Theme Layout"> <aura:attribute name="search" type="Aura.Component[]" required="false"/> <aura:attribute name="profileMenu" type="Aura.Component[]" ...


1

Each apex:radioGroup is a unique record group. You can select all of them because they separate radio groups. In other words, you're expecting code like the following: <input type="radio" name="group1" /> <input type="radio" name="group1" /> ... But what you're really getting is: <input type="radio" name="group1" /> <input type="radio"...


1

You should be using Custom Labels for that. After creating custom label, you can use in cmp by using {!$Label.c.labelName} OR you can use $A.get("$Label.namespace.labelName") in Javascript of component. Then you should translate the labels in translation workbench or Directly After these steps you should see the labels in chosen language.


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