Answers.Body: <p>This turned out to be a bug in said version and is now fixed.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-10T12:02:33.640Z
Answers.LastActivityDate: 2018-07-10T12:02:33.640Z
Answers.UserDisplayName: naomi
Body: <p>After upgrading to 4.7.1, when trying to edit custom fields in tabs, the edit popup opens and you can enter data (and it does client-side validation) but the data is not saved.</p>
  
  <p>Moving the set of custom fields to <code>inline</code> rather than <code>tab</code> is a successful workaround.</p>
  
  <p>I couldn't reproduce it on demo, but I could on my dev site which has no extensions in common so I think it is unlikely to be due to an extension. I noticed demo is running 4.7.2 ... is this issue known to be fixed in 4.7.2? If so I'll just wait for the release and work around in the meantime.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-02-17T17:32:41.433Z
Comments.Text: 4.7.2 was released just this morning! https://civicrm.org/blogs/kurund/announcing-civicrm-472-and-4613-release
Comments.UserDisplayName: Allen Hutchison
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-02-17T19:02:11.773Z
Comments.Text: @AllenHutchison great, thanks - I'll try it!
Comments.UserDisplayName: naomi
Tags: <custom-fields><4.7>
Title: Custom fields in tabs are not editable since upgrade to 4.7.1
ThreadText: # Custom fields in tabs are not editable since upgrade to 4.7.1
  
  (Asked by: username_0 on 2016-02-17)
  
  After upgrading to 4.7.1, when trying to edit custom fields in tabs, the edit popup opens and you can enter data (and it does client-side validation) but the data is not saved.
  
  Moving the set of custom fields to `inline` rather than `tab` is a successful workaround.
  
  I couldn't reproduce it on demo, but I could on my dev site which has no extensions in common so I think it is unlikely to be due to an extension. I noticed demo is running 4.7.2 ... is this issue known to be fixed in 4.7.2? If so I'll just wait for the release and work around in the meantime.
  
  **Tags:** custom-fields, 4.7
  
  > **Comments:**
  > **username_1**: 4.7.2 was released just this morning! https://civicrm.org/blogs/kurund/announcing-civicrm-472-and-4613-release  
  > **username_0**: @username_1 great, thanks - I'll try it!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-07-10. Score: 2
  
  This turned out to be a bug in said version and is now fixed.
  
  
  ---
  
  