Answers.Body: <p>I had this same issue and resolved by fixing my Redactor configs. If you have a misconfigured file or a formatting error it causes problems related to rendering later in the page, likely related to Redactor throwing a javascript error.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-25T21:28:07.650Z
Answers.Text: My redactor configs are default and unmodified. Also not seeing any javascript or any errors of any kind.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-12T19:51:26.013Z
Answers.LastActivityDate: 2016-01-12T20:01:10.783Z
Answers.LastEditDate: 2016-01-12T20:01:10.783Z
Answers.UserDisplayName: Allan Kukral
Body: <p>Same issue as found here - but no resolution: <a href="https://craftcms.stackexchange.com/questions/12541/missing-buttons-in-settings-after-update-to-2-5-beta">Missing buttons in settings after update to 2.5 beta</a></p>
  
  <p>All of the orange buttons in the CP are missing but the code is there for the css and if I select a checkmark and unselect it then press return the functions still run. </p>
  
  <p>The only thing I can think that may have triggered this is there was a license discrepancy while I ran the upgrade, but I can't recreate it on a new install. </p>
  
  <p>It's missing on every single browser across multiple computers.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-25T21:26:00.930Z
Comments.Text: I'm seeing it on Chrome - latest version, Safari also up to date. I even tested it on Microsoft Edge on my PC, same result.
Comments.UserDisplayName: Chris
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-25T21:33:30.970Z
Comments.Text: Any Craft plugins installed?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-26T20:00:38.780Z
Comments.Text: Yep, even with them disabled same issue.
Comments.UserDisplayName: Chris
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-26T20:01:54.777Z
Comments.Text: Ended up solving it just by setting up a new 2.5 craft environment and putting in my template and database, etc. Strange issue.
Comments.UserDisplayName: Chris
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-12T01:24:37.653Z
Comments.Text: What browser/version are you seeing that on?  Do you have any Craft plugins installed that might be interfering?
Comments.UserDisplayName: Brad Bell
Tags: <admin><updates>
Title: Missing buttons after upgrading site to 2.5
ThreadText: # Missing buttons after upgrading site to 2.5
  
  (Asked by: username_0 on 2016-01-12)
  
  Same issue as found here - but no resolution: [Missing buttons in settings after update to 2.5 beta](https://craftcms.stackexchange.com/questions/12541/missing-buttons-in-settings-after-update-to-2-5-beta)
  
  All of the orange buttons in the CP are missing but the code is there for the css and if I select a checkmark and unselect it then press return the functions still run.
  
  The only thing I can think that may have triggered this is there was a license discrepancy while I ran the upgrade, but I can't recreate it on a new install.
  
  It's missing on every single browser across multiple computers.
  
  **Tags:** admin, updates
  
  > **Comments:**
  > **username_1**: What browser/version are you seeing that on?  Do you have any Craft plugins installed that might be interfering?  
  > **username_0**: I'm seeing it on Chrome - latest version, Safari also up to date. I even tested it on Microsoft Edge on my PC, same result.  
  > **username_1**: Any Craft plugins installed?  
  > **username_0**: Yep, even with them disabled same issue.  
  > **username_0**: Ended up solving it just by setting up a new 2.5 craft environment and putting in my template and database, etc. Strange issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-01-12. Score: 1
  
  I had this same issue and resolved by fixing my Redactor configs. If you have a misconfigured file or a formatting error it causes problems related to rendering later in the page, likely related to Redactor throwing a javascript error.
  
  > **Comments:**
  > **username_0**: My redactor configs are default and unmodified. Also not seeing any javascript or any errors of any kind.  
  
  ---
  
  