Forum Moderators: open

Message Too Old, No Replies

Is it necessary to upgrade to Joomla 1.5?

Do I really have to?

         

wjnesbitt

4:40 am on Sep 2, 2009 (gmt 0)

10+ Year Member



I'm still using Joomla 1.0.13. And I'm wondering is it necessary to upgrade to Joomla 1.5? Would my site be ok without the upgrade or is it something that's highly recommended I do?

What would be the advantages/disadvantages?

Sierra_Dad

5:05 am on Sep 2, 2009 (gmt 0)

10+ Year Member



I'm wondering the same, though with a slightly different leaning.

If I'm ready to move from Joomla 1.0.x to 1.5, wouldn't it also be worth considering something else? I;ve been with Joomla and I'm not entirely happy with it. I have more to say but won't hijack your thread.

Disadvantages that I can see for staying put: I believe that 1.0.x stopped providing security patches, so the next exploit might hack your sites and you might be forced to upgrade.

Disadvantages of moving: there will be some turmoil and your site may break temporarily in the process. Of course, for me that has always happened with Joomla for more minor updates or if the plugins/components/bridges that are out of sync with each other.

travelin cat

2:54 pm on Sep 2, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



We pondered this for a while, in fact we hired someone to help us migrate to 1.5.

In the end, we had too many conflicts with the existing 1.0X version of some plug-ins and decided not to migrate,

Since we do not sell anything, we have no merchant services, just content, I think we are a smaller target for hackers.

One thing I would recommend, if you are not doing it already make regular backups of your database and your home directory.

We have a plug-in that emails us our database every night. Also, once a week we make a backup of both, burn them to a DVD and put them in a media safe. We also keep copies on two separate hard drives. If something should happen, we should be able to be back up and running with a copy of our site that is less then a week old.

ergophobe

5:22 pm on Sep 2, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



We have a plug-in that emails us our database every night.

You don't need a plugin. All you need is a simple script that you run nightly as a cron job. And by the way, unless the plugin is fired by a cron job, it can only run when the site is being accessed, so if your site has primarily local traffic and is "dead" in the middle of the night, the plugin won't get invoked, so you'll want to create a cron job to hit the URL that fires the plugin.

My backup script looks like this


#!/bin/bash
DATESTAMP=`date +%Y%m%d`
mysqldump --opt -h 127.0.0.1 -u dbusername -pdpassword dbname ¦ gzip -c > gzippedoutput.gz
mutt -a gzippedoutput.gz -s "email subject line backed up on $DATESTAMP" ergophobe@example.com < File-with-email-body-text.txt

That's all you need - create a shell script like that (replace italics parts with your own info), set the file perms to make it executable, place it outside web root, and set a cron job to fire it daily.

No plugins needed, works with any CMS (or any DB for that matter) as long as the gzipped DB is small enough to mail as an attachment.

[edited by: ergophobe at 6:30 pm (utc) on Sep. 2, 2009]

travelin cat

5:36 pm on Sep 2, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



For those who don't like implementing their own script, the plug-in is actually a pre-made cron job extension for Joomla. Quick, easy, and free. There are a few of them at extensions.joomla.org, search for "cron backup"

ergophobe

6:34 pm on Sep 2, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



And of course a lot of people don't have permissions on shared servers to access the mail server, run a shell script and all that.

What I like about my solution is that it should never need updating, has fewer security issues (since it's outside web root) and can work with any DB regardless of CMS.

But I think I hijacked the thread... I only meant to say that wanting access to a DB backup plugin would not be an argument for upgrading/changing CMS.

Anyway, Marc, I remember you discussing the upgrade in the past. What pushed you over the edge to decide you needed to move to 1.5?

travelin cat

6:56 pm on Sep 2, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



We were worried about hackers, still are as we didn't complete the migration to 1.5 due to the problems I mentioned above.

We have been fortunate so far with 1.0.X, but we are prepared (hopefully) with our backup regimen.

Also, the site is rock solid. So we're hanging in there as we would have to really modify the site to untested stuff in 1.5

wjnesbitt

3:39 am on Sep 3, 2009 (gmt 0)

10+ Year Member



This info is great and all, but do any of you have any input on the original question which started this thread?

travelin cat

4:47 am on Sep 3, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



I was trying to point out that a move to 1.5 is not mandatory. If you feel that your site is not secure, you may wish to upgrade to 1.5 for its tightened security.

Also, many Joomla developers are only developing for 1.5 and have discontinued support for 1.0.X. The reverse is also true - one of the main reasons we did not make the change is because a key component of our site had no native 1.5 version. They still don't.