Answers.Body: <p>The cause of this symptom was a mis-configured, hidden price set. There is a hidden price set and field (both of id = 1, at least on this site) that are used for non-price-set contributions. On this site, the price set had no financial type configured and the price field was disabled, a fact that was alerted on the System Status page. Setting a valid financial type and enabling the price field was actually kind of tricky (a combination of hacking urls and sql), but it fixed the problem.</p>
  
  <p>I don't know how we ended up with that mis-configuration, an error in the executing code would have been nice.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-25T19:32:56.800Z
Answers.LastActivityDate: 2017-10-25T19:32:56.800Z
Answers.UserDisplayName: Alan Dixon
Body: <p>Using Drupal 7 and CiviCRM 4.7.22, I am unable to record any contributions unless I use a priceset, i.e. if I use this form:
  /civicrm/contact/view/contribution?reset=1&amp;action=add&amp;cid=mycid&amp;context=contribution and put in any amount without using a priceset, then the contribution is stored as $0 without showing any errors.</p>
  
Tags: <civicontribute>
Title: Why can't I record backend contributions without using a priceset?
ThreadText: # Why can't I record backend contributions without using a priceset?
  
  (Asked by: username_0 on 2017-10-25)
  
  Using Drupal 7 and CiviCRM 4.7.22, I am unable to record any contributions unless I use a priceset, i.e. if I use this form:
  /civicrm/contact/view/contribution?reset=1&action=add&cid=mycid&context=contribution and put in any amount without using a priceset, then the contribution is stored as $0 without showing any errors.
  
  **Tags:** civicontribute
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-10-25. Score: 1
  
  The cause of this symptom was a mis-configured, hidden price set. There is a hidden price set and field (both of id = 1, at least on this site) that are used for non-price-set contributions. On this site, the price set had no financial type configured and the price field was disabled, a fact that was alerted on the System Status page. Setting a valid financial type and enabling the price field was actually kind of tricky (a combination of hacking urls and sql), but it fixed the problem.
  
  I don't know how we ended up with that mis-configuration, an error in the executing code would have been nice.
  
  
  ---
  
  