Answers.Body: <p>This kind of question is hard to answer for an open source project like CiviCRM :-) There is no 'owner' of the product that can tell you this. Nor is there a group of paid developers that will be able to continue supporting this. Considering that I think it is an impossible question to answer, and the wrong one to ask at this point in time. It would have to be one of the considerations when starting with heavy customization.</p>
  
  <p>Having said that, I have worked in closed source situations where this kind of thing was promised by sales manager but never materialised :-). "No we will continue to support this version as long as you want to use it" and then a year later "we really urge you to upgrade as we will no longer support this version".</p>
  
  <p>As an individual and member of the CiviCRM community I would not be interested in keeping a 4.6 version alive in combination with PHP 7. It would probably mean changing the 4.6 to a new PHP 7 compliant subversion, and then keeping it alive. That would leave me hardly any space for making a living. But that is solely as an individual with none of the organizations I work with facing this problem. It is only my personal opinion, it does not mean it is not possible or will never happen.</p>
  
  <p>If there is a large group interested in doing this however you might be able to fund it. Or find partners that are willing to take this on. So I would really urge others to answer your question too!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-06T16:52:39.210Z
Answers.Text: Thanks for your comment. So if a developer made extensions for CiviCRM 4.6 LTS and PHP 5.6 while CiviCRM 4.7 and PHP7 were out, and advised clients to stay on 4.6 knowing the impending doom, do you think the customer should pay for the upgrades? Obviously, there are lots of financial models out there.
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-07T08:37:22.080Z
Answers.Text: I have no idea :-). Personally I always explain to any organization that there are real downsided to customization. And this is one of them. They tend to ignore the warnings :-). I assume you have not paid any licenses for CivICRM? And did not complain about that?
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-06T08:32:10.310Z
Answers.LastActivityDate: 2018-03-06T08:32:10.310Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>When PHP 5.6 reaches it end of life. It means basicly that no further updates are coming from the official php group. But it means you can still keep php 5.6 on your server it does not stop from working.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-06T16:51:13.453Z
Answers.Text: Correct me if I am wrong, but it also means there are no security updates?
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-06T17:02:42.533Z
Answers.Text: Yes it means there are no security updates. Unless the wider php community takes this role over from the php group. Which I dont think will happen. But the changes are more likely to happen than that a smaller comuunity as civicrm makes 4.6 compatible with php 7.
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-16T20:35:21.370Z
Answers.Text: All of the CiviCRM sites that I manage run with Drupal 7.x. While Drupal 7 core should be compatible with PHP 7.1 now, one has to check modules individually. And every Drupal site I manage has tons of modules. For me, at least, it makes the OP question moot; I'm going to have to keep running PHP 5.6 past EOL because it is way too much work to get Drupal 7 contrib modules working on PHP 7.1. Am I missing something?
Answers.UserDisplayName: Shai
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-06T08:49:24.827Z
Answers.LastActivityDate: 2018-03-06T08:49:24.827Z
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.Body: <p>Skvare was considering supporting 4.6 on php 7.  See <a href="https://issues.civicrm.org/jira/browse/CRM-17789?focusedCommentId=105743&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-105743" rel="nofollow noreferrer">this link</a>  </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-07T14:39:03.267Z
Answers.LastActivityDate: 2018-03-07T14:39:03.267Z
Answers.UserDisplayName: Aidan
Body: <p>If an organization is currently heavily invested into customizations built for CiviCRM 4.6 LTS, is it possible for them to continue using the LTS version of CiviCRM when PHP 5.6 EOL? (31 Dec 2018) and an upgrade to PHP 7+ is necessary?</p>
  
Tags: <php7>
Title: Will there be a LTS release of CiviCRM 4.6.x that supports PHP 7+
ThreadText: # Will there be a LTS release of CiviCRM 4.6.x that supports PHP 7+
  
  (Asked by: username_0 on 2018-03-06)
  
  If an organization is currently heavily invested into customizations built for CiviCRM 4.6 LTS, is it possible for them to continue using the LTS version of CiviCRM when PHP 5.6 EOL? (31 Dec 2018) and an upgrade to PHP 7+ is necessary?
  
  **Tags:** php7
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2018-03-06. Score: 5
  
  This kind of question is hard to answer for an open source project like CiviCRM :-) There is no 'owner' of the product that can tell you this. Nor is there a group of paid developers that will be able to continue supporting this. Considering that I think it is an impossible question to answer, and the wrong one to ask at this point in time. It would have to be one of the considerations when starting with heavy customization.
  
  Having said that, I have worked in closed source situations where this kind of thing was promised by sales manager but never materialised :-). "No we will continue to support this version as long as you want to use it" and then a year later "we really urge you to upgrade as we will no longer support this version".
  
  As an individual and member of the CiviCRM community I would not be interested in keeping a 4.6 version alive in combination with PHP 7. It would probably mean changing the 4.6 to a new PHP 7 compliant subversion, and then keeping it alive. That would leave me hardly any space for making a living. But that is solely as an individual with none of the organizations I work with facing this problem. It is only my personal opinion, it does not mean it is not possible or will never happen.
  
  If there is a large group interested in doing this however you might be able to fund it. Or find partners that are willing to take this on. So I would really urge others to answer your question too!
  
  > **Comments:**
  > **username_0**: Thanks for your comment. So if a developer made extensions for CiviCRM 4.6 LTS and PHP 5.6 while CiviCRM 4.7 and PHP7 were out, and advised clients to stay on 4.6 knowing the impending doom, do you think the customer should pay for the upgrades? Obviously, there are lots of financial models out there.  
  > **username_1**: I have no idea :-). Personally I always explain to any organization that there are real downsided to customization. And this is one of them. They tend to ignore the warnings :-). I assume you have not paid any licenses for CivICRM? And did not complain about that?  
  
  ---
  
  ### Answer by username_2 on 2018-03-06. Score: 4
  
  When PHP 5.6 reaches it end of life. It means basicly that no further updates are coming from the official php group. But it means you can still keep php 5.6 on your server it does not stop from working.
  
  > **Comments:**
  > **username_0**: Correct me if I am wrong, but it also means there are no security updates?  
  > **username_2**: Yes it means there are no security updates. Unless the wider php community takes this role over from the php group. Which I dont think will happen. But the changes are more likely to happen than that a smaller comuunity as civicrm makes 4.6 compatible with php 7.  
  > **username_3**: All of the CiviCRM sites that I manage run with Drupal 7.x. While Drupal 7 core should be compatible with PHP 7.1 now, one has to check modules individually. And every Drupal site I manage has tons of modules. For me, at least, it makes the OP question moot; I'm going to have to keep running PHP 5.6 past EOL because it is way too much work to get Drupal 7 contrib modules working on PHP 7.1. Am I missing something?  
  
  ---
  
  ### Answer by username_4 on 2018-03-07. Score: 3
  
  Skvare was considering supporting 4.6 on php 7. See [this link](https://issues.civicrm.org/jira/browse/CRM-17789?focusedCommentId=105743&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-105743)
  
  
  ---
  
  