Pau Lo
asked on
end-of-life CMS query
I have a query in relation to CMS support lifecycles. One of our partners uses a legacy version of concrete5 to maintain there website, who issued an end-of-life announcement last month:
https://www.concrete5.org/about/blog/community-blog/official-end-life-concrete5-version-6x
The note does clearly say that critical security updates will still be applied for a further 12 months, but I want to identify the risks in using this at present. Apart from 'critical updates' what other types of support/update would you receive if you move to a supported version of the software, that they will be missing out on while still operating the legacy version? I would like them to be more reactive and rather than wait right up until the end of the 12 month period, and upgrade now to a supported release, but I need some more examples of why this is required at this stage/what they are missing out on/risks in using the legacy version.
https://www.concrete5.org/about/blog/community-blog/official-end-life-concrete5-version-6x
The note does clearly say that critical security updates will still be applied for a further 12 months, but I want to identify the risks in using this at present. Apart from 'critical updates' what other types of support/update would you receive if you move to a supported version of the software, that they will be missing out on while still operating the legacy version? I would like them to be more reactive and rather than wait right up until the end of the 12 month period, and upgrade now to a supported release, but I need some more examples of why this is required at this stage/what they are missing out on/risks in using the legacy version.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Concrete5 has a marketplace available that allows you to install templates (designs) and features (such as cookie control, form managers, etc). Many of the features of your existing sites may make use of these extensions. Without access to the marketplace, you may not be able to update them (or at the very least you may need to update them manually). It's also possible that vendors of extensions may choose to no longer support older versions of Concrete5.
With that in mind, it really is best to keep as up to date as you can.
With that in mind, it really is best to keep as up to date as you can.
ASKER
could you elaborate a bit on this, as I am new to concrete5. What do you mean by 'disable it' and could you expand on the significance