Answers.Body: <p>SOLVED: For good measure here is a repeat of the above comment. </p>
  
  <p>I was able to successfully install the upgrade to 4.7.21 on Drupal 6 after applying the patch mentioned above, and after disabling Views, CTools and Webform (and all related/dependant modules).</p>
  
  <p>The upgrade then ran smoothly without any problems.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-11T21:36:51.850Z
Answers.LastActivityDate: 2017-07-11T21:36:51.850Z
Answers.UserDisplayName: Davy Ivins
Answers.Body: <p>We have had to create this field in the db in several sites we have upgraded. Not sure why the upgrade script is failing to do this correctly</p>
  
  <p>Fuzion have provided a <a href="https://issues.civicrm.org/jira/browse/CRM-20318" rel="nofollow noreferrer">patch</a> for this to avoid the problem for future folks doing upgrades</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-11T21:04:43.050Z
Answers.Text: Thanks Pete. I tried the patch but still wasn't successful. But fortunately I saw in the related comments stream a suggestion that the problem was related to Civi/Webform/Views/CTools so I disabled those and re-ran the upgrade. It ran perfectly.
Answers.UserDisplayName: Davy Ivins
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-11T21:44:15.820Z
Answers.Text: Davy - thanks for the input on this. Not finding the discuss re CTools etc. Canyou pls point to it? I looked at https://issues.civicrm.org/jira/browse/CRM-20623 and https://issues.civicrm.org/jira/browse/CRM-20507 and https://github.com/civicrm/civicrm-core/pull/10028
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-11T21:53:31.267Z
Answers.Text: Pete: Via https://issues.civicrm.org/jira/browse/CRM-20318 then Subtasks to https://issues.civicrm.org/jira/browse/CRM-20502.
Answers.UserDisplayName: Davy Ivins
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-10T23:43:26.937Z
Answers.LastActivityDate: 2017-07-11T07:32:16.907Z
Answers.LastEditDate: 2017-07-11T07:32:16.907Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>After installing the 4.7.21 upgrade my D6 site shows as upgraded and Civi appears to run correctly. However when I run the upgrade script I get error: <code>Sorry but we are not able to provide this at the moment. DB Error: no such field</code>""</p>
  
  <p>If I delve into the error I find:
  <code>[nativecode=1054 ** Unknown column 'civicrm_custom_group.is_public' in 'field list']&amp;quot;]</code></p>
  
  <p>Can anyone guide me how to fix this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-10T22:33:31.140Z
Comments.Text: That sounds familiar - do you have views enabled? Are you using drush?
Comments.UserDisplayName: user4278
Tags: <upgrade><drupal-6><4.7.21>
Title: SOLVED: Can't run Upgrade script 4.7.21 (Drupal6) due to unknown column = civicrm_custom_group.is_public
ThreadText: # SOLVED: Can't run Upgrade script 4.7.21 (Drupal6) due to unknown column = civicrm_custom_group.is_public
  
  (Asked by: username_0 on 2017-07-10)
  
  After installing the 4.7.21 upgrade my D6 site shows as upgraded and Civi appears to run correctly. However when I run the upgrade script I get error: `Sorry but we are not able to provide this at the moment. DB Error: no such field`""
  
  If I delve into the error I find:
  `[nativecode=1054 ** Unknown column 'civicrm_custom_group.is_public' in 'field list']"]`
  
  Can anyone guide me how to fix this?
  
  **Tags:** upgrade, drupal-6, 4.7.21
  
  > **Comments:**
  > **username_1**: That sounds familiar - do you have views enabled? Are you using drush?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-07-10. Score: 3 | Accepted answer
  
  We have had to create this field in the db in several sites we have upgraded. Not sure why the upgrade script is failing to do this correctly
  
  Fuzion have provided a [patch](https://issues.civicrm.org/jira/browse/CRM-20318) for this to avoid the problem for future folks doing upgrades
  
  > **Comments:**
  > **username_0**: Thanks Pete. I tried the patch but still wasn't successful. But fortunately I saw in the related comments stream a suggestion that the problem was related to Civi/Webform/Views/CTools so I disabled those and re-ran the upgrade. It ran perfectly.  
  > **username_2**: Davy - thanks for the input on this. Not finding the discuss re CTools etc. Canyou pls point to it? I looked at https://issues.civicrm.org/jira/browse/CRM-20623 and https://issues.civicrm.org/jira/browse/CRM-20507 and https://github.com/civicrm/civicrm-core/pull/10028  
  > **username_0**: Pete: Via https://issues.civicrm.org/jira/browse/CRM-20318 then Subtasks to https://issues.civicrm.org/jira/browse/CRM-20502.  
  
  ---
  
  ### Answer by username_0 on 2017-07-11. Score: 3
  
  SOLVED: For good measure here is a repeat of the above comment.
  
  I was able to successfully install the upgrade to 4.7.21 on Drupal 6 after applying the patch mentioned above, and after disabling Views, CTools and Webform (and all related/dependant modules).
  
  The upgrade then ran smoothly without any problems.
  
  
  ---
  
  