Answers.Body: <p>I feel this issue is documented  and fixed at <a href="https://issues.civicrm.org/jira/browse/CRM-21180" rel="nofollow noreferrer">CRM-21180</a>. You can try by applying <a href="https://github.com/civicrm/civicrm-core/pull/11364" rel="nofollow noreferrer">patch</a> or wait for 4.7.30 release.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-25T13:27:11.457Z
Answers.Text: Thanks for the answer, Pradeep. Yes that seems to address issue #2, but not issue #1?
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-25T13:28:15.503Z
Answers.Text: I feel it does please try
Answers.UserDisplayName: Pradeep Nayak
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-25T13:31:57.430Z
Answers.Text: Oh ok, will do so.
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-26T11:53:06.240Z
Answers.Text: I'm not having much success. I'll admit I'm not sure exactly what procedure I need to follow to apply the patch :-/  I've tried updating just the 11 files in the patch, and I've tried updating the whole codebase.  Both break my 4.7.29 installation. Are there any guides you could point me to?
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-26T12:09:25.780Z
Answers.Text: Ooops, I should have searched first, then posted after :-) https://civicrm.stackexchange.com/questions/4622/how-do-i-apply-a-patch-supplied-in-the-issue-queue-via-git
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-27T19:50:11.150Z
Answers.Text: OK, so I've applied the patch.  It seems to have fixed problem 2, but NOT problem 1.
  
  I can make and save changes to records with Contact Subtypes, but first I see the "Contact Subtype" error as described above. If I click "OK" to ignore the warning, the record saves without complaining about custom addressees -- but all the custom subtype data is lost. 
  
  So as I feared, the patch does address the custom addressee issue, but not this contact subtype problem.
  
  Other ideas?
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-28T12:11:24.040Z
Answers.Text: I'm going to go ahead and accept this answer, because it did solve my question about the Custom Addressee issue. But since it seems these two issues aren't in fact related, I'm going to open a new question with just the Contact Subtype error. thanks again for your help here!
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-24T15:30:57.293Z
Answers.LastActivityDate: 2018-01-24T15:30:57.293Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>I've just updated a Joomla 2.5.28 site from an older version of CiviCRM (4.4) to the latest 4.7.29.  Now I can't edit any of the fields under the "Contact Details" pane for existing records.</p>
  
  <p>There are two errors:</p>
  
  <ol>
  <li><p>When editing these fields for contacts that have custom subtypes, a popup appears saying "One or more contact subtypes have been de-selected from the list for this contact. Any custom data associated with de-selected subtype will be removed as long as the contact does not have a contact subtype still selected. Click OK to proceed, or Cancel to review your changes before saving." </p></li>
  <li><p>For all contacts (including custom subtypes from item 1 above), saving doesn't work and throws this error:  "Custom Addressee is a required field if Addressee is of type Customized."</p></li>
  </ol>
  
  <p>It's also interesting that I can create NEW records of contact subtypes, but get the errors again if I try to update the Contact Details of the new record.</p>
  
  <p>I found this post (<a href="https://civicrm.stackexchange.com/questions/4277/why-after-importing-contact-records-were-addressee-field-values-set-to-customize">Why after importing contact records were Addressee field values set to &quot;Customized&quot; for records where Custom Addressee had a null value?</a>) which seems to address issue #1, but I'm a bit stumped as to issue #2.  And I didn't want to try the correction suggested in this post until I knew if the two issues could be related.</p>
  
  <p>Site details:
  Joomla 2.5.28
  CiviCRM 4.7.29</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-24T14:14:31.807Z
Comments.Text: Crap. Just noticed I made a mistake in my first post -- the last paragraph should say that the post addresses item #2, and #1 has me stumped :-)
Comments.UserDisplayName: minbori
Tags: <contacts><error><contact-types>
Title: after upgrade, can't edit Contact Details fields (Custom Addressee and de-selected subtypes errors)
ThreadText: # after upgrade, can't edit Contact Details fields (Custom Addressee and de-selected subtypes errors)
  
  (Asked by: username_0 on 2018-01-24)
  
  I've just updated a Joomla 2.5.28 site from an older version of CiviCRM (4.4) to the latest 4.7.29. Now I can't edit any of the fields under the "Contact Details" pane for existing records.
  
  There are two errors:
  
  1. When editing these fields for contacts that have custom subtypes, a popup appears saying "One or more contact subtypes have been de-selected from the list for this contact. Any custom data associated with de-selected subtype will be removed as long as the contact does not have a contact subtype still selected. Click OK to proceed, or Cancel to review your changes before saving."
  2. For all contacts (including custom subtypes from item 1 above), saving doesn't work and throws this error: "Custom Addressee is a required field if Addressee is of type Customized."
  
  It's also interesting that I can create NEW records of contact subtypes, but get the errors again if I try to update the Contact Details of the new record.
  
  I found this post ([Why after importing contact records were Addressee field values set to "Customized" for records where Custom Addressee had a null value?](https://civicrm.stackexchange.com/questions/4277/why-after-importing-contact-records-were-addressee-field-values-set-to-customize)) which seems to address issue #1, but I'm a bit stumped as to issue #2. And I didn't want to try the correction suggested in this post until I knew if the two issues could be related.
  
  Site details:
  Joomla 2.5.28
  CiviCRM 4.7.29
  
  **Tags:** contacts, error, contact-types
  
  > **Comments:**
  > **username_0**: Crap. Just noticed I made a mistake in my first post -- the last paragraph should say that the post addresses item #2, and #1 has me stumped :-)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-01-24. Score: 1 | Accepted answer
  
  I feel this issue is documented and fixed at [CRM-21180](https://issues.civicrm.org/jira/browse/CRM-21180). You can try by applying [patch](https://github.com/civicrm/civicrm-core/pull/11364) or wait for 4.7.30 release.
  
  > **Comments:**
  > **username_0**: Thanks for the answer, username_1. Yes that seems to address issue #2, but not issue #1?  
  > **username_1**: I feel it does please try  
  > **username_0**: Oh ok, will do so.  
  > **username_0**: I'm not having much success. I'll admit I'm not sure exactly what procedure I need to follow to apply the patch :-/  I've tried updating just the 11 files in the patch, and I've tried updating the whole codebase.  Both break my 4.7.29 installation. Are there any guides you could point me to?  
  > **username_0**: Ooops, I should have searched first, then posted after :-) https://civicrm.stackexchange.com/questions/4622/how-do-i-apply-a-patch-supplied-in-the-issue-queue-via-git  
  > **username_0**: OK, so I've applied the patch.  It seems to have fixed problem 2, but NOT problem 1.  I can make and save changes to records with Contact Subtypes, but first I see the "Contact Subtype" error as described above. If I click "OK" to ignore the warning, the record saves without complaining about custom addressees -- but all the custom subtype data is lost.   So as I feared, the patch does address the custom addressee issue, but not this contact subtype problem.  Other ideas?  
  > **username_0**: I'm going to go ahead and accept this answer, because it did solve my question about the Custom Addressee issue. But since it seems these two issues aren't in fact related, I'm going to open a new question with just the Contact Subtype error. thanks again for your help here!  
  
  ---
  
  