Answers.Body: <p>Further research shows that this is indeed a known issue for this version of CiviCRM: <a href="https://issues.civicrm.org/jira/browse/CRM-17388" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17388</a> states that it has been fixed for version 4.7. That version is only in beta at the time of writing, so not of help on a production site. I wonder if this fix will be rolled into 4.6.x given that 4.6 is the new LTS (long term support) version?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-15T10:22:04.303Z
Answers.LastActivityDate: 2015-12-15T10:22:04.303Z
Answers.UserDisplayName: Graham
Answers.Body: <p>Graham, I found the fix here
  <a href="https://issues.civicrm.org/jira/browse/CRM-17388" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17388</a></p>
  
  <p>We had exactly the same issue but really thankful it is resolved with the patch</p>
  
  <p>Jon-man</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-03T18:54:41.743Z
Answers.LastActivityDate: 2016-09-03T18:54:41.743Z
Answers.UserDisplayName: Jon-man
Answers.Body: <p>Have you applied the changes to cividiscount.php as outlined from these issues?</p>
  
  <p><a href="https://github.com/dlobo/org.civicrm.module.cividiscount/pull/120" rel="nofollow">https://github.com/dlobo/org.civicrm.module.cividiscount/pull/120</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-18T16:28:39.457Z
Answers.LastActivityDate: 2016-01-18T16:28:39.457Z
Answers.UserDisplayName: Barbara Forbes-Lyons
Body: <p>Using D7/CiviCRM 4.6.10 and Cividiscount 3.1</p>
  
  <p>I've set up a discount code to enable current members to renew their membership at 50% of the standard membership fee. If i make the code non-automatic and enter it manually it works.</p>
  
  <p>Setting the automatic discount options for the code for the membership type and 'any current status' should ensure that if the user has the membership type and their status is one of the those considered current (i.e. New, Current, Grace) then they automatically get the discount, but I'm seeing nothing applied on the contribution page.</p>
  
  <p>The contribution page recognises the user as a current member, as it is displaying a message to tell the user when their current membership is due to expire, but it is not applying the discount, and nor it it displaying the "not eligible" message.</p>
  
  <p>Is this a known issue, or am I missing something subtle in the configuration?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-14T11:04:29.400Z
Comments.Text: I don't think you've missed anything, probably worth reporting on https://github.com/dlobo/org.civicrm.module.cividiscount. Can see some similar issues on the issue queue but not the exact same one.
Comments.UserDisplayName: Parvez Saleh
Tags: <civimember><cividiscount>
Title: Automatic discount for membership not working
ThreadText: # Automatic discount for membership not working
  
  (Asked by: username_0 on 2015-12-13)
  
  Using D7/CiviCRM 4.6.10 and Cividiscount 3.1
  
  I've set up a discount code to enable current members to renew their membership at 50% of the standard membership fee. If i make the code non-automatic and enter it manually it works.
  
  Setting the automatic discount options for the code for the membership type and 'any current status' should ensure that if the user has the membership type and their status is one of the those considered current (i.e. New, Current, Grace) then they automatically get the discount, but I'm seeing nothing applied on the contribution page.
  
  The contribution page recognises the user as a current member, as it is displaying a message to tell the user when their current membership is due to expire, but it is not applying the discount, and nor it it displaying the "not eligible" message.
  
  Is this a known issue, or am I missing something subtle in the configuration?
  
  **Tags:** civimember, cividiscount
  
  > **Comments:**
  > **username_1**: I don't think you've missed anything, probably worth reporting on https://github.com/dlobo/org.civicrm.module.cividiscount. Can see some similar issues on the issue queue but not the exact same one.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_0 on 2015-12-15. Score: 0 | Accepted answer
  
  Further research shows that this is indeed a known issue for this version of CiviCRM: <https://issues.civicrm.org/jira/browse/CRM-17388> states that it has been fixed for version 4.7. That version is only in beta at the time of writing, so not of help on a production site. I wonder if this fix will be rolled into 4.6.x given that 4.6 is the new LTS (long term support) version?
  
  
  ---
  
  ### Answer by username_2 on 2016-09-03. Score: 1
  
  username_0, I found the fix here
  <https://issues.civicrm.org/jira/browse/CRM-17388>
  
  We had exactly the same issue but really thankful it is resolved with the patch
  
  username_2
  
  
  ---
  
  ### Answer by username_3 on 2016-01-18. Score: 0
  
  Have you applied the changes to cividiscount.php as outlined from these issues?
  
  <https://github.com/dlobo/org.civicrm.module.cividiscount/pull/120>
  
  
  ---
  
  