We have chosen Joomla for many of our projects as it's flexible, well supported, easy to use and highly scalable. It also happens to be cutting edge, and in an effort to keep it that way, an ambitious development strategy has been put into effect, click here for the details (http://developer.joomla.org/strategy.html).
As you can see from the development strategy, there are 2 types of release, Short Term Release (STR) and Long Term Release (LTR). To minimise maintenance costs, and to take advantage of more freely available extensions, we always recommend using the latest Long Term Release (LTR).
So, it's nearly the the End of Life for Joomla 1.5, which was an LTR. The latest LTR version is now Joomla 2.5.
Click here to see the Joomla Development Status page which gives status information on all the current Joomla releases, including launch and end of life dates.
It's a jungle out there, there are lots of Content Management Systems (CMS) vying to be top, many of them Open Source like Joomla.
Not only that, but the web landscape is changing at ferocious pace. External factors such as social media, a proliferation of technologies and devices mean that in order to keep up, a major release is needed every 18 months to 2 years.
Everybody wants a cutting edge website, with that WOW factor, improving Joomla regularly is a necessary step to achieving that aim.
How does this affect me?
If your website uses Joomla 1.5, you need to start thinking about upgrading it to 2.5 from July 2012 onwards, as it will eventually become vulnerable to security exploits. Joomla 1.5 will be obsolete, and as such no security patches will be available from the Joomla community.
What do I do about it?
We would recommend 2 options, migrate your current website to 2.5 by converting the current template, migrating your articles and revising and migrating your current extensions so that they are 2.5 compatible.
The second option, that will probably better suit anyone with a site that is 2 years old or older, is to review the website, and then re-build it from scratch to meet your current and future needs better. This could include new functionality, new/revised design and content, and the removal of functionality that is no longer required. It's a great time to take stock, re-focus, and re-answer probably the most important questions a website owner can have, "what are the goals I'd like my users to achieve, and how can I help them do that ?"
How we can help
Just get in touch and we can advise you accordingly, but remember, doing nothing could be asking for trouble!
Have you ever wanted to force a HTTPS connection for your ExpressionEngine website? If so, you may have also wanted to 'unforce' that connection for other areas of your website, either for performance issues or because maintaining both HTTP and HTTPS for the same section can be tricky. Avoid those pesky browser warnings about unsafe (non HTTPS) assets with this htaccess rewrite.
Everything looks better with an oilslick filter #Fireworks-- Delivered by Feed43 service11 Feb 2014 | 9:04 pm View full tweet
@meloncreative cool just be warned that the documentation for Form Integ. is incorrect, so if you are relying on it there are some gotchas-- Delivered by Feed43 service9 Jan 2014 | 5:39 pm View full tweet
@meloncreative do you need any sample code for the Form Integration?-- Delivered by Feed43 service8 Jan 2014 | 9:35 pm View full tweet
Thanks for your message! We will get back to you ASAP!