Answers.Body: <p>Solved: For reasons that are still a mystery to me, installing the Drupal module civicrm_entity resolved this. The site has been running for years through many CiviCRM updates and this is the first time it's needed this. It seems to be required for any version newer than 5.65.1.</p>
  <p>Hopefully this can save someone else a few hours work if they encounter the same thing!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-20T17:22:27.280Z
Answers.LastActivityDate: 2024-01-20T17:22:27.280Z
Answers.UserDisplayName: AlexT
Body: <p>We have a Drupal 7 site which is days away from being ready to migrate to Drupal 10.<br />
  Mapping the final rollover process in a dev environment, I had planned to upgrade CiviCRM on the D7 site to current, from 5.65.1 to 5.69.2.<br />
  The CiviCRM upgrade reported and appeared to be fine, and I opted to implement the recommended Smarty3.</p>
  <p>Unfortunately all Drupal Views  (eg Custom Formatted lists of events for registration) are now broken.</p>
  <ul>
  <li>When viewed, the Views show no results.</li>
  <li>When edited, all Fields display &quot;Broken/missing handler&quot;.</li>
  <li>When attempting to add a new view, no CiviCRM entities are visible.</li>
  </ul>
  <p><strong>Has anyone else encountered this, and any suggestions?</strong></p>
  <p>I'll be rolling back and investigating whether deferring the CiviCRM upgrade until after Drupal is at v10 works better due to entity handling.</p>
  <hr />
  <p><strong>Solved:</strong>
  For reasons that are still a mystery to me, installing the Drupal module civicrm_entity resolved this.
  The site has been running for years through many CiviCRM updates and this is the first time it's needed this.
  It seems to be required for <em>any</em> version newer than 5.65.1.</p>
  <p>Hopefully this can save someone else a few hours work if they encounter the same thing!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-19T16:17:44.703Z
Comments.Text: Thank you @AlexT!  Please choose "Answer your own question", move your solution into an answer, and mark it as accepted?  This will make it clearer to others that a solution exists.  Also - Drupal 10 does CiviCRM Views fundamentally differently, and civicrm_entity is a requirement (Civi entities are registered as Drupal entities, instead of doing trickery in settings.php).  So this is the better solution for you moving forward regardless.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-20T17:25:32.477Z
Comments.Text: Thanks Jon G.  Yes I was definitely using civicrm_entity already for Drupal 10, and it is way nicer that the old ways!  I just hadn't expected it to become essential in Drupal 7 when upgrading CiviCRM only.   Underway on the D10 upgrade now!
Comments.UserDisplayName: AlexT
Tags: <drupal-views><drupal-7>
Title: Drupal 7 Views broken with upgrade to CiviCRM v5.69.2
ThreadText: # Drupal 7 Views broken with upgrade to CiviCRM v5.69.2
  
  (Asked by: username_0 on 2024-01-18)
  
  We have a Drupal 7 site which is days away from being ready to migrate to Drupal 10.  
  Mapping the final rollover process in a dev environment, I had planned to upgrade CiviCRM on the D7 site to current, from 5.65.1 to 5.69.2.  
  The CiviCRM upgrade reported and appeared to be fine, and I opted to implement the recommended Smarty3.
  
  Unfortunately all Drupal Views (eg Custom Formatted lists of events for registration) are now broken.
  
  * When viewed, the Views show no results.
  * When edited, all Fields display "Broken/missing handler".
  * When attempting to add a new view, no CiviCRM entities are visible.
  
  **Has anyone else encountered this, and any suggestions?**
  
  I'll be rolling back and investigating whether deferring the CiviCRM upgrade until after Drupal is at v10 works better due to entity handling.
  
  ---
  
  **Solved:**
  For reasons that are still a mystery to me, installing the Drupal module civicrm\_entity resolved this.
  The site has been running for years through many CiviCRM updates and this is the first time it's needed this.
  It seems to be required for *any* version newer than 5.65.1.
  
  Hopefully this can save someone else a few hours work if they encounter the same thing!
  
  **Tags:** drupal-views, drupal-7
  
  > **Comments:**
  > **username_1**: Thank you @username_0!  Please choose "Answer your own question", move your solution into an answer, and mark it as accepted?  This will make it clearer to others that a solution exists.  Also - Drupal 10 does CiviCRM Views fundamentally differently, and civicrm_entity is a requirement (Civi entities are registered as Drupal entities, instead of doing trickery in settings.php).  So this is the better solution for you moving forward regardless.  
  > **username_0**: Thanks Jon G.  Yes I was definitely using civicrm_entity already for Drupal 10, and it is way nicer that the old ways!  I just hadn't expected it to become essential in Drupal 7 when upgrading CiviCRM only.   Underway on the D10 upgrade now!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2024-01-20. Score: 2 | Accepted answer
  
  Solved: For reasons that are still a mystery to me, installing the Drupal module civicrm\_entity resolved this. The site has been running for years through many CiviCRM updates and this is the first time it's needed this. It seems to be required for any version newer than 5.65.1.
  
  Hopefully this can save someone else a few hours work if they encounter the same thing!
  
  
  ---
  
  