Answers.Body: <p>The symptom was caused by a misconfigured membership priceset. Specifically, it had a price field with an assigned membership type that had been disabled.</p>
  
  <p>If you want to check your database for a similar issue, you can use this sql:</p>
  
  <pre>select pf.label,fv.id,fv.price_field_id,fv.is_active,fv.label,mtype.name,mtype.is_active from civicrm_price_field_value fv left join civicrm_membership_type mtype on fv.membership_type_id = mtype.id left join civicrm_price_field pf on pf.id = fv.price_field_id where fv.membership_type_id > 0 and fv.is_active = 1 and mtype.is_active != 1;</pre>
  
  <p>If that sql returns any rows, you probably want to disable the corresponding price field values in the price field labelled by the first column of the results.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-24T14:31:17.280Z
Answers.LastActivityDate: 2017-10-24T14:31:17.280Z
Answers.UserDisplayName: Alan Dixon
Body: <p>Using CiviCRM 4.6.31 with Drupal 7, I have a contribution page that uses membership price sets, and for one of the options, no contribution or membership is created, no credit card transaction occurs, and yet a receipt is generated and no error appears for the visitor who fills out the form with their credit card.</p>
  
Tags: <civicontribute><civimember>
Title: Why is my membership contribution page not generating a contribution or transaction?
ThreadText: # Why is my membership contribution page not generating a contribution or transaction?
  
  (Asked by: username_0 on 2017-10-24)
  
  Using CiviCRM 4.6.31 with Drupal 7, I have a contribution page that uses membership price sets, and for one of the options, no contribution or membership is created, no credit card transaction occurs, and yet a receipt is generated and no error appears for the visitor who fills out the form with their credit card.
  
  **Tags:** civicontribute, civimember
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-10-24. Score: 1
  
  The symptom was caused by a misconfigured membership priceset. Specifically, it had a price field with an assigned membership type that had been disabled.
  
  If you want to check your database for a similar issue, you can use this sql:
  
  ```
  select pf.label,fv.id,fv.price_field_id,fv.is_active,fv.label,mtype.name,mtype.is_active from civicrm_price_field_value fv left join civicrm_membership_type mtype on fv.membership_type_id = mtype.id left join civicrm_price_field pf on pf.id = fv.price_field_id where fv.membership_type_id > 0 and fv.is_active = 1 and mtype.is_active != 1;
  ```
  
  If that sql returns any rows, you probably want to disable the corresponding price field values in the price field labelled by the first column of the results.
  
  
  ---
  
  