Answers.Body: <p>We also needed to disable some billing fields, including the state/province, so we wrote an extension for it: <a href="https://github.com/WeMoveEU/nobillingfields" rel="nofollow noreferrer">https://github.com/WeMoveEU/nobillingfields</a></p>
  
  <p>It keeps only first name, last name and zip code, and this is a hardcoded thing, but you should be able to easily adapt to your needs if you have a developer. 
  Note however that when we migrated to 4.7, the extension stopped working, and I patched civi core to make it work again. <a href="https://issues.civicrm.org/jira/browse/CRM-19965" rel="nofollow noreferrer">I reported the problem</a>, and the suggested fix was to unset validation errors with a hook, but I have yet to try it.</p>
  
  <p>I'm afraid there is no easier solution...</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-31T07:00:04.167Z
Answers.LastActivityDate: 2017-08-31T07:00:04.167Z
Answers.UserDisplayName: Djizeus
Answers.Body: <p>The address fields are defined in a file call CRM/Core/Payment.php.
  I approached this by overridding the file in a Custom PHP directory and commenting out the State/province field. Not ideal I realise, but fast.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-05T10:19:06.260Z
Answers.LastActivityDate: 2017-10-05T10:19:06.260Z
Answers.UserDisplayName: Rob Squires
Body: <p>In the UK, the list of counties provided by Civicrm (and by the ISO) is mysterious to say the least to most UK dwellers. Many people think they live in a county which changed to something else years ago!</p>
  
  <p>So, afaik it's best not to use counties in addresses with drop-down options - such as billing fields.</p>
  
  <p>Therefore, how can one disable state/county in a billing address block? Or at least make it not required?</p>
  
  <p>We use Authorize.net for most UK transactions.</p>
  
  <p>Thanks for your help!</p>
  
  <p>Drupal 7.56, Civi 4.7.22</p>
  
  <p>PS - I see this: <a href="https://issues.civicrm.org/jira/browse/CRM-19688" rel="noreferrer">https://issues.civicrm.org/jira/browse/CRM-19688</a>
  But I don't think it helps in this situation?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-29T21:40:01.803Z
Comments.Text: A similar issue was raised at [this reference](https://civicrm.stackexchange.com/questions/15793/billing-name-and-address) that might help in your situation.
Comments.UserDisplayName: peterb
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-01T16:28:21.380Z
Comments.Text: Agreed that CRM-19688 isn't relevant to your situation, but I think the link that peterb raises is.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-02T21:26:36.170Z
Comments.Text: I've asked a question in the comments of peterb's link. I'm not sure it still applies to 4.7.22? I think I read it that all fields are set to be required in one sweep.
Comments.UserDisplayName: Andyg8
Tags: <billingblock>
Title: How to disable State/Province in billing address blocks
ThreadText: # How to disable State/Province in billing address blocks
  
  (Asked by: username_0 on 2017-07-29)
  
  In the UK, the list of counties provided by Civicrm (and by the ISO) is mysterious to say the least to most UK dwellers. Many people think they live in a county which changed to something else years ago!
  
  So, afaik it's best not to use counties in addresses with drop-down options - such as billing fields.
  
  Therefore, how can one disable state/county in a billing address block? Or at least make it not required?
  
  We use Authorize.net for most UK transactions.
  
  Thanks for your help!
  
  Drupal 7.56, Civi 4.7.22
  
  PS - I see this: <https://issues.civicrm.org/jira/browse/CRM-19688>
  But I don't think it helps in this situation?
  
  **Tags:** billingblock
  
  > **Comments:**
  > **username_1**: A similar issue was raised at [this reference](https://civicrm.stackexchange.com/questions/15793/billing-name-and-address) that might help in your situation.  
  > **username_2**: Agreed that CRM-19688 isn't relevant to your situation, but I think the link that username_1 raises is.  
  > **username_0**: I've asked a question in the comments of username_1's link. I'm not sure it still applies to 4.7.22? I think I read it that all fields are set to be required in one sweep.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2017-08-31. Score: 3
  
  We also needed to disable some billing fields, including the state/province, so we wrote an extension for it: <https://github.com/WeMoveEU/nobillingfields>
  
  It keeps only first name, last name and zip code, and this is a hardcoded thing, but you should be able to easily adapt to your needs if you have a developer.
  Note however that when we migrated to 4.7, the extension stopped working, and I patched civi core to make it work again. [I reported the problem](https://issues.civicrm.org/jira/browse/CRM-19965), and the suggested fix was to unset validation errors with a hook, but I have yet to try it.
  
  I'm afraid there is no easier solution...
  
  
  ---
  
  ### Answer by username_4 on 2017-10-05. Score: 2
  
  The address fields are defined in a file call CRM/Core/Payment.php.
  I approached this by overridding the file in a Custom PHP directory and commenting out the State/province field. Not ideal I realise, but fast.
  
  
  ---
  
  