Answers.Body: <p>I'll call this an answer, only because it worked. I discovered this link after googling around. civicrm.org/extensions/nzcofuzioncivitoken
  After installing the extension, my Expiration Template now contains:</p>
  
  <blockquote>
    <p>Your membership is paid thru: {latestcurrentmembership.allend_date}</p>
    
    <p>Member since: {latestcurrentmembership.alljoin_date}</p>
  </blockquote>
  
  <p>Since this seems a practical necessity for Membership-related Scheduled Reminders, I updated the documentation for Membership > Renewals to point to this extension for others who wish to associate membership information to the contact in the reminder.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-12T19:48:00.547Z
Answers.Text: hi Karl - as a free open source project most of what gets added to civi is done because someone is able to contribute the work, or the funds. So it is always helpful when firing in a 'please' to indicate if you can contribute either. Beyond that, there may be other reasons why contributions of work remain as extensions rather than being incorporated in to core code but I can't offer a technical reason in this case. Lastly, another way to contribute is through improving documentation, so if there is somewhere that you think some signposts could be added then please give it a go.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-12T21:52:27.487Z
Answers.Text: Thanks for the suggestions, and I will take a whack at the documentation - there are two places for it, under Scheduled Reminders and under the specific pointer to Membership Renewals. Such signposts would have helped me as that was where I first looked. This is our first CiviCRM instance, somewhat on trial. If it sticks we'll certainly contribute funds and possibly work, too, if we really get into it.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-14T00:15:00.583Z
Answers.Text: Excuse me for asking a simple question, from a subversion (not git) person. I created a git clone on my win 10 desktop where I have GIT GUI and GIT Bash installed. I edited just one file docs/membership/renewals.md. I committed to my local working copy and want to push it back to the master branch. Note my SSH keys are all set up with github.com. What URL should I use to push it back? Will it only send the one file, or will it try to create a new branch? I'm hoping there is some sort of review process before accepting and don't want to mess anything up. Thanks for any little help here.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-14T00:44:02.390Z
Answers.Text: Actually, instead of working from a clone, I read the README.md and then simply forked and edited that single page in my browser. I then put in a comment and created a pull request. Is that all there is to it?
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-14T01:36:13.763Z
Answers.Text: sounds right. put the PR here and someone might engage
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-15T02:39:00.547Z
Answers.Text: Pete - it was reviewed and committed. Since I'm a real believer in good documentation, it's nice to know there is a good process in place. Thanks again for pointing me to that.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-15T06:06:28.703Z
Answers.Text: I updated my answer to reflect the documentation change, accepted it, but I could not +1 it because it was my own answer. Oh well ;)
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-15T18:52:25.023Z
Answers.Text: then i will +1 it ;-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-12T18:54:52.277Z
Answers.LastActivityDate: 2016-12-15T06:04:41.613Z
Answers.LastEditDate: 2016-12-15T06:04:41.613Z
Answers.UserDisplayName: Karl Rudnick
Body: <p>We are having a problem in setting up our Scheduled Reminders for Membership Renewals. The reminders are sent out as scheduled, but the relationship between Contact to Membership (which is through a foreign key in the database) seems to be broken as far as inserting tokens into the renewal email.</p>
  
  <p>For example, adding lines to our Expiration Template like:</p>
  
  <p>Paid thru: {membership.end_date}
  Member since: {membership.join_date}</p>
  
  <p>only replaces the tokens with blank in our email tests.</p>
  
  <p>I found <a href="https://forum.civicrm.org/index.php?topic=36009.0" rel="nofollow noreferrer">this reference from 2015</a> in the old CiviCRM Community Forum, but am re-posting here. I can't believe this is an unresolved issue. I use other membership software, like aMember PRO, and this is one of the most basic functions in renewal reminder emails.</p>
  
  <p>If it has been resolved, please point me to a solution. My searches in this Stack Exchange haven't worked for me.</p>
  
  <p>Thanks for any help!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-12-12T18:03:38.703Z
