support lifecycle
Permalink
Is there any sort of support lifecycle for concrete5? e.g. is Concrete5 5.6.3.5 still supported, are security updates still released for this version etc, do the developers issue routine security updates for concrete5? How old exactly is this release?
thanks for the response... are there any risks in using such an old version of concrete5, aside from support/patches.. need to understand the need/urgency for an upgrade and pros/cons of staying on the current version.
the risks are the same as with any system that will eventually stop receiving security updates on its core and its plugins.
Somebody somewhere MIGHT one day try to break your stuff.
Another also strong possibility is that technology will evolve in a way that will make the old stuff stop working altogether. If your host decides to switch to PHP 7 without asking for that and you're still using legacy, your site will break.
The good news is none of that will happen overnight so you still have time to think about it and decide on the best way to deal with that. And really, you should be thinking about it.
Somebody somewhere MIGHT one day try to break your stuff.
Another also strong possibility is that technology will evolve in a way that will make the old stuff stop working altogether. If your host decides to switch to PHP 7 without asking for that and you're still using legacy, your site will break.
The good news is none of that will happen overnight so you still have time to think about it and decide on the best way to deal with that. And really, you should be thinking about it.
PS. There's lots of websites running 5.6 on PHP 7.1. It runs smooth and doesn't give any problems.
Like @ramonleenders said, it works with an unofficial update and I don't think it's ready for 7.2 but I might be wrong.
It does have that same Object class 5.7 and 8 have that had to be renamed in 8.4 and I'm pretty sure constants are not quoted when defined so I'd say 7.2 might be an issue.
It does have that same Object class 5.7 and 8 have that had to be renamed in 8.4 and I'm pretty sure constants are not quoted when defined so I'd say 7.2 might be an issue.
https://www.concrete5.org/developers/developer-downloads...
You will see this in the list:
5.6.3.5 (6-9-2017)
So it's 1 year and 2 months ago since the last 5.6.x release. There is an unofficial update to support PHP 7.x on GitHub if I'm not mistaken (since 5.6 doesn't run on PHP 7.x yet, officially).
There is no end date for the legacy 5.6 yet. See this quote in specific:
"Before we’d announce a end of life date for the concrete5 legacy security updates, we’d announce a stop date for marketplace sales of version 6 add-ons and themes here at concrete5.org. You should expect that to happen before too long and it’ll be a good indicator that we’re really closing the door on concrete5 legacy." - from this blog post -->
https://www.concrete5.org/about/blog/core-roadmap/concrete5-legacy-v...