Answers.Body: <p>@Tapash - I tried to reproduce one of the specific issues that you reported post upgrade to 4.6.16 : <a href="https://civicrm.stackexchange.com/questions/11796/fatal-error-when-renewing-membership-after-upgrading-to-4-6-16/11798#11798">Fatal Error when renewing membership after Upgrading to 4.6.16</a></p>
  
  <p>But I can not - it's all working fine on our 4.6.16s - I also don't have any reports of any of our projects experiencing issues on 4.6.16 I'm wondering if perhaps something went wrong during your recent upgrade? </p>
  
  <p>General recipe for this is to restore both code base (files) &amp; databases back to 4.6.14 and then to run the upgrade script [to 4.6.16] again. If you can: run it via drush - it may give you some warnings/errors that give you some insight as to what's going on. </p>
  
  <blockquote>
    <p>sudo -u apache drush civicrm-upgrade-db</p>
  </blockquote>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T15:35:23.867Z
Answers.LastActivityDate: 2016-05-13T15:35:23.867Z
Answers.LastEditDate: 2017-04-13T12:53:13.207Z
Answers.UserDisplayName: KarinG - Semper IT
Answers.Body: <p>6.18 which is out now. There were regressions in 4.6.16 which had fixes in 4.6.17 &amp; 4.6.18 due to fixing a difficult security issue</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-12T18:39:05.370Z
Answers.LastActivityDate: 2016-06-12T18:39:05.370Z
Answers.UserDisplayName: Eileen
Body: <p>Since I have upgraded to 4.6.14 > 4.6.16 everything is so messed up on my website. Events that are not yet finished they are not appearing on the dashboard, Cant change the event end date, clicking save button returns only endless CiviCRM logo loop. Cant renew membership. Keep getting the message "The Contact Sub Type does not match the Contact type for this record". </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T15:01:17.390Z
Comments.Text: Could you paste the errors you're getting in the error log?
Comments.UserDisplayName: Brad Xanti
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T15:02:39.333Z
Comments.Text: Also, did you back up your site before upgrading?  It might be best to just revert to that.
Comments.UserDisplayName: Brad Xanti
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-14T07:36:40.913Z
Comments.Text: Yes, I have kept a backup, but the complication arises due to entries we have made after upgrade. then all new entries have to be made manually? I was thinking, what would be complication if I use database version 4.6.16 but codebase 4.6.14? I have tried that on a demo install and all worked fine!!
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-16T15:26:32.947Z
Comments.Text: Unfortunately, AFAIK, you would have to make the new entries manually.  But it looks like from your other post you've gotten everything figured out.  Cheers!
Comments.UserDisplayName: Brad Xanti
Tags: <civievent><civimember>
Title: Keep getting HTTP ERROR 500 since upgraded to 4.6.16
ThreadText: # Keep getting HTTP ERROR 500 since upgraded to 4.6.16
  
  (Asked by: username_0 on 2016-05-13)
  
  Since I have upgraded to 4.6.14 > 4.6.16 everything is so messed up on my website. Events that are not yet finished they are not appearing on the dashboard, Cant change the event end date, clicking save button returns only endless CiviCRM logo loop. Cant renew membership. Keep getting the message "The Contact Sub Type does not match the Contact type for this record".
  
  **Tags:** civievent, civimember
  
  > **Comments:**
  > **username_1**: Could you paste the errors you're getting in the error log?  
  > **username_1**: Also, did you back up your site before upgrading?  It might be best to just revert to that.  
  > **username_0**: Yes, I have kept a backup, but the complication arises due to entries we have made after upgrade. then all new entries have to be made manually? I was thinking, what would be complication if I use database version 4.6.16 but codebase 4.6.14? I have tried that on a demo install and all worked fine!!  
  > **username_1**: Unfortunately, AFAIK, you would have to make the new entries manually.  But it looks like from your other post you've gotten everything figured out.  Cheers!  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-05-13. Score: 1
  
  @username_0 - I tried to reproduce one of the specific issues that you reported post upgrade to 4.6.16 : [Fatal Error when renewing membership after Upgrading to 4.6.16](https://civicrm.stackexchange.com/questions/11796/fatal-error-when-renewing-membership-after-upgrading-to-4-6-16/11798#11798)
  
  But I can not - it's all working fine on our 4.6.16s - I also don't have any reports of any of our projects experiencing issues on 4.6.16 I'm wondering if perhaps something went wrong during your recent upgrade?
  
  General recipe for this is to restore both code base (files) & databases back to 4.6.14 and then to run the upgrade script [to 4.6.16] again. If you can: run it via drush - it may give you some warnings/errors that give you some insight as to what's going on.
  
  > sudo -u apache drush civicrm-upgrade-db
  
  
  ---
  
  ### Answer by username_3 on 2016-06-12. Score: 0
  
  6.18 which is out now. There were regressions in 4.6.16 which had fixes in 4.6.17 & 4.6.18 due to fixing a difficult security issue
  
  
  ---
  
  