Answers.Body: <p>I never found the cause to this, but ended up using a Rule in Drupal to set the member_since and join_date variables when a new membership is created.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-11T05:22:02.973Z
Answers.Text: good to know you found that as a workaround but somewhat worrying that something on your system is affecting this core feature
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-27T06:48:03.413Z
Answers.Text: Make sure you check https://civicrm.stackexchange.com/a/39407/245 in case it is the same problem on your site @kimberlie-davis
Answers.UserDisplayName: jitendra - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-11T04:01:28.200Z
Answers.LastActivityDate: 2018-12-11T04:01:28.200Z
Answers.UserDisplayName: Kimberlie Davis
Body: <p>We recently upgraded from Civi 4.6.23 to 5.3.2.  The upgrade has gone fairly smoothly, but today we discovered a problem where the Member Since and Start Dates are not being set for any new memberships started since the day we upgraded.  Though these members are being giving the status of "Current", they are not being given correct access to our site.</p>
  
  <p>I've checked our error logs, and there are no errors.  I also checked the database, and the database does not have a Member Since or Start Date, and has no record of a membership in the member_log table.</p>
  
  <p>In this picture, you can see that there is no date set for Member Since or Start Date:
  <a href="https://i.sstatic.net/DVJSN.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/DVJSN.png" alt=""></a></p>
  
  <p>If we got to edit the member, though, it does have a Member Since date.  But, still not Start Date.
  <a href="https://i.sstatic.net/SahJA.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/SahJA.png" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-30T03:05:05.157Z
Comments.Text: That looks like a serious data loss. If you have logging enabled, you can update `member_since` and `start_date` columns in `civicrm_membership` table looking at the last (not empty) value in `log_civicrm_membership`.
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-30T03:55:40.177Z
Comments.Text: Do you have any extensions installed which deal with dates and/or Membership?  What about custom override files?
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-31T04:42:13.187Z
Comments.Text: Hi, sorry an important detail I guess I left off, this is only affecting new memberships since the upgrade.  All memberships from before are working fine.  We do not have any extensions or custom overrides that would be affecting this.
Comments.UserDisplayName: Kimberlie Davis
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-26T23:17:35.533Z
Comments.Text: I have looked through the error logs, and there doesn't seem to be any errors causing this. There was a Geocoder error being thrown when a membership is created, but I resolved that error and it did not resolve the membership date issue.
  
  I went back to an older version of our site, and was able to create a membership without issue.  I also updated to the latest version, and still ran into this issue.
Comments.UserDisplayName: Kimberlie Davis
Tags: <civimember>
Title: Start/member since dates not being set since upgrade to 5.3.2
ThreadText: # Start/member since dates not being set since upgrade to 5.3.2
  
  (Asked by: username_0 on 2018-10-29)
  
  We recently upgraded from Civi 4.6.23 to 5.3.2. The upgrade has gone fairly smoothly, but today we discovered a problem where the Member Since and Start Dates are not being set for any new memberships started since the day we upgraded. Though these members are being giving the status of "Current", they are not being given correct access to our site.
  
  I've checked our error logs, and there are no errors. I also checked the database, and the database does not have a Member Since or Start Date, and has no record of a membership in the member\_log table.
  
  In this picture, you can see that there is no date set for Member Since or Start Date:
  [![](https://i.sstatic.net/DVJSN.png)](https://i.sstatic.net/DVJSN.png)
  
  If we got to edit the member, though, it does have a Member Since date. But, still not Start Date.
  [![enter image description here](https://i.sstatic.net/SahJA.png)](https://i.sstatic.net/SahJA.png)
  
  **Tags:** civimember
  
  > **Comments:**
  > **username_1**: That looks like a serious data loss. If you have logging enabled, you can update `member_since` and `start_date` columns in `civicrm_membership` table looking at the last (not empty) value in `log_civicrm_membership`.  
  > **username_2**: Do you have any extensions installed which deal with dates and/or Membership?  What about custom override files?  
  > **username_0**: Hi, sorry an important detail I guess I left off, this is only affecting new memberships since the upgrade.  All memberships from before are working fine.  We do not have any extensions or custom overrides that would be affecting this.  
  > **username_0**: I have looked through the error logs, and there doesn't seem to be any errors causing this. There was a Geocoder error being thrown when a membership is created, but I resolved that error and it did not resolve the membership date issue.  I went back to an older version of our site, and was able to create a membership without issue.  I also updated to the latest version, and still ran into this issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-12-11. Score: 1 | Accepted answer
  
  I never found the cause to this, but ended up using a Rule in Drupal to set the member\_since and join\_date variables when a new membership is created.
  
  > **Comments:**
  > **username_3**: good to know you found that as a workaround but somewhat worrying that something on your system is affecting this core feature  
  > **username_1**: Make sure you check https://civicrm.stackexchange.com/a/39407/245 in case it is the same problem on your site @username_0-username_0  
  
  ---
  
  