Answers.Body: <p>OK, so the civirules 1.2 extension was causing the problem.  The problem is documented a bit here: <a href="https://github.com/CiviCooP/org.civicoop.civirules/issues/132" rel="nofollow noreferrer">https://github.com/CiviCooP/org.civicoop.civirules/issues/132</a></p>
  
  <p>Luckily I hadn't set up at civirules stuff so it was easy to just disable it.  Maybe in the future I'll use an updated version of it.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-19T20:02:32.147Z
Answers.LastActivityDate: 2017-09-19T20:02:32.147Z
Answers.UserDisplayName: Matt Muchowski
Body: <pre><code>I'm using civicrm 4.7.17 on drupal 7.54.  Logged in with administrator rights.
  
  When I try to add a new field, (admin -&gt; customize data and screen -&gt; custom fields) everything works fine.  I create a new set, no problem, but then when I add a new field to the set, and click on save, it just hangs, loading forever. 
  
  This seems to be a new thing as I've created lots of custom fields before. 
  </code></pre>
  
  <p>Any ideas?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-19T18:34:08.427Z
Comments.Text: When you go to add a custom field, please right-click the **Add Custom Field** button and select "Open in New Tab".  When you save the custom field, you should get a more informative error. Better still, first enable debugging. Go to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save". Repeat the steps that caused your error, and you'll see much a more detailed error. Please update this question with the expanded error and backtrace - and don't forget to disable debug/backtrace when you're done!
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-19T19:09:12.433Z
Comments.Text: That would make sense to debug it first.  So when I made a new tab, and tried to save, it had this error, " Sorry but we are not able to provide this at the moment.  id is not a valid integer"
Comments.UserDisplayName: Matt Muchowski
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-19T19:30:07.160Z
Comments.Text: Added the debugging to the original post
Comments.UserDisplayName: Matt Muchowski
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-20T16:11:12.813Z
Comments.Text: Glad you worked it out!  For reference - the error you gave is the "debug" info but not the "backtrace".  The debug shows the error - but the backtrace shows where in the code that error takes place.  Both are often necessary to solve a problem.
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <custom-fields>
Title: New Fields Won't Save
ThreadText: # New Fields Won't Save
  
  (Asked by: username_0 on 2017-09-19)
  
  I'm using civicrm 4.7.17 on drupal 7.54.  Logged in with administrator rights.
  
  When I try to add a new field, (admin -> customize data and screen -> custom fields) everything works fine.  I create a new set, no problem, but then when I add a new field to the set, and click on save, it just hangs, loading forever. 
  
  This seems to be a new thing as I've created lots of custom fields before. 
  
  Any ideas?
  
  **Tags:** custom-fields
  
  > **Comments:**
  > **username_1**: When you go to add a custom field, please right-click the **Add Custom Field** button and select "Open in New Tab".  When you save the custom field, you should get a more informative error. Better still, first enable debugging. Go to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save". Repeat the steps that caused your error, and you'll see much a more detailed error. Please update this question with the expanded error and backtrace - and don't forget to disable debug/backtrace when you're done!  
  > **username_0**: That would make sense to debug it first.  So when I made a new tab, and tried to save, it had this error, " Sorry but we are not able to provide this at the moment.  id is not a valid integer"  
  > **username_0**: Added the debugging to the original post  
  > **username_1**: Glad you worked it out!  For reference - the error you gave is the "debug" info but not the "backtrace".  The debug shows the error - but the backtrace shows where in the code that error takes place.  Both are often necessary to solve a problem.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-09-19. Score: 1 | Accepted answer
  
  OK, so the civirules 1.2 extension was causing the problem. The problem is documented a bit here: <https://github.com/CiviCooP/org.civicoop.civirules/issues/132>
  
  Luckily I hadn't set up at civirules stuff so it was easy to just disable it. Maybe in the future I'll use an updated version of it.
  
  
  ---
  
  