|
Joomla forced upgrade policy |
|
|
|
Tuesday, 23 August 2011 |
|
I have always been suspicious of a 'forced' upgrade policy, this is the
policy that Microsots (sic) impose on their user base, always changing
the goalposts and causing people to have to buy new versions of their
apps just because they change the underlying o/s. I say if it works then
stick with it. I have stuck to Joomla only to find I have been unable to
carry on with it as I couldn't upgrade certain of my sites. Those
remaining 10 x Joomla 1.0.15 sites, my preferred solution has been to
migrate the straight CMS sites to Joostina (J1.0.16+) or transfer the
cart-based sites to OSCommerce.
The former solution is a no-brainer as it is still approximately Joomla
1.0 and it satisfies my personal demands for a technically interesting
but easy upgrade path. The latter is interesting as it is a totally new
platform with plenty to learn and plenty to benefit from.
I would have had to choose neither of those two alternatives if the
migration path to J1.5 had not been quite so 'hard'.
It is an important point to note that a migration from J1.0 to J1.5,
although being essential, was fundamentally an uninteresting and boring
task to all concerned. No-one really benefitted much, and it was a
significantly time-consuming chore.
Many of us support multiple sites for multiple clients, so the decision
is more difficult.
From the time that Joomla 1.0 was end-of-lifed to now, I am pretty sure
that it would have been possible to introduce the changes more gradually
to get to where we are today. It might have been more work for the devs
but over this period of time I am sure it could have been done. The
problem is not so much that we had to migrate from 1.0, one migration
might just be bearable, it is the fact that we have to do it again and
again. I now realise that my decision to not upgrade from 1.0 to 1.5 has
saved me a lot of time, effort and money, avoiding 1.5 and 1.6 &c. I may
upgrade to Joomla 1.8 when it is proven that it is lot more stable and
hopefully not subject to more migrations - or maybe that is too much too
ask?
 |
Click on the image above.
(2)
Subscribe to this comment's feed