Body: <p>After upgrading to CiviCRM to 4.7 we cannot use the inline editing for one of our sets of custom fields.  You can see on the <em>Application Fields</em> that they cannot be edited with the inline editor. </p>
  
  <p><a href="https://i.sstatic.net/RhBa7.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/RhBa7.png" alt="Application Fields Cannot Be Edited"></a></p>
  
  <p>When you look at the <em>Legacy Fields</em> they can be edited with inline editing. <a href="https://i.sstatic.net/ujWTD.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ujWTD.png" alt="enter image description here"></a></p>
  
  <p>I have cleared caches and turned off extensions to see if that would change anything and it did not.  </p>
  
  <p>Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T02:20:20.440Z
Comments.Text: Did you by any chance, change the custom field type recently? Have you tried going to these fields, and then simply, resaving it again?
Comments.UserDisplayName: Kristine
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T02:48:57.147Z
Comments.Text: @Kristine I did not change the fields.  The only change was the upgrade from 4.6 to 4.7. The fields work perfectly if I do the full page edit.  I did as you suggested with saving the fields again and this did not have any change.
Comments.UserDisplayName: Josh
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T06:29:43.560Z
Comments.Text: Please do check the in_selector field in the civicrm_custom_field table? I stumbled over that one before. It should be set to 1.
Comments.UserDisplayName: ErikH - CiviCooP
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T12:52:40.797Z
Comments.Text: What CMS are you using?
Comments.UserDisplayName: KilakwaBT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T14:06:47.283Z
Comments.Text: Did you check for messages in the browser console? If you have javascript issues, they might show up there.
Comments.UserDisplayName: Alan Dixon
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T15:27:24.343Z
Comments.Text: Thank you for all the thoughts/questions.  The in_selector value is '0'. I checked and this is the same for fields that can be edited and those that are not working.  --  We are using Drupal 7. -- When I look at the console there are no JS errors but lots of  'violation's. (https://s3-us-west-2.amazonaws.com/onlinesharing18/Screen+Shot+2017-05-02+at+9.23.14+AM.png). Thanks!
Comments.UserDisplayName: Josh
Tags: <contacts><custom-fields>
Title: Cannot Use Inline Editing On Custom Fields
ThreadText: # Cannot Use Inline Editing On Custom Fields
  
  (Asked by: username_0 on 2017-05-02)
  
  After upgrading to CiviCRM to 4.7 we cannot use the inline editing for one of our sets of custom fields. You can see on the *Application Fields* that they cannot be edited with the inline editor.
  
  [![Application Fields Cannot Be Edited](https://i.sstatic.net/RhBa7.png)](https://i.sstatic.net/RhBa7.png)
  
  When you look at the *Legacy Fields* they can be edited with inline editing. [![enter image description here](https://i.sstatic.net/ujWTD.png)](https://i.sstatic.net/ujWTD.png)
  
  I have cleared caches and turned off extensions to see if that would change anything and it did not.
  
  Thanks!
  
  **Tags:** contacts, custom-fields
  
  > **Comments:**
  > **username_1**: Did you by any chance, change the custom field type recently? Have you tried going to these fields, and then simply, resaving it again?  
  > **username_0**: @username_1 I did not change the fields.  The only change was the upgrade from 4.6 to 4.7. The fields work perfectly if I do the full page edit.  I did as you suggested with saving the fields again and this did not have any change.  
  > **username_2**: Please do check the in_selector field in the civicrm_custom_field table? I stumbled over that one before. It should be set to 1.  
  > **username_3**: What CMS are you using?  
  > **username_4**: Did you check for messages in the browser console? If you have javascript issues, they might show up there.  
  > **username_0**: Thank you for all the thoughts/questions.  The in_selector value is '0'. I checked and this is the same for fields that can be edited and those that are not working.  --  We are using Drupal 7. -- When I look at the console there are no JS errors but lots of  'violation's. (https://s3-us-west-2.amazonaws.com/onlinesharing18/Screen+Shot+2017-05-02+at+9.23.14+AM.png). Thanks!  
  
  ---
  
  ## 0 answers
  
  