Answers.Body: <p>Long story short, it was a permission issue. A change to groups on my institutions relatively new server left Apache without execute permission on some files and folders in myTheme/civicrm/files. The change was actually a good thing that had been requested some time ago, but I was unaware it was implemented. Reinforcing group read/write/execute on those files solved it. The only remaining mystery is why it was working before the upgrade since the change by our IT person was implemented a few weeks ago.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-07T17:41:01.313Z
Answers.LastActivityDate: 2022-01-07T17:41:01.313Z
Answers.UserDisplayName: Jeff Wood
Body: <p>After an upgrade from 5.38 to 5.44 on a Drupal 8 site the menu and dashboard failed to load. Other page elements, like the footer and header did load. Status page was also inaccessible, but mysite/civicrm/admin and other administrative pages could be accessed. However, edit windows for contacts would just show the spinning throbber and never load, nor would other ajax components work such as help popups, etc.
  Turning on Debugging, without taking any other action solves all the problems, but obviously I don't want to leave debugging on. Does anyone have thoughts on what might be causing the problem?</p>
  <p><strong>UPDATE</strong>
  After checking the console I see that the page is throwing a pile of 403 errors when it attempts to access angular files in /civicrm/persist/contribute/dyn/ BUT ONLY when debugging is disabled. When I turn on debugging the 403 errors disappear.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-01-05T20:16:24.343Z
Comments.Text: Debugging would turn off caching, so that could explain that difference, and then the issue is probably permissions on that `dyn` folder, either filesystem or .htaccess somewhere in that path. Can you check the permissions and owner etc?
Comments.UserDisplayName: Demerit
Tags: <upgrade><menu><ajax><debugging>
Title: After upgrade to 5.44 menu and some elements won't load without debugging enabled
ThreadText: # After upgrade to 5.44 menu and some elements won't load without debugging enabled
  
  (Asked by: username_0 on 2022-01-05)
  
  After an upgrade from 5.38 to 5.44 on a Drupal 8 site the menu and dashboard failed to load. Other page elements, like the footer and header did load. Status page was also inaccessible, but mysite/civicrm/admin and other administrative pages could be accessed. However, edit windows for contacts would just show the spinning throbber and never load, nor would other ajax components work such as help popups, etc.
  Turning on Debugging, without taking any other action solves all the problems, but obviously I don't want to leave debugging on. Does anyone have thoughts on what might be causing the problem?
  
  **UPDATE**
  After checking the console I see that the page is throwing a pile of 403 errors when it attempts to access angular files in /civicrm/persist/contribute/dyn/ BUT ONLY when debugging is disabled. When I turn on debugging the 403 errors disappear.
  
  **Tags:** upgrade, menu, ajax, debugging
  
  > **Comments:**
  > **username_1**: Debugging would turn off caching, so that could explain that difference, and then the issue is probably permissions on that `dyn` folder, either filesystem or .htaccess somewhere in that path. Can you check the permissions and owner etc?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2022-01-07. Score: 2 | Accepted answer
  
  Long story short, it was a permission issue. A change to groups on my institutions relatively new server left Apache without execute permission on some files and folders in myTheme/civicrm/files. The change was actually a good thing that had been requested some time ago, but I was unaware it was implemented. Reinforcing group read/write/execute on those files solved it. The only remaining mystery is why it was working before the upgrade since the change by our IT person was implemented a few weeks ago.
  
  
  ---
  
  