Giving you the time you need to stay up to date and secure.
Up to 5 years
As with many other OpenSource projects we need to drop official, free support at some point. But as we know there are times when the amount of time to migrate from one version to another is simply too short.
In these rare cases you now have the option to subscribe to a support plan. These plans help both the TYPO3 project and you. You fund the CMS team so they can spend the additional time on supporting TYPO3 CMS versions 4.5 and 6.2 as well as the future development of TYPO3 CMS as a whole.
We cannot stress enough that these plans are by no means a wildcard to postpone a necessary migration further than absolutely necessary and are a last-resort.
Certain sectors of the industry demand longer lifetimes of websites or applications than 3 years. This is where you can make use of our ELTS plans that allow to extend the lifetime of your project for up to two additional years. This gives you plenty of time to plan your upgrades to the newest TYPO3 version.
With our ELTS plan you can cover the following TYPO3 versions at the moment:
If popular demand requests periods longer than stated above, we might extend the support time even longer.
Our ELTS plans cover browser compatibility up to the newest versions - even if the regular support of a TYPO3 version would not cover these browsers or browser versions anymore.
So you won't have to worry about locking your editors out when IT starts rolling out those shiny new computers to your team.
But apart from editor happyness we also backport all changes to code compliant to TYPO3s platform promise, meaning you won't have to plan for updates of your application-service-layer like PHP or MySQL. TYPO3 ELTS versions will run smoothly on PHP and MySQL versions they were originally planned for.
Protecting the data of your company and users is one of the most important and time consuming tasks in IT. Our ELTS plans backport all security patches of current TYPO3 versions into the ELTS versions - thus offering the same level of security TYPO3 is known for with its current versions.
All security patches are announced to your technical contact so you can plan your rollouts with enough time in advance, reducing the workload of your IT-team.
/ extended year
/ extended year
/ extended year
A number of members of the TYPO3 Association approached us (the CMS Team) and asked for the possibility to extend the support for TYPO3 CMS 4.5 because they could not manage to get their migrations done in time.
Although some think of this as being an excuse for being lazy there are several valid reasons for this:
Supporting TYPO3 CMS 4.5 seems trivial at first but there are a lot of things to consider:
Taking all these factors into account, we needed to decide whether we make this edge-case a paid service or to hinder the development of future TYPO3 versions - we chose the continued development of TYPO3 CMS.
An instance is a set of up to 3+n TYPO3 installs (Live, Live Failover, Staging, Development per Developer) as long as the scope of the installation remains the same.
Here are some examples:
If you are unsure about your setup, contact us and we will help you out with the definition.
First off, it is important to make clear that migrating to TYPO3 CMS 6.2 or higher is never wrong advise.
Basically this extended support does not remove the reason to migrate, it just postpones the situation.
So by advising your client to migrate you actually saved the clients' money.
In case of problems you can contact Mathias Schreiber, the Product Owner of TYPO3 CMS and arrange for a meeting or a phone call to set things right.
"Expensive" is no absolute term. A car can be considered expensive, when compared to a piece of bread. So you need to put things in relation to each other.
I want to give you an example based on real world use-cases from 4.5 support.
So you see, supporting a TYPO3 version is probably a lot more work than you anticipated. At the same time we cannot be sure if we have security issues to patch or new browsers to maintain - making a reliable calculation simply impossible.
So we need to mix up our calculation so we can deliver the standard we always delivered.
Because we are fine traveling economy ;-)