Body: <p>We have hit issues after upgrades that require additional "drush cc all" and/or "clear out templates_c" to make me wonder if the upgrade script could be taking care of this better?</p>
  
  <p>Would it be possible to have the script run an extra one of each at the end of the process?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-03T02:58:25.820Z
Comments.Text: Perhaps a permissions issue? I usually run upgrades as the webuser (in our case): sudo -u apache
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-03T08:13:08.670Z
Comments.Text: Agree current behaviour is not always enough - eg https://civicrm.stackexchange.com/questions/25541/why-have-all-my-custom-civi-fields-stopped-showing-up-in-drupal-view   I've had issues with Stripe IPN's after upgrades that are fixed by another cache clear.
Comments.UserDisplayName: Aidan
Tags: <upgrade>
Title: Does the upgrade process perform enough 'clear caches / templates_c' or should it?
ThreadText: # Does the upgrade process perform enough 'clear caches / templates_c' or should it?
  
  (Asked by: username_0 on 2018-07-02)
  
  We have hit issues after upgrades that require additional "drush cc all" and/or "clear out templates\_c" to make me wonder if the upgrade script could be taking care of this better?
  
  Would it be possible to have the script run an extra one of each at the end of the process?
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: Perhaps a permissions issue? I usually run upgrades as the webuser (in our case): sudo -u apache  
  > **username_2**: Agree current behaviour is not always enough - eg https://civicrm.stackexchange.com/questions/25541/why-have-all-my-custom-civi-fields-stopped-showing-up-in-drupal-view   I've had issues with Stripe IPN's after upgrades that are fixed by another cache clear.  
  
  ---
  
  ## 0 answers
  
  