Lightning Experience header no longer appears after adding custom component to page

I've added a custom component to my org, but now the header for standard object pages no longer loads properly. In test this was working fine.


enter image description here

After: enter image description here

Also Activity/Chatter functionality has become broken.

I know this isn't much to go by, but does anyone know what could drive this issue? As I mentioned before, this only happens after moving the change set with these components/classes to the production org.

  • By header do you mean the buttons? or the inforamtion under the button? – Rao Oct 4 '17 at 20:47
  • Yes, the buttons are completely gone. The Chatter/Activity button to Add/Share are also gone. – CCrenshaw Oct 4 '17 at 20:54
  • Did you check if the standard components Chatter and Highlight panels were removed from the page layout by mistake – Rao Oct 4 '17 at 20:56
  • Yes, they were not. If I remove my lightning action from the Account page everything appears again properly. – CCrenshaw Oct 4 '17 at 21:13
  • Did you check the component code to see if there is any kind of navigatetoURL/naviagetocomponent components? I would even check if there are selective filters applied to show / hide components based on the account data if you are on a winter 18 org – Rao Oct 4 '17 at 21:22

Update for others: After a lot of back and forth talk the buttons were getting messed up due to the force:lightningQuickActionWithoutHeader Interface, nothing to do with navigation.

From the behavior you are reporting I am sure the custom component you are embedding inside your account layout has some kind of navigation behavior. If you take a look at the URL it no more says "one/one.app#/sObject/001xxxxxxxxxxxxx/view" it is replaced by /one/one.app#xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In your case I am suspecting the component has a force:editrecord component or lightning:recordViewForm (if you are on winter 18) that only shows the account related information.

eg: My component

<aura:component implements="lightning:actionOverride,force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,force:lightningQuickAction" access="global" >
    <aura:handler name="init" value="{!this}" action="{!c.navigateToMyComponent}"/>


Inside the navigatetochildcomponent I am just showing a datatable. Take a look at the output, all the header and highlight panel info will be cleared on loading the account record.

    navigateToMyComponent : function(component, event, helper) {
        var record_id = component.get("v.recordId");
        var evt = $A.get("e.force:navigateToComponent");
            componentDef : "c:navigatetochildcomponent",
            componentAttributes: {

enter image description here

  • Hmm, this doesn't look to be the case but I think there may be something similar. The URL does not change, it includes /view at the end. I do have an init that clears out some stuff. sObject/0014600000k4fUxAAI/view - before sObject/0014600000k4fUxAAI/view - after – CCrenshaw Oct 5 '17 at 0:42
  • Check if there is a navigation component, that could be tour answer on why the page is not rendering the standard components – Rao Oct 5 '17 at 0:45
  • Can you post the complete component and controller – Rao Oct 5 '17 at 2:01
  • Inspecting the html before/after, I noticed anything in <div>s with forceActions (or actionsContainer) is not appearing normally. I wonder if it has to do with this? For example, <div> with error (completely empty): imgur.com/a/c7sqb No error (everything there!): imgur.com/a/Qn0nZ – CCrenshaw Oct 5 '17 at 4:43
  • Tough to say witjout looking at the component. If you are suspecting your custom component might be messing up standard salesforce components, that is not possible at all if you have activated locker service. Locker makes sure doms cannot mess each other when rendered from different domains – Rao Oct 5 '17 at 5:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.