Comments.Text: What version of Civi are you using?  Which CMS?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-12-12T18:12:51.267Z
Comments.Text: Sorry I didn't add that. CiviCRM 4.7.12 with WordPress 4.6.1
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-12-12T18:14:15.137Z
Comments.Text: Also, just discovered this link after googling around. https://civicrm.org/extensions/nzcofuzioncivitoken If I need this, why isn't this basic core functionality?
Comments.UserDisplayName: Karl Rudnick
Tags: <civimail><civimember><tokens>
Title: Civimember: token for membership end date not working
ThreadText: # Civimember: token for membership end date not working
  
  (Asked by: username_0 on 2016-12-12)
  
  We are having a problem in setting up our Scheduled Reminders for Membership Renewals. The reminders are sent out as scheduled, but the relationship between Contact to Membership (which is through a foreign key in the database) seems to be broken as far as inserting tokens into the renewal email.
  
  For example, adding lines to our Expiration Template like:
  
  Paid thru: {membership.end\_date}
  Member since: {membership.join\_date}
  
  only replaces the tokens with blank in our email tests.
  
  I found [this reference from 2015](https://forum.civicrm.org/index.php?topic=36009.0) in the old CiviCRM Community Forum, but am re-posting here. I can't believe this is an unresolved issue. I use other membership software, like aMember PRO, and this is one of the most basic functions in renewal reminder emails.
  
  If it has been resolved, please point me to a solution. My searches in this Stack Exchange haven't worked for me.
  
  Thanks for any help!
  
  **Tags:** civimail, civimember, tokens
  
  > **Comments:**
  > **username_1**: What version of Civi are you using?  Which CMS?  
  > **username_0**: Sorry I didn't add that. CiviCRM 4.7.12 with WordPress 4.6.1  
  > **username_0**: Also, just discovered this link after googling around. https://civicrm.org/extensions/nzcofuzioncivitoken If I need this, why isn't this basic core functionality?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-12-12. Score: 2 | Accepted answer
  
  I'll call this an answer, only because it worked. I discovered this link after googling around. civicrm.org/extensions/nzcofuzioncivitoken
  After installing the extension, my Expiration Template now contains:
  
  > Your membership is paid thru: {latestcurrentmembership.allend\_date}
  >
  > Member since: {latestcurrentmembership.alljoin\_date}
  
  Since this seems a practical necessity for Membership-related Scheduled Reminders, I updated the documentation for Membership > Renewals to point to this extension for others who wish to associate membership information to the contact in the reminder.
  
  > **Comments:**
  > **username_2**: hi Karl - as a free open source project most of what gets added to civi is done because someone is able to contribute the work, or the funds. So it is always helpful when firing in a 'please' to indicate if you can contribute either. Beyond that, there may be other reasons why contributions of work remain as extensions rather than being incorporated in to core code but I can't offer a technical reason in this case. Lastly, another way to contribute is through improving documentation, so if there is somewhere that you think some signposts could be added then please give it a go.  
  > **username_0**: Thanks for the suggestions, and I will take a whack at the documentation - there are two places for it, under Scheduled Reminders and under the specific pointer to Membership Renewals. Such signposts would have helped me as that was where I first looked. This is our first CiviCRM instance, somewhat on trial. If it sticks we'll certainly contribute funds and possibly work, too, if we really get into it.  
  > **username_0**: Excuse me for asking a simple question, from a subversion (not git) person. I created a git clone on my win 10 desktop where I have GIT GUI and GIT Bash installed. I edited just one file docs/membership/renewals.md. I committed to my local working copy and want to push it back to the master branch. Note my SSH keys are all set up with github.com. What URL should I use to push it back? Will it only send the one file, or will it try to create a new branch? I'm hoping there is some sort of review process before accepting and don't want to mess anything up. Thanks for any little help here.  
  > **username_0**: Actually, instead of working from a clone, I read the README.md and then simply forked and edited that single page in my browser. I then put in a comment and created a pull request. Is that all there is to it?  
  > **username_2**: sounds right. put the PR here and someone might engage  
  > **username_0**: Pete - it was reviewed and committed. Since I'm a real believer in good documentation, it's nice to know there is a good process in place. Thanks again for pointing me to that.  
  > **username_0**: I updated my answer to reflect the documentation change, accepted it, but I could not +1 it because it was my own answer. Oh well ;)  
  > **username_2**: then i will +1 it ;-)  
  
  ---
  
  