- Simply porting the site is going to be a lot of work.
- We just did our site a few years ago and don't have the budget for it.
- Things we rely upon didn't make it to 2.5.
- We hate change.
- The site is outdated; if we're going to update it we want to redesign it and that's a big job.
- There's no reason to upgrade (AKA "if it ain't broke, don't fix it").
- You're only telling me I need to upgrade because you want more business.
Every web site is different, so each of the reasons above can be more or less relevant depending on circumstances. At one end of the spectrum is the hobby site that generates no revenue, and doesn't have much traffic. A site that could be off line for a few weeks or months and not suffer. I'm going to exclude them from this discussion.
For everyone else, the question to ask is "what's the cost of having my site suddenly go to an 'under construction' page?" What's the monetary value? What's the value of lost reputation? Take a serious look at your situation and try to come up with a reasonable number. Compare this with the cost of upgrading your site. If the numbers are close, it's probably a good idea to start budgeting. If the cost is significantly higher than upgrading, find the budget now because it's time to start planning!
Here's the key issue: the technologies that Joomla uses, most significantly PHP, are also changing over time. This chart illustrates the problem for Joomla 1.5:
|PHP Version||Runs Joomla 1.5?||Status|
|5.2||Yes||Unsupported, past end-of-life, no updates.|
|5.3||Yes||End-of-Life cycle started March 2013, critical updates only.|
|5.5||NO||Supported (available as of June 2013).|
To put it clearly: there is no currently supported version of PHP that will run Joomla 1.5! While that shouldn't be panic-inducing, it is not something to be ignored. There's a lot of code out there (not just Joomla) that will have problems running under PHP 5.4, and lots of hosting companies will continue to support it, including Abivia. But – and this is a big one – sooner or later your host is going to send out a notice saying that they're moving to PHP 5.4 or 5.5. Depending on the host, you're likely to get anywhere between a week to 90 days notice. Even at 90 days, that's a pretty tight timeline for a mid-range site, particularly if you want to throw in a redesign at the same time.
This problem is made particularly challenging by the fact that the PHP folks chose to stick with the same major version number, even though they made some major changes to the language. There are some hosts who are just now retiring PHP 4. This was made possible because hosts could run PHP 4 in parallel with PHP 5. By not making recent versions PHP 6 and PHP 7, this mechanism is no longer available. If a host wants to support 5.4, they have to drop support for 5.3 at the same time.
So put your finger on the calendar a month from today, whatever day you happen to be reading this. Imagine that at the same moment you're doing that, you get a notice from your host saying "PHP 5.3 will not longer supported after..." and substitute the date under your finger. If that makes you uncomfortable, then it's time to start planning your upgrade!
Image credit: cta web (Flickr) Used under a CC-SA-ND license